2 ms·
I spent 6 months on a feature that I thought would require 2 lines of code and less than an hour to test and ship. It took 1 month dissecting spaghetti to conc
by themerone 3y ago
I spent 6 months on a feature that I thought would require 2 lines of code and less than an hour to test and ship.
It took 1 month dissecting spaghetti to conclude the task was impossible without a hughe rewrite.
5 months later, the feature was a 2 line change, that could be tested and shipped in an hour.
- deely3 3y agoThats true. For system complex enough you will spend more time learning system than modifying it. Thats why all developers love to write new code and mostly hate to suport existing, working, legacy code.
- e12e 3y agoThis is the way: > for each desired change, make the change easy (warning: this may be hard), then make the easy change - Kent Beck https://twitter.com/KentBeck/status/250733358307500032 https://twitter.com/KentBeck/status/250733358307500032 Also related to tfa: > If you have a month to plan a project in detail, spend it on four one-week iterations developing while you improve your estimates. If you have a week to plan a project, hold five one-day iterations. Feedback cycles give you information and the experience to make accurate estimates. - Kent Beck, Extreme Programming Explained: Embrace Change (The XP Series)