So, I'm one of the more highly-skilled developers working on X. I'm also needed to help troubleshoot some emergency on Y for a week.
Someone has to figure out schedules priorities and whatnot. But I don't give a $#@% about that sort of boring people-stuff, because I only care about interesting technical problems.
How does this get handled?
.
People do not always follow the same process over and over again. When they do, that's an excellent candidate for automation.
People can have multiple interests and skill sets, but those won't always include negotiation and constraint optimization. Those tasks still have to get handled for everyone, even the people who won't handle them for themselves.
.
There will always be hierarchies. There are at least two fundamental ones: skill, and scope. Neither maps exactly to management hierarchies.
yes but we bundle a lot of things into the term management
hierarchy will always exist (if at least someone has to pay or fire you)
authority will always exist (if at least someone will be more experienced in a topic)
processes will always exist (and someone has to put them in place)
you can have processes in place for emergencies, deciding if those emergencies are worth dropping stuff, for boring bugduties etc
the shift is imho not so much about making everyone his own boss but about pushing decisions as far as possible "down the chain" until you do no longer need to think in "hierarchy chains" but roles and groups of people
Someone has to figure out schedules priorities and whatnot. But I don't give a $#@% about that sort of boring people-stuff, because I only care about interesting technical problems.
How does this get handled?
.
People do not always follow the same process over and over again. When they do, that's an excellent candidate for automation.
People can have multiple interests and skill sets, but those won't always include negotiation and constraint optimization. Those tasks still have to get handled for everyone, even the people who won't handle them for themselves.
.
There will always be hierarchies. There are at least two fundamental ones: skill, and scope. Neither maps exactly to management hierarchies.
reply