News for hackers. Stuff that matters.

A comment on Engineering productivity can be measured, just not how you'd expect. Parent comment

Re:Engineering productivity can be measured, just not how yo... by michaelt on Wednesday February 03, 2021 @06:40AM (#26012733)
> Based on what I've observed by studying successful open source projects, you actually want to discourage "very high impact" employees, since they introduce knowledge risk.

If you're trying to sell this concept to developers, you might want to change "discourage" to "hire more than one"

[ Parent | on HN ]
Re:Engineering productivity can be measured, just not how yo... by sdesol on Wednesday February 03, 2021 @11:37AM (#26015391)
Ideally you would like to hire more than one, but I think my use of the word "discourage", was not the right one. What I ultimately wanted to say was, you want a balanced team, where no individual development pattern sticks out.

A very high impact employee could easily be the result of having multiple poor employees, improper planning, and so forth.

[ Parent | on HN ]