Paul Ford with short piece about low-code tools and the importance of working with data versus writing code:

Code culture can be solipsistic and exhausting. Programmers fight over semicolon placement and the right way to be object-oriented or functional or whatever else will let them feel in control and smarter and more economically safe, and always I want to shout back: Code isn’t enough on its own. We throw code away when it runs out its clock; we migrate data to new databases, so as not to lose one precious bit. Code is a story we tell about data.

...

This guide is a great example of how a lot of introductory walkthroughs of technology should work. Every time I’ve worked with new users to help them understand using the command line, Unix commands, or git, people only mimic the individual commands they’re supposed to type without a fundamental understanding of what’s happening.

This’ll now be the first place I send anyone new to git. I know this would’ve helped me a ton in wrapping my mind around how it all worked, and I already had some familiarity with the SVN “trunk” versus “branch” structure. The sketches throughout help especially...

An entertaining talk from Rich Hickey, creator of the Clojure programming language. He talks about the value of simplicity in software design, and spends a decent amount of time refining the semantic differences between “simple” and “easy”. My biggest takeaway: simple is objective, easy is relative.

It gets pretty technical in the CS realm, but good principles for building anything.