mini software dev rant
It boggles my mind how it's *still* a widespread belief that libraries/frameworks must be opinionated "because otherwise people would get lost in the options" - as if "technically forcing people into a specific choice" (with all of its significant downsides) is somehow the only possible way to help guide someone towards a sensible solution.
mini software dev rant, pol?
I really have to write Properly(tm) about these intersections between authoritarian ideology and software development culture some day, because this is *far* from the only case where this crops up
mini software dev rant, pol?
I wonder whether this can be convincingly explained to people (who have bought into that ideology) by equating it to the saying about "teaching someone to fish", as that saying seems to resonate with a lot of tech folks on an emotional level - an opinionated framework is giving someone a fish, providing guidance on how to select options and what options there are is *teaching* someone to fish.
re: mini software dev rant, pol?
mini software dev rant, pol?
I also feel like this ties into authoritarian ideology in interesting ways. The broader belief that the only way you can make people do something "for their own good" is by forcing them into it and giving them no other choices, rather than giving people agency and trusting them to be responsible and competent in handling it.