News for hackers. Stuff that matters.
Re:Overengineering can kill a product by nisa on Wednesday November 24, 2021 @06:46AM (#29329034)
Complexity kills your product - Overengineering is just one instance of complexity - Technical Debt like having state and data all over the place is another one - I quit my last job and I happily blame this article for convincing me to quit: https://itnext.io/the-origin-of-complexity-8ecb39130fc - coordination causes complexity and this killed me - we had everything not once but twice or more in different places - just one example - it's much more complex but me and my colleagues were grinded between an old codebase that nobody understood anymore and kubernetes, ci, etc.pp on the other side because management sold this without understanding that you need a process and time for digesting and applying the concepts in the team.
Re:Overengineering can kill a product by oweiler on Wednesday November 24, 2021 @08:08AM (#29329616)
This sounds exactly like the last place where I worked. I quit in anger Not because I don't like Kubernetes but because management sold it as the fixall solution.
Re:Overengineering can kill a product by throw10920 on Wednesday November 24, 2021 @11:15AM (#29331495)
> Complexity kills your product

This is like saying that water is lethal - both are true in the sense that some x (water, complexity) is ok, but too much is bad.

Complexity is an unfortunate (but necessary) side-effect of (1) adding features and (2) optimizing for performance, both of which are critical for building a product.

If you try to remove all complexity from your product, you won't have a product. Instead, you have to try to minimize complexity while still delivering the same set of features and level of performance.

Re:Overengineering can kill a product by vanusa on Wednesday November 24, 2021 @12:05PM (#29332247)
The basic point is that the default tendency in many environments is to run toward ever-increasing levels complexity -- often without even being aware that this is happening -- rather than be (as I believe one should be) by default always skeptical of added complexity.

If you try to remove all complexity from your product,

This wasn't what the commenter was advocating, of course.

Rather it was an attempt to simplify the basic message of: "Complexity has attendant risks which are too easily ignored -- and which in short enough order, can kill hour product."

Re:Overengineering can kill a product by vanusa on Wednesday November 24, 2021 @06:06PM (#29336262)
your product
Re:Overengineering can kill a product by nisa on Wednesday November 24, 2021 @04:02PM (#29335099)
basically I just looked for an excuse to post the link to the article - which is really a great article and describes the problems inherent to software in an - for me at that time - new and fascinating way.

Of course in practice it's always messy and rightly so, but I've learned the hard way that you better don't loose control about your state and data - because that's where the ugly bugs are.

The article is very good. Just ignore my drivel :)

Re:Overengineering can kill a product by baby on Wednesday November 24, 2021 @11:01AM (#29331305)
I interpret “early over engineering” not as adding complexity necessarily. It could also be about decreasing complexity but by taking too much time. Early on you’re supposed to rush to your MVP and add tech debt, not spend too much time to design something pretty and modular. Later on once you know your company can survive multiple quarters, then you can spend more time refactoring.
Re:Overengineering can kill a product by jasfi on Wednesday November 24, 2021 @06:58AM (#29329106)
I agree, complexity is the real underlying problem. That is why good frameworks and libraries help so much.
Re:Overengineering can kill a product by 123pie123 on Wednesday November 24, 2021 @07:38AM (#29329372)
>That is why good frameworks and libraries help so much.

until they change - again.

Re:Overengineering can kill a product by jeffkeen on Wednesday November 24, 2021 @07:45AM (#29329439)
Gotta keep up with the updates
Re:Overengineering can kill a product by amelius on Wednesday November 24, 2021 @01:59PM (#29333724)
My dependencies can't keep up.
Re:Overengineering can kill a product by rytcio on Wednesday November 24, 2021 @10:45AM (#29331098)
Frameworks and libraries are the cause of complexity, imo
Re:Overengineering can kill a product by baby on Wednesday November 24, 2021 @11:02AM (#29331326)
It depends, there’s a trade off. At some point things can become very complicated if you don’t abstract them and put them in their own lib or framework.
Re:Overengineering can kill a product by toopok4k3 on Thursday November 25, 2021 @08:27AM (#29341174)
The less you use external dependencies, more time for you to focus on your own product instead of solving problems updating those dependencies and replacing them.
Re:Overengineering can kill a product by d0m3 on Wednesday November 24, 2021 @05:51PM (#29336129)
Great article, thanks for sharing. I like the vocabulary explanations and the chart that summarizes all. Will share and read again!