[yold__]

I think there is an additional reason here too. Software development work is (too often) seen as heads-down, anti-social work. Large corporations often bridge communication between software developers and the business/end-users via third-parties, such as product owners/manager, architects, and business analysts. Remember the "telephone" game we all played in kindergarten, where a message whispered between participants becomes comically unrecognizable by the time it reaches the last person? That is BigCorp software development in a nutshell.

Solving this communication problem is uncomfortable. Connecting software developers with end-users is hard. It means software developers have to have courage to ask "dumb questions" when the end-users explains something too quickly in jargon-laden terms. It means that end-users have to be patient, with the time to teach and explain enough about the problem domain. People with strong communication *and* technical skills are hard to find, and creating ongoing mutual respect and cooperation between end-users and the oft-hated IT department is only possible when employee attrition is low enough to create long-standing relationships.

Software development is fun when it is a high-momentum, self-contained exercise. So we direct our energy to complexity, because its fun and safe. We don't need to stop and engage with end-users who speak a language we barely understand. We don't need to create consensus among disagreeing end-users representatives. We just need put on some good music, drink some coffee, and solve clean technical problems, rather than messy people problems. I'd guess most software developers would say "you don't pay me enough to deal with people", and walk away.

[sharas-]

Hi yold_. It is made heads-down anti-social work by simple minded managers. They create infantilized environment that self-select for devs that don't like to talk to people.

Talking to people is trusted to "big boys" from business. You've listed the roles. Business big boys will sell complexity to clients through IT woo wooo. More complexity - more revenue.

I guess the most useful understanding from my post is that it is by design. It didn't "just" happen. Corporations bread them and make it a norm. This proliferates an understanding of a dev as an infantile that plays with himself.

Thank you for showing me I probably didn't articulate that understanding well enough.

[MonaroVXR]

> "Software development is fun when it is a high-momentum, self-contained exercise..."

Same goes for SOME sports, I mean whenever you score a goal, your team automatically are making a profit from you. Not that is bad, but it still does.

But what you're explaining is part of the software development or I.T. in general.

[sharas-]

P.S. Do you mind if I add your comment to the post?

[yold__]

no prob, go ahead