Re:Ask HN: Software Design and documentation – what do you use?
by eddyparkinson on Wednesday August 13, 2014 @07:52PM
(#8175519)
>Second-system effect
Thanks, never seen that one before.
I wish there was better rule for deciding what feature to put in. Maybe for every added feature i should have "a use case" . ... Um, an "add feature rule", to create a good rule, maybe I need some use cases.
Instead of over-designing and engineering from the very beginning, I prefer a more iterative approach. Admit to yourself that the first time you design/implement a system you will most likely get a lot of things wrong. Get a proof of concept out there, and try to learn from it. The second time you design that system you will probably try to incorporate everything you know and are prone to overengineering and feature bloat (http://en.wikipedia.org/wiki/Second-system_effect). So, be careful.
Check out "The Mythical Man-Month". It's a timeliness book on software engineering.