3 ms·
Is there a point though, when badly written code becomes so hard to maintain and improve, that people would just avoid doing that altogether? The reason "badly
by capdeck 7y ago
Is there a point though, when badly written code becomes so hard to maintain and improve, that people would just avoid doing that altogether?
The reason "badly written" works for Open Source is that if code is useful - there will be someone in the future who will refactor it. In proprietary setting that only happens when the fate of the company itself (or a large chunk of the business) is at stake. Otherwise stagnation is king.
- diminoten 7y agoIt's easy to pretend that "badly written" code is intentional or desirable, because then when we write it, we can excuse ourselves by saying, "BUT IT WORKS!" That's why this idea is popular, and your comment is controversial. You're taking away a crutch that many of our peers cling desperately to as a way to justify their shortcuts and poor decision making.
- deleted 7y ago[deleted]
- naniwaduni 7y ago> there will be someone in the future who will refactor it maybe abstractly in practice, this never happens because the code will cease to be considered useful first