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...
For further actions, you may consider blocking this person and/or reporting abuse
you missed an "s":
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".
even if the word "stupid" is addressed to the programmer it's okay for as it can be consider a good alert to remember. 😁
Means: Dont be stupid, keep it simple!
exactly 👌
you are right 😂😂
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.
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
Nice article. i'll shared in my linkedin
glad you liked it, check also my other articles
It's what I tend to do more when using C# and less when using Go. :-)
i always feel like C# is pushing you to use simplest way without need to go throw a lot of hassle
Pareto principle too
can you explain it?
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...
thanks for explanation