Kernighan and Pike were right: Do one thing, and do it well
Good article, but to me it seems to be co-opting the term enshitification in a strange way:<p>> Large codebases will eventually reach an “enshittification point” — the point at which bugs are introduced faster than they can reasonably be fixed.<p>I think of enshitification primarily as an organisational/business phenomenon rather than a technical one.<p>It doesn’t necessarily emerge “bottom up” as the result of technical debt but from top down as a result of misalignment of values between the brutally commercial goals of the business and the values/goals if its customers. Tech debt and development velocity do play into this but I don’t think it’s the <i>primary</i> driver of it.<p>The term is a useful one at that level of abstraction imho because we already have quite a lot of language to describe things like this at the lower, more technical level.