Re:Operators, Not Users and Programmers
by coderatlarge on Sunday July 06, 2025 @12:28AM
(#44477845)
unwieldy yes but a working prototype of what the organization actually needs.
two thoughts:
1) did you read the linked post on malleable software (https://nothingisnttrivial.com/vines.html)? it has a very good distinction between “functional risk” (is the business logic right) and “technical risk” (was the logic implemented correctly), and says—correctly IMO—that the more control we give to end users, the lower the functional risk is.
2) sometimes it’s ok for software not to scale (https://gwern.net/doc/technology/2004-03-30-shirky-situateds...). sometimes people are solving a problem just for themselves, not for a business. i want it to be possible to build situated software in an afternoon without spending a month studying how terminals and stacks and data structures work.
Yes, configurability is good and scripting is a great way to safely add functionality to a system but there will always be a distinction between people who use software and just want it to work perhaps with minor tweaking, and those who build systems. It makes no more sense to throw everyone in the same bucket than saying that being able to change the oil in a car makes everyone a mechnical engineer.
Also:
> Many, many technologists have taken one look at an existing workflow of spreadsheets, reacted with performative disgust, and proposed the trifecta of microservices, Kubernetes and something called a "service mesh".
Yes, over-engineering is a thing, but piles of interlinked spreadsheets are usually thrown out precisely because the people who created them didn't have the skills necessary to build a system, and these ad-hoc systems eventually outgrow their usefulness and become unwieldy horror shows. Maybe Beryl in accounts knows the eighteen cells across three files that need to be updated when the interest rate changes, but if she leaves then we're all screwed.