[dondenoncourt]

Here! Here! Personally, I'm getting tired of refactoring NoSQL back the standard SQL and merging multiple "Microservices" apps into one manageable app. And figuring out the JS Single-page framework Dijour when standard Ajax-based pages would have cost far less to create and maintain yet provide the same functionality.

[MrBuddyCasino]

I think over-engineering is just plain old incompetency in a different costume. Good guys successfully manage complexity, bad ones don't. The bad ones have just more options now.

[cookiecaper]

The question is how do we successfully communicate this to everyone else. People see "We need to move this to super-cool new technology like THE GOOGLES!!!" as a positive, affirmative, and cutting-edge thing that will make them more like the coolest, smartest company there ever was, whereas they see "Why should we change that?" as backward and frightened.

We need some way to protect the industry from marketing-oriented impulses that mischaracterize flat, reliable, comprehensible architectures as primitive.

[meesterdude]

> I think over-engineering is just plain old incompetency in a different costume. Good guys successfully manage complexity, bad ones don't. The bad ones have just more options now.

I've felt alienated in some ways because of this, so i'm glad you put some light on it. I don't understand devs that so casually over-engineer or choose what's flashy for what works. I guess it's a matter of the tech mattering more than the product, and i've often held an inverse opinion.

[convolvatron]

there are lots of options out there for constructing systems.

but if you approach the problem by saying 'we don't need to really build software, we just make do by gluing together a bunch of big pre-existing packages' - then ... thats what you get

[meesterdude]

I''m glad I'm not the only one! So many of my rescue projects have been untangling overly-complex solutions by making the tech stack far more boring so that the project can make the project itself more interesting.