The principal coin of the realm in software development is developer's time.
Consequently, a majority of significant software management, whether it's admitted or not, is spent trying to control what developers work on.
Under this definition, developers do a lot of software management, in the form of fighting over what task they get to work on, how they do it, etc.
If a certain personality type of developer doesn't like a task they've been assigned, they can find other things to do, get someone to agree these things are more important, then they have license to stonewall the original task. You see this pattern often in many different contexts, and it seems to relate more to an individual person's working style more than culture or circumstance.
In my experience, regardless of their experience or overall technical abilities, developers who tend to stonewall are significantly less effective than those who don't, with a markedly lower contribution.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment