Been doing this you a very long time too and I highly disagree that devs should be shielded from business analysis and kept several steps away from upper management.
In fact quite the opposite, your suggestion is a recipe for substandard and failing software projects.
To make high quality software the quickest and cheapest way developers should be intimate with the domain and have a good relationship with the clients and stakeholders. I could write a book on the amount of times i've seen this work beautifully. I could write 10 books on how many times i've seen projects ruined by companies keeping developers in silos and behind layers of communication.
Software design at it's best is an iterative process.. this means involving everyone in the decision making. I think having BAs who don't understand tech who hand down tasks to be turned into code is wrong... tech decisions are better made at the same time as features and ux.
If the devs know the domain they will come up with much better solutions most of the time .. i see this constantly... plus the more you keep your devs isolated the more they think about tech and the less they think about pragmatism and business value.
On your other point, I do agree that it is highly beneficial to have managers who have a computer science background, although in my experience most of the time it's better not to have a manager at all... or if you do, one that actively codes and is more of a mentor than an authority figure.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Been doing this you a very long time too and I highly disagree that devs should be shielded from business analysis and kept several steps away from upper management.
In fact quite the opposite, your suggestion is a recipe for substandard and failing software projects.
To make high quality software the quickest and cheapest way developers should be intimate with the domain and have a good relationship with the clients and stakeholders. I could write a book on the amount of times i've seen this work beautifully. I could write 10 books on how many times i've seen projects ruined by companies keeping developers in silos and behind layers of communication.
Software design at it's best is an iterative process.. this means involving everyone in the decision making. I think having BAs who don't understand tech who hand down tasks to be turned into code is wrong... tech decisions are better made at the same time as features and ux.
If the devs know the domain they will come up with much better solutions most of the time .. i see this constantly... plus the more you keep your devs isolated the more they think about tech and the less they think about pragmatism and business value.
On your other point, I do agree that it is highly beneficial to have managers who have a computer science background, although in my experience most of the time it's better not to have a manager at all... or if you do, one that actively codes and is more of a mentor than an authority figure.