It's like.. a very specific dialect, or way of thinking, where the primary benefit appears to be in selling the simplicity of framework thinking, but where the outcome is an explosion of unintuitive and complicated database manipulations resulting in incomprehensible designs.
Nothing is more complicated to build and maintain like an application built on active record.
You have to invest an incredible amount of effort into making simple changes to those things after a couple of years.
The amount of mental focus it takes absolutely destroys my mind.
You might as well timestamp it: Each time you're introducing a Boolean field in a Database schema, use a timestamp instead. Future You will thank you. #SQL#Architecturechangelog.com/posts/you-migh…
I would consider Modern Software Engineering by @davefarley77 and Accelerate by @nicolefv et al. to be required reading for every founding team that works with software, regardless of the role.
If the changes at Twitter teach us anything, it’s that we should each be in control of the source of truth for what we say on the Web, else it’s likely to be lost or made inaccessible at any time. Your own site and RSS are a great expression of that.
I expected technology to make programming less laborious, as it does to most things. But I have to admit I expected it to happen by programmers switching to more powerful languages, rather than continuing to write programs full of boilerplate, but having AIs generate most of it.
tidyfirst.substack.com/p/distinctions… At first, programming is just programming. You think of a thing. You make the computer do it. 🎉
After a while, you notice that not all programming is the same. Déjà vu sets in. “I’ve done this before.”
A list of distinctions in software design.