3 ms·
Great post. I think a similar issue is when an engineer feels they need a certain set of infrastructure or algorithmic features before they can start building t
by casual_slacker 13y ago
Great post. I think a similar issue is when an engineer feels they need a certain set of infrastructure or algorithmic features before they can start building their program. If you end up finding out that most potential users have a different problem though it can all be for waste. I've met many programmers who seem to have forgotten (or never learned) how to prototype, and can't imagine building something with a fundamental security or scalability flaw.
There's also a far more difficult one to become aware of, which is building an overly complex solution when a simpler one exists for the problem.
- jot 13y agoVery true. It's not just in the name of 'design' and 'user experience' perfection that developers overly delay their first product.
- mikeash 13y agoI can see passing on scalability, but security? In what circumstances does it make sense to build something with a fundamental security flaw? Getting security right doesn't have to take significantly more time than getting it wrong.