News for hackers. Stuff that matters.
Re:Technical Debt: Why it'll ruin your software by ironmagma on Friday October 23, 2020 @02:15PM (#24872248)
It's also a bit of an abuse of the term. Overengineering in engineering (mechanical, civil and other similar disciplines) means building a component to withstand more than the absolute minimum. So, a bridge you'd want to be overengineered by a factor of 2 or 3 at least, whereas airplanes are hardly overengineered (lower factor of safety).
Re:Technical Debt: Why it'll ruin your software by Ma8ee on Friday October 23, 2020 @04:13PM (#24873518)
But isn’t that how the term is used? The system is over engineered when it is built to scale to a million concurrent users while we current only have a hundred. Or when it is built to handle use cases that no one has required.
Re:Technical Debt: Why it'll ruin your software by ironmagma on Friday October 23, 2020 @05:46PM (#24874595)
In this context I read it more as being excessively complicated to some unspecified end rather than engineered to withstand a load way larger than necessary.
Re:Technical Debt: Why it'll ruin your software by Ma8ee on Saturday October 24, 2020 @04:09PM (#24881638)
Often it is excessively complicated because it’s divided into dozens of services to be able to scale, or having extra abstraction layers to deal with imagined future requirements.
Re:Technical Debt: Why it'll ruin your software by ironmagma on Saturday October 24, 2020 @11:18PM (#24883609)
Sure, but the fact that those requirements are imaginary instead of real is why it’s not actual overengineering. Overengineering is done with a specific dimension of scalability in mind for something that probably will happen, and there’s a budget for it too, etc.
Re:Technical Debt: Why it'll ruin your software by miltondts on Friday October 23, 2020 @02:33PM (#24872418)
Ah I was not aware of the general term and its' meaning. As you say, quite the abuse of the expected meaning.