3 ms·
Those things are not necessarily all that terrible. I can see how overeager coders might do any of those things in anticipation of some as yet unseen requiremen
by lordnacho 10y ago
Those things are not necessarily all that terrible. I can see how overeager coders might do any of those things in anticipation of some as yet unseen requirement. And it's not always clear why a code base evolved the way it did.
Also let's not forget the opposite. I've worked in places where everyone just wrote their own spaghetti, no concept of version control, and every time there's a small change it takes ages for the only coder who wrote it to untangle and modify it. Basically a steaming pile of turd, used to invest real money in the real market. The worst part about it is when you call them out it's YOU who doesn't understand the requirements.
- ThomPete 10y agoThe thing is that just because it's spaghetti code doesn't mean it's not successful and thus it can be fixed. Premature optimization is the developers version of pixel perfection. They are both the enemy of getting anything done.
- tzakrajs 10y agoSpaghetti code is so frustrating to refactor, that you sometimes may as well rewrite to maintain your sanity.
- ThomPete 10y agoSure but then you do that. Its better than having spent an insane smount of time on something no one ends using.
- AstralStorm 10y agoWrite a serious test suite before doing so. Otherwise you will miss a bug 31337 fixed in 19xx and will be sad later.
- mathgenius 10y agoThe opposite of over-engineering is not spaghetti code, the opposite is "tracer bullets": http://www.artima.com/intv/tracer.html http://www.artima.com/intv/tracer.html