I think "Programming" is just a word to decribe the representation of the consequence. The real value of a programmer is in understanding things fully (in orde

I think "Programming" is just a word to decribe the representation of the consequence. The real value of a programmer is in understanding things fully (in order to formally articulate them in a program). The suits I work with don't understand things fully, they just understand it to some (I'd say superficial) degree. Then they decide something but they don't know what constraints apply to what element in the process and their estimates / decisions / ... are regularly completely off. So I am not only a programmer, but I am the "understander" of the domain (and thereby of the production part of our business). This creates a lot of frustration because the suits decide, yet they don't know that they don't know. Hence also the tendency for good programmers to become independent or depressive.