3 ms·
Not necessarily. There's plenty of horrible, horrible code that doesn't get changed because it currently works, and it would be too much of a hassle to try and
by pyre 17y ago
Not necessarily. There's plenty of horrible, horrible code that doesn't get changed because it currently works, and it would be too much of a hassle to try and de-tangle it. There's also really awesome code that gets replaced because the requirements have changed and it needs to do something completely different.
- patio11 17y agoI throw out about 50% of all code written for A/B tests within, typically, a week or two. If it weren't for all the business value added by it, I guess I would suck as a programmer.
- Periodic 17y agoIn fact, the particularly horrible code might not be replaced for a long time precisely because it is hard to understand but it works and changing it could cause problems elsewhere. There are plenty of enterprise systems like this.