Once I worked for a company which I prefer not to name here. They wanted to solve a huge problem which I have solved during my previous tenure elsewhere. Once I

Once I worked for a company which I prefer not to name here. They wanted to solve a huge problem which I have solved during my previous tenure elsewhere. Once I learned that they are trying to do this I offered my help. I realized that they picked someone with zero experience with this who was about to make the same mistake(s) I made before. I managed to talk with the VP about this problem and after about half an hour I realized that the person who was responsible for this decision not only didn't know anything about software development, but he also didn't know what the problem was and why we wanted to solve it. A day after this talk I've heard that a very high level IC resigned so I had a talk with him. As it turns out he also worked on this problem before and spent 3 months trying to make his point about this and after he utterly failed he just couldn't take it anymore. I also resigned a few months later. Having managers that have no idea about how programs are written and how the whole process works is a surefire way to sink the ship. Needless to say this organization had layers after layers of managers who all tried to protect their turf from all the potential damage others can make.