3 ms·
> Hence plan to throw one away; you will, anyhow. > Fred Brooks as usual stands the test of time.[...]I'd bring the argument against a Second-System I'm confu
by scubbo 2y ago
> Hence plan to throw one away; you will, anyhow.
> Fred Brooks as usual stands the test of time.[...]I'd bring the argument against a Second-System
I'm confused. The GP appears to be saying that one should plan to build two systems - one as a proof-of-concept, and another (which is actually presented to most customers) in which one does things "the right way" based on learnings during that process - whereas you (and Fred[0]) seem to allude that the second system tends to be bloated and over-engineered. What am I missing?
[0] https://en.wikipedia.org/wiki/Second-system_effect https://en.wikipedia.org/wiki/Second-system_effect
- nabla9 2y agoPrototype is not the first system.
- mpweiher 2y ago"If you plan to throw away one, you will throw away two" -- Programming Pearls https://tildesites.bowdoin.edu/~ltoma/teaching/cs340/spring05/coursestuff/Bentley_BumperSticker.pdf https://tildesites.bowdoin.edu/~ltoma/teaching/cs340/spring0...
- piva00 2y agoSecond-system effect is the replacement of a full production application with another full blown production application where the second-system has to replicate all (or at least most) of the features from the first-system into the second one while also adding new features into the second-system. Even worse are the cases where the first-system still has to coexist and keep being developed while the replacement second-system is in development, that usually leads to a never-ending catch up of the second-system trying to integrate all the changes from the first-system that happened after the start of the second-system project. Have you read the book? I'd recommend it!