Ok, that is a good point, I can absolutely see that I may be wrong to call is fascist, but it is definitely authoritarian, where the coders decide the rules and the program enforces them, I can see that applying a left/right political bias can be wrong.
Code is a language that can describe all sorts of systems, some of those systems have rigid hierarchies and some of those systems are distributed.
Software development teams also tend to work in collaborative ways, as much as Agile and Scrum development practices are bastardized in many large companies the core philosophies are very worker-empowering.
In the cases where companies use “waterfall” or misuse Agile the culprit seems to be managerial interference or very rigid and important requirements (e.g. a plane software system that must not fail)
I see your point, but per the above I would say it’s not universal and I would also counter that software architects have very open-ended solutions to choose from and are used to thinking about a system as a whole, which in my case at least leads me to questioning how our political and social systems can change for the better.
Fair, just wanted to point out that the monarchy class I’m proposing is actually a communist class intended to keep the capitalist/socialist citizenry in check. So there may be more in it than you might have realised from the abstract alone.
Ok, that is a good point, I can absolutely see that I may be wrong to call is fascist, but it is definitely authoritarian, where the coders decide the rules and the program enforces them, I can see that applying a left/right political bias can be wrong.
Code is a language that can describe all sorts of systems, some of those systems have rigid hierarchies and some of those systems are distributed.
Software development teams also tend to work in collaborative ways, as much as Agile and Scrum development practices are bastardized in many large companies the core philosophies are very worker-empowering.
In the cases where companies use “waterfall” or misuse Agile the culprit seems to be managerial interference or very rigid and important requirements (e.g. a plane software system that must not fail)
I see your point, but per the above I would say it’s not universal and I would also counter that software architects have very open-ended solutions to choose from and are used to thinking about a system as a whole, which in my case at least leads me to questioning how our political and social systems can change for the better.
Glad to see like-minded people here! I actually just finished a manifesto on this exact topic:
https://arendjr.nl/blog/2025/02/new-monarchy/
It’s quite the read, but I’d be happy to hear your feedback.
Not like minded… I’m not opposed to the principles you lay out in your abstract but the monarchy power structure isn’t what I’m interested in.
Socialism, communism, and ultimately anarchism are the way forward in my opinion.
Fair, just wanted to point out that the monarchy class I’m proposing is actually a communist class intended to keep the capitalist/socialist citizenry in check. So there may be more in it than you might have realised from the abstract alone.