2 ms·
This is a great article. I've worked for defense contractors, but most of my time has been spent at a very conservative, results-driven, constantly-in-ship-mod
by ChrisMarshallNY 7y ago
This is a great article.
I've worked for defense contractors, but most of my time has been spent at a very conservative, results-driven, constantly-in-ship-mode commercial corporation.
It has taught me to make software that actually works; not software that looks like it works.
I don't give pitches; I give demos. I quickly learned to never try selling a pig in a poke. It had better work.
The problem with that, is that it takes more work and time to get to that phase, and, possibly, more risk.
It taught me to carefully evaluate projects, and plan for the long term.
I'm often painted as a "naysayer" because of this.
Nothing could be farther from the truth. I plan to succeed. That means shooing the unicorns and pixies out to pasture, and concentrating on the raw materials, and how we will get from here, to there. That often requires resource husbandry, and compromises.
I also NEVER assume that the MVP will be a "one-off." It WILL be the seed of the product for the long term, so it can't be rushed, and it must be of the highest quality that can be reasonably achieved. I generally optimize for quality over features for early-stage releases; knowing that we probably will never be given the chance to "go back and fix it later."
In that respect, the corporation was very much like the defense department. There's a story about Hyman Rickover, and how he'd deal with tech salesmen, coming to his office with sample kit. I'm not sure if it's true, but it is fun:
He is said to have taken the kit, walked over to his second-story Pentagon window, and dropped the device out onto the ground below.
"If it still works, I'll consider it." He is reputed to have said.