Posts tagged with simplicity
The true work is in building complexity into software, then thoughtfully editing and pruning it into something that takes a minute to learn, yet offers a lifetime of mastery for those who want to accomplish complicated things.
Read more [buttondown.com]
say: complexity very, very bad
Read more [grugbrain.dev]
Join 9,500+ smart developers
Every month I share what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
What I've come to realize, though, is that anyone can write code that seems complicated. The hard thing is solving complex problems with simple code.
Read more [www.joshwcomeau.com]
We're way overdue a correction back to simplicity for the frontend. ES6/HTTP2/Import maps looks like they'll deliver just that.
Read more [world.hey.com]
All models are wrong but simple models are more wrong than complex ones. Simple models are more appealing, easier to teach and spread and apply. Because of that, they can bring value faster, and they can cause harm faster.
Read more [verraes.net]
Seb makes the case that subtracting things can be better than adding things.
Read more [sebastiandedeyne.com]
Gergely Orosz argues that you should start with a simple design and try your best to keep it simple. I don't necessarily agree with everything in the post, but it's an interesting opinion nonetheless.
Software architecture best practices, enterprise architecture patterns, and formalized ways to describe systems are all tools that are useful to know of and might come in handy one day.
Read more [blog.pragmaticengineer.com]
Extracting doesn’t guarantee simplicity. Sometimes extracting code into another module means I’ve smeared one “conceptual module” in my brain into two physical files. Now I can’t look at the whole thing at once, and their internal wiring is more prominent than it deserves. Oops.
— Dan Abramov (@dan_abramov) September 25, 2019
Read more [twitter.com]
DHH explains that there's nothing wrong with a bit a magic.
It’s always better to be explicit! That’s pretty much a programming truism. Rarely directly challenged, lest one betray the foundational tenors of Proper Programming. But challenge it we should, and head on.
https://m.signalvnoise.com/programming-with-a-love-of-the-implicit-66629bb81ee7
Subhas Dandapni wrote an excellent overview of the most common over-engineering mistakes.
Few things are guaranteed to increase all the time: Distance between stars, Entropy in the visible universe, and Fucking business requirements. Many articles say Dont over-engineer but don’t say why or how. Here are 10 clear examples.
https://medium.com/@rdsubhas/10-modern-software-engineering-mistakes-bc67fbef4fc8
Sandi Metz solved the Roman numerals kata in a very interesting way. Along the way she makes the case for keeping code simple.
The desire for simplicity means that I abhor special cases. I am willing to trade CPU cycles to achieve sameness. I'll happily perform unnecessary operations on objects that are already perfectly okay if that lets me treat them interchangeably. Code is read many more times that it is written, and computers are fast. This trade is a bargain that I'll take every time.
http://www.sandimetz.com/blog/2016/6/9/make-everything-the-same
Amen to that. I did not know that additive Roman numerals are perfectly valid.
If you want to read more posts by Sandi, be sure to subscribe to her newsletter.