I'm the owner of my small software development shop. So that makes me management. I'm also the principle programmer of the code we develop. We have junior devel

I'm the owner of my small software development shop. So that makes me management. I'm also the principle programmer of the code we develop. We have junior developers whom I manage. There are several deep problems with the rules described above. The primary problem the assumption of agency inherent in these recommendation. The manifesto assumes that interests of the employee/programmer are identical to the owners/managers. Most of the time they are aligned. Occasionally, usually on critical decisions, they are not. Take for example the principle of code ownership. I would very much like my junior developers to own the code they develop, fix it and take pride in maintaining it and refactoring it. However, for some of the individuals, their objective is to learn as much as possible in the shortest period of time, so they can grow and get higher paying jobs. This is a perfectly legitimate, indeed desirable objective, for any individual. However, this also, often translates to a lack of interest in maintaining code. So as their manager, I also become the owner of the code. I find myself, maintaining a bunch of code. I'm okay with this. I do delegate some maintenance of the code to others, but I usually find myself modifying and once in a while rewriting the code, until it is in a generally stable state, that does not require much maintenance. Them there is the idea of voluntary and free collaboration. In general of course, employment is voluntary, but I'm guessing the recommendation is not made in that sense. The idea I think is that programmers should be free to choose their own projects, possibly their own tech stack. That does make sense within the confines of a given business need. However, free reign can be dangerous. I routinely find, that my programmers, prefer to rewrite code in the latest fad framework, rather than simply fix issues with old code. In one extreme instance, I had a programmer use reactJS for what ended up being about 20 lines of plain Javascript. It seems like he wanted to learn to use React. I deployed him onto a project that actually did need react, and rewrote the original code in plain JS. It's now code that needs no maintenance at all. Nevertheless the sentiments expressed in this manifesto are important to keep in mind I suppose.