Re:Doing is normally distributed, learning is log-normal
by nabla9 on Tuesday May 28, 2024 @06:38AM
(#40499287)
Prototype is not the first system.
Re:Doing is normally distributed, learning is log-normal
by piva00 on Tuesday May 28, 2024 @06:48AM
(#40499357)
Second-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!
Re:Doing is normally distributed, learning is log-normal
by mpweiher on Tuesday May 28, 2024 @06:42AM
(#40499317)
"If you plan to throw away one, you will throw away two" -- Programming Pearls
https://tildesites.bowdoin.edu/~ltoma/teaching/cs340/spring0...
> 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