News for hackers. Stuff that matters.
Re:The Fallacy of Premature Optimization (2009) by teddyuk on Tuesday December 31, 2019 @05:57AM (#21920192)
I just finished a project where literally everything had been over engineered to the point that it took them weeks to do a release.

The code generally had one path but every method was built using dictionaries of possible classes that would implement interfaces so they wouldn’t have any duplicate code.

Sometimes some dev teams go down the wrong path.

Re:The Fallacy of Premature Optimization (2009) by MaxBarraclough on Tuesday December 31, 2019 @06:30AM (#21920324)
> dictionaries of possible classes

Sounds like a horror show built by people who don't understand OOP.

Re:The Fallacy of Premature Optimization (2009) by Doxin on Tuesday December 31, 2019 @07:19AM (#21920533)
Sounds like a group of people succumbing to the inner platform effect: https://en.wikipedia.org/wiki/Inner-platform_effect

It's not nearly as uncommon as I'd like.

Re:The Fallacy of Premature Optimization (2009) by MaxBarraclough on Tuesday December 31, 2019 @08:24AM (#21920821)
It doesn't sound like inner-platform-effect to me. teddyuk didn't say they were reinventing the wheel, just that they were doing awful things with dictionaries.
Re:The Fallacy of Premature Optimization (2009) by teddyuk on Tuesday December 31, 2019 @12:26PM (#21922693)
I started reading the article:

“ The inner-platform effect is the tendency of software architects to create a system so customizable...”

Yup, that was it and I have seen it so many times - architects should think that a flexible system that “can just” handle any possible future requirement. This always ends in a mess of junk that isn’t actually needed by the business.

Re:The Fallacy of Premature Optimization (2009) by FpUser on Tuesday December 31, 2019 @02:35PM (#21923937)
They might as well hand a development tool to a client and call it a day ;) Super flexible