>This policy has created a lot of extra work, headaches, and overhead for more senior programers that have to support it. By my best estimate, less than 2% of our code is written by non-programmer programmers. Despite all this, I’m very glad we did it.
Does the author hold some resentment for senior engineers or something?
I wonder if other areas of the org were opened up to this behaviour whether the response would be the same. How about having the accountants doing some experiment design or have data analysts balancing the books?
It's an interesting idea and social experiment but somewhere in their organisation, someone is bearing the brunt of it (engineers by the sound of it), and that's a cultural deficiency caused by bad leadership.
I would like to have heard more about how that deficiency might be solved but the post seems hell bent on driving home a narrow, feel good, "anyone can do it!" message rather than exploring the idea meaningfully.