DEV Community

Cover image for What is overengineering

What is overengineering

Hasan Elsherbiny on January 26, 2024

how many times you have started a side project to address a simple idea, but after few days a lot of things have come to your mind and you wanted t...
Collapse
 
efpage profile image
Eckehard • Edited

you missed an "s":


Kiss

Collapse
 
eljayadobe profile image
Eljay-Adobe

I like the phrase "keep it simple stupid".

The word "stupid" refers to the "it".

The word "stupid" does not refer to the programmer or to the user.

If the "it" were made clever, that's bad. Hard to maintain. Hard to reason about. Hard to debug.

If the "it" were made too-clever-by-half, that's really bad.

However, if the wording gets someone upset, I'm okay with "keep it stupidly simple".

Collapse
 
hasanelsherbiny profile image
Hasan Elsherbiny

even if the word "stupid" is addressed to the programmer it's okay for as it can be consider a good alert to remember. 😁

Thread Thread
 
efpage profile image
Eckehard • Edited

Means: Dont be stupid, keep it simple!

Image description

Thread Thread
 
hasanelsherbiny profile image
Hasan Elsherbiny

exactly 👌

Collapse
 
hasanelsherbiny profile image
Hasan Elsherbiny

you are right 😂😂

Collapse
 
arocha profile image
Nefario313

Always amaze people arguing of using architecture, technologies or trending solution before studying the problem domain. The abuse of "use of API" for everything, microservice architecture, containerized solution and so on... are the most frequent nowadays.

Collapse
 
hasanelsherbiny profile image
Hasan Elsherbiny

this is what i said to some of my friends few days ago, when told me he wants to learn DDD ,microservice and these new staff

Collapse
 
muhamadsyahrulmubarok profile image
Muhamad Syahrul Mubarok

Nice article. i'll shared in my linkedin

Collapse
 
hasanelsherbiny profile image
Hasan Elsherbiny

glad you liked it, check also my other articles

Collapse
 
ruicraveiro profile image
Rui Craveiro

It's what I tend to do more when using C# and less when using Go. :-)

Collapse
 
hasanelsherbiny profile image
Hasan Elsherbiny

i always feel like C# is pushing you to use simplest way without need to go throw a lot of hassle

Collapse
 
valvonvorn profile image
val von vorn

Pareto principle too

Collapse
 
hasanelsherbiny profile image
Hasan Elsherbiny

can you explain it?

Collapse
 
valvonvorn profile image
val von vorn

Pareto is another strategy to keep things simple, by doing what is good enough , and try not to reach perfection. The rule of thumb claims that's about doing 80% of what we could achieve in 20% of the total time, and try not to waste the other 80% on the remaining 20% to perfection.

Wikipedia:
en.wikipedia.org/wiki/Pareto_princ...

The Pareto principle states that for many outcomes, roughly 80% of consequences, come from 20% of causes (the "vital few").[1] Other names for the principle are the 80/20 rule, the law of the vital few and the principle of factor sparsity.[1][2]

Thread Thread
 
hasanelsherbiny profile image
Hasan Elsherbiny

thanks for explanation