3 ms·
If it was just based on the title and the term "half-assed" then I would agree about technical debt. But having read the article, I'm not sure that is quite wh
by ilaksh 6y ago
If it was just based on the title and the term "half-assed" then I would agree about technical debt. But having read the article, I'm not sure that is quite what he was saying.
He is talking about prioritization of effort and how thorough the solutions are. If you properly judge the importance of things or the level of sophistication actually needed to solve the problem adequately (but not necessarily "fully"), you may not ever need to revisit that part. Especially since requirements evolve. But also because bottlenecks (in terms of performance or requirements churn or bugs etc.) are often clustered in particular areas. So even though there is a more complicated solution that could be more elegant or flexible or performant, it may actually never make sense to implement because the relative importance just never increases.
What he seems to be more or less talking about is similar to the 80/20 Rule (ala Pareto Principle).
I think a less negative term could have been less confusing.