3 ms·
In my experience misdirected effort comes more from a lack of planning or full-fat spec being produced before the work begins rather than an attempt to cram in
by corobo 9y ago
In my experience misdirected effort comes more from a lack of planning or full-fat spec being produced before the work begins rather than an attempt to cram in every feature under the sun.
Instead of knowing exactly what features to put in you get a request along the line of "We need something that does x" and no time to plan how to do x, so you end up with something that does it then the feature creep starts, making the original x look like a code version of Seth Brundle after his teleportation mishap in The Fly.
The age old "Weeks of programming can save hours of planning"
- jsty 9y agoTotally agree. A few pages of good spec / design docs can save so much wasted effort. Indeed I'd struggle to think of many non-trivial past projects where committing the design to paper hasn't revealed some hidden flaw that would've bitten hard later on. > Seth Brundle after his teleportation mishap in The Fly For anyone who didn't get this reference like me ... http://i43.tinypic.com/2ngr969.jpg http://i43.tinypic.com/2ngr969.jpg
- _asummers 9y agoI think the underlying wisdom is "don't create frameworks for your solution before you have it" not "don't anticipate your first and second degree direction changes".