Re:How to reward skilled coders with something other than pe...
by solistice on Saturday November 22, 2014 @01:47AM
(#8644990)
So essentially managers are people sysadmins. They make sure everyone is working, try to resolve conflicts and ideally make sure that everyone is running the right tools. What would be a people engineer in that vein?
[ Parent
| on HN ]
Re:How to reward skilled coders with something other than pe...
by jghn on Saturday November 22, 2014 @12:41PM
(#8646098)
Yes. Although in my case when I was talking about my 'best managers', they were also the people who were brilliant and were really good at the tech side too. These people all just had a natural ability to navigate through the political BS while still being extremely competent software folks.
Re:How to reward skilled coders with something other than pe...
by solistice on Saturday November 22, 2014 @01:01PM
(#8646138)
Looks like those people were truly "full stack". From the tech layer to the interdepartmental layer.
Re:How to reward skilled coders with something other than pe...
by jghn on Saturday November 22, 2014 @01:20PM
(#8646189)
Yes, as much as I hate that term it really does apply here. And I'm really only thinking of 2, maybe 3 folks. These were the people who managed to be the most productive members of the team while dealing with all of the manager BS. When you find one of those you do what you can to stay under them.
Re:How to reward skilled coders with something other than pe...
by alttab on Saturday November 22, 2014 @12:37PM
(#8646083)
Mentors and leaders.
Re:How to reward skilled coders with something other than pe...
by blumkvist on Saturday November 22, 2014 @04:01AM
(#8645164)
HR.
Re:How to reward skilled coders with something other than pe...
by chitresh on Saturday November 22, 2014 @05:23AM
(#8645267)
Nope. Those would be teachers and trainers.
Re:How to reward skilled coders with something other than pe...
by solistice on Saturday November 22, 2014 @08:07AM
(#8645476)
So to continue the IT parallel, that'd be setup (hiring and training) and maintenance/debugging (hr complaints and problem resolving) imo. My personal hunch would be that viewing the whole thing in a systems context, the EOs would be engineering. After all, they decide how the company is run at a top level, and either assemble a functioning "people stack" or set guidelines for doing so. In that vein, components/prospective employees are churned out by the education system as a broader whole, and the raw material for that...alright, i think that's taking the metaphor far enough.