3 ms·
> I often fail to deliver or comprehend industry jargon. In my experience, that alone can act as a powerful blocker. Although I'm quite sure that the jargon t
by tempodox 5y ago
> I often fail to deliver or comprehend industry jargon.
In my experience, that alone can act as a powerful blocker. Although I'm quite sure that the jargon thing is being used as a proxy for something more substantial, I doubt that it's a useful one. I suspect it's actually more of a social-group thing (are you “in” or are you “out”) than anything else.
One question about the “Q.C.D.”, though (quantum chromodynamics?). Could it be that you meant q.e.d. — quod erat demonstrandum (≈ “what was to be proven”)? Lowercase to distinguish it from the acronym for quantum electrodynamics.
- ChrisMarshallNY 5y agoQuality, Cost, Deliverable. The Japanese live by it. If you ever want to work with a Japanese company, it's a good idea to know it. I think Deming may have started it. "Quality": How do we measure the deliverable? Not just testing targets. Any form of quantification. Progress tracking goes here, as does a lot of things like CI. "Cost": What will the cost of the deliverable be? Not just money, but also schedule, the number of folks working on it, prototypes, BoM, progress meetings, buy-in from stakeholders, risk management, etc. "Deliverable": What will be delivered? Please describe expected deliverable, what will be delivered at milestones defined in (Q) and (C). It's a very rigid process (good for hardware), but can be difficult to deal with in software. I've learned to do my own version of it. I've written about it. BTW: I just demonstrated "jargon," but in a different way. I do not think less of you for not knowing it.
- tempodox 5y agoThank you for the explanation! I actually didn't know that.