3 ms·
If you can rewrite it in 3 or 4 weekends, it's really not that complicated. Either that or significant chunks of it were retained and your improvements were mo
by ams6110 8y ago
If you can rewrite it in 3 or 4 weekends, it's really not that complicated.
Either that or significant chunks of it were retained and your improvements were mostly cosmetic.
- JoeAltmaier 8y agoOr, they are actually good at their craft and rewrote it. That's not an unreasonable timeline. Taking code that does something and writing another version in another design pattern is much, much faster than starting from scratch. Even with complicated code (especially with complicated code)
- thrower123 8y agoIt really wasn't very complicated... basically just some queries to search a database and a front-end to display results. I still don't know how the preceding mess got to the point of being such a baroque cobbled-together monstrosity, but it was enough copy-pasta to keep an Olive Garden supplied for a year, and a raft of incomprehensible stored procedures that did SELECT * FROM table WHERE xyz in bizarrely complicated ways involving multiple casts and nested temp results.
- flukus 8y agoI've worked on similar projects that could have been re-written relatively quickly but were only complicated because the developers made it complicated. Some devs just want to solve hard problems in "elegant" ways and will throw in elaborate inheritance chains, meta-programming, code generation, service oriented architectures, layers upon layers, frameworks, rules engines and anything else that's not boring business logic. IME these projects are usually more complicated than all but the most wild of business logic.