3 ms·
Yes. I am simply accepting the premise given and trying to explore from there. I am aware of the generalisation. But, your answer does help us move ahead. It b
by scotch_bright 9y ago
Yes. I am simply accepting the premise given and trying to explore from there. I am aware of the generalisation.
But, your answer does help us move ahead. It basically says that there is a way to produce a high quality code base. It is not impossible. The right set of circumstances seem to be:
1. No deadlines
2. Focus on code quality
The "no deadlines" part I take to mean that within OSS projects there is time to refactor to perfection. There is time to design, comment, document and indent to perfection.
So, your point is it is possible. But it seems like within the context of a company, it almost never happens. (Nobody has still posted here to saying that their code base is not a mess. A lot of people have now seen this.)
When one thinks about that, it is just weird right? The people who get paid to make software do things that make their work un-productive. And the opposite is true for good OSS.
- chatmasta 9y agoWell, it seems like there exists a tradeoff between code quality and profits. Profits provide incentive, and therefore pressure, which manifests itself in deadlines. If we think of deadlines as time windows, then the tradeoff is really between code quality and time. Everyone knows this; rushing through projects will reduce their quality. Given all this, it should not be surprising that corporate code is “lower quality” than OSS. The authors of each are optimizing for different metrics. It’s only weird if you think companies are irrational for prioritizing deadlines over code quality.