News for hackers. Stuff that matters.
Re:Things I have learnt as the software engineering lead of ... by knieveltech on Friday December 29, 2017 @04:10PM (#16032016)
"Being overworked is not a good reason to hire."

Because the world certainly needs more sociopathic management advice.

Re:Things I have learnt as the software engineering lead of ... by egor598 on Friday December 29, 2017 @04:29PM (#16032114)
The way I understood this: "If you are overworked, first look at your team, is everyone at their place and pulling their weight, evaluate your deadlines and promises, check your planning and management and your relationship with stakeholders. Because most of the times it's one of those things that's broken and probably affects the rest".
Re:Things I have learnt as the software engineering lead of ... by claudiulodro on Friday December 29, 2017 @04:20PM (#16032063)
Theoretically, it might not be a good reason to hire. Maybe the problem is bad planning or project management. Hiring more people won't really solve that.

But, in general, I agree with you.

Re:Things I have learnt as the software engineering lead of ... by mmcnl on Saturday December 30, 2017 @09:53AM (#16035454)
That's your (negative) take on it. You can do something about being overworked without hiring (evaluate deadlines and scope, learn to say no). There's a good chance that hiring people without establishing the underlying cause of "being overworked" will only lead to more people being overworked. If you're hiring because of "being overworked", you're hiring too late.
Re:Things I have learnt as the software engineering lead of ... by jayd16 on Friday December 29, 2017 @04:21PM (#16032076)
Rereading the advice, I think he means hire before you get to overworked. I agree it's phrased poorly.
Re:Things I have learnt as the software engineering lead of ... by ckip on Friday December 29, 2017 @09:32PM (#16033464)
I agree with his advice and not yours. Good candidates are a good reason to hire. Overworked is a good reason to reexamine priorities.