LOL
The basic selling point of starting a greenfield project instead of trying to fix the existing codebase is to replace the old & tired problems with fresh & exciting problems
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
When the key developers leave, it is time to rewrite the sh*t.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Paying down the existing tech debt is a lot less appealing than declaring bankruptcy and incurring new tech debt
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
... and then, eventually, when those problems turn out to be more bothersome than expected, complain to management about being stuck in the maintenance swamp, and make them offload it all to some offshore contractors. Usually happens around first public release of the product.
-
... or, in the case of REAL experts, some 6 to 12 months before release. I mean, only small minds can get excited about such words as "quailty", "defects" and "production-ready" when the basic concepts have been demonstrated. All these crashes just shows how advanced it all is.
End of conversation
New conversation -
-
-
Also true for most startups.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You mean like Jax, Flax, Trax, Objax, Optax, and Haiku? P.S. this an attempt at humor, I like Jax.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
BTW: Also doomed to failure is the attempt to create a software solution all over again from scratch in order to avoid the design errors of the first implementation the second time around. Even if you ever get the chance: don't do it!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.