Frankly, computer science knowledge and software abilities can be a real liability as an engineer. Many times what is needed is to let go of a sensible technic

Frankly, computer science knowledge and software abilities can be a real liability as an engineer. Many times what is needed is to let go of a sensible technical approach and just help the organization go where it is trying to go. It may not make sense technically, but it makes sense to the org, and that sort of matters more. I find my knowledge of good architecture often just makes it more painful to watch the code go through the inevitable logjams, rewrites, and process failures that are a crucial part of an organization “feeling” it’s way through a very complex multi-dimensional domain that includes many considerations that have nothing to do with code. I think in many ways, people with less technical skills can do that better, to live in the meta space. My brain keeps getting dragged down into the “why can’t we just do the sensible, minimal, technically correct thing that needs to happen for this problem to go away”. But the answer is “because the org doesn’t see the problem the way you do”. What good is it if I can solve problems no one else in the organization even recognizes as problems?