3 ms·
Thanks so much for that! This is heresy, in today's tech industry: > The manager, of course, remains ultimately responsible and must accept the blame if subor
by ChrisMarshallNY 3y ago
Thanks so much for that!
This is heresy, in today's tech industry:
> The manager, of course, remains ultimately responsible and must accept the blame if subordinates make mistakes.
> Complex jobs cannot be accomplished effectively with transients. Therefore, a manager must make the work challenging and rewarding so that his people will remain with the organization for many years.
> The ideas I have mentioned are not new—previous generations recognized the value of hard work, attention to detail, personal responsibility, and determination.
Engineering is not a new discipline. Software engineering is, but humans have thousands of years of prior art, and it is being actively ignored by today's tech industry. I was privileged to work for a 100-year-old engineering company. It had a lot of frustrations, but they made damn good hardware. I learned a great deal from them (and also banged my head bloody, trying to get them to let me deal with software differently from hardware).
I think that this should be on a billboard on I-280S:
> ... when the details are ignored, the project fails. No infusion of policy or lofty ideals can then correct the situation.
- paulryanrogers 3y agoWhat about their software approach did you want to change and why?
- ChrisMarshallNY 3y agoThey treated software in exactly the same manner as hardware: measure twice/cut once, waterfall. All QC was after the fact, and done manually. We did a great job of delivering yesterday's technology, tomorrow. I wanted them to add flexibility. Things like a different QC system, iterative development, and faster releases of software. I won't get into details, though. Much as I wasn't happy with things, I had (still have) tremendous respect for the company, and wish them nothing but good luck (they'll need it). I will say this, though: I worked with some of the top engineers and scientists in the world. The company had been producing precision optical equipment for 100 years, and people paid a lot of money for it. It was extremely hard to suggest that they might want to consider doing stuff differently. They had a formula that worked quite well, and not changing on a whim was a big part of that. I think most folks, hereabouts, would go nuts, working that way, but you can't argue with the results. I learned to write software of a pretty high Quality, as a direct result of working with these folks.
- MichaelZuo 3y ago> …measure twice/cut once, waterfall. All QC was after the fact… Doesn’t “measure twice” imply some QC is being done before the “cutting”?
- ChrisMarshallNY 3y agoSort of. They basically had "Quality" as a part of their entire culture. Each person was expected to do their part in the Quality ecosystem. The spec process could take months; years, even. Once a spec was written, it became Holy Writ. It could only be changed or amended with buckets of blood. The projects tended to be about 50% spec, 20% initial development, 30% post QC, and then, 50% fixing the problems found by QC. We tended to deliver software that people wanted, eighteen months ago. It worked to spec, but didn't do much else.