News for hackers. Stuff that matters.
Re:Employee #1: Tumblr by romanhn on Wednesday August 10, 2016 @10:29PM (#12265999)
Nobody at Tumblr was gonna turn to me and be like, “Dude, you’re working too many hours, chill, take time, sleep.” No one ever turned to me and said that, ever.

That's just sad. I wish more people did say this - everyone loses when a colleague burns out.

Re:Employee #1: Tumblr by wott on Wednesday August 10, 2016 @11:20PM (#12266140)
Oh, there are managers who learned their managing lesson that they should show care for the employees and will tell them this very sentence.

... And at the same they remind you about the deadline twice a day, ask you for an estimate thrice a day, and tell you should speed up because you won't be allowed to miss the deadline.

This is worse than just putting pressure on someone. This kind of contradictory orders, of double binds, drives you crazy. Not only are you now afraid of failing the deadline, but you are also afraid of failing the 'hours check', for you know pretty well that they are incompatible.

It also shows that the first advice was just fake, they don't give a damn about it, they just read somewhere that a good manager should say that so they say that, but they have no intent to build up the conditions so that it can happen.

Re:Employee #1: Tumblr by smcl on Thursday August 11, 2016 @05:25AM (#12266986)
I have had this and it drives you insane. For some reason it caused me to start thinking of my holidays as yet another task I had to do, but didn't have time for - and instead of being a relaxing thing to look forward to became stressful "issue" I didn't want to handle
Re:Employee #1: Tumblr by _pmf_ on Thursday August 11, 2016 @04:18AM (#12266844)
> That's just sad. I wish more people did say this - everyone loses when a colleague burns out.

If some (single, without family) colleague does this, I usually assume he/she just likes his job very much (I worked a lot more, unpaid at home, when I did not have children, and enjoyed it). It's not always externally visible that this causes problems for the colleague, and it's a bit patronizing to assume that the guy/gal has a problem with it.

Either you have a toxic environment, in which case everyone suffers the same, or you have a non-toxic environment where it's more or less up to you how much you work. If it's the latter, please don't put responsibility on your colleagues for your work load. If it's the former, due to the fact that it is an employer's market (despite what some shills try to tell you), you only have the option to leave.

Re:Employee #1: Tumblr by rebeccaskinner on Thursday August 11, 2016 @08:54AM (#12267796)
A couple of companies ago I was the lead developer working mostly with people who were early on in their careers, single, and wanting to put in a lot of time. Even then I always advised them that programming and solving problems is fun, but they should find side projects or something and not spend all that extra effort on work projects. Even if they start doing it because of passion it can ruin things at work because it gives the managers a very poor sense of scale and estimation (because it's hard enough to estimate when you don't have to think about how interesting a given developer will find a problem as part of calculating velocity), it sets expectations on them that they really don't want to have (people start to count on your long hours even if you suddenly have something else going on in your life) and finally fresh ideas and new perspectives are the lifeblood of a team, so having people doing their own thing outside of work and bringing in those things is way more valuable than getting that one project done a little early.
Re:Employee #1: Tumblr by PJDK on Thursday August 11, 2016 @07:23AM (#12267322)
I run a smallish team (6 including me) at a startupish company (as in it's quite small with growth ambitions, but the nature of the industry means it's never going to be worth much more than $40m even in the best case.

I say this sort of thing - not that often because people have taken it on board. As far as I'm concerned it's just best practice. Sustained crunch style working doesn't make you go any faster - bugs, burn out, turn over they'll all kill any short term gains you might get. If someone is being pressured into running a team into the ground, they have a professional duty to push back against that - it's in the best interests of all concerned.

I also feel that it makes it much easier to ask people to work longer if some emergency does come up that can't wait (bug in production or something like that - we get this maybe 3-4 times a year and it generally means a couple of late days getting it sorted).

I'm not sure why anyone thinks "this time the death march might work!"

Re:Employee #1: Tumblr by skybrian on Wednesday August 10, 2016 @11:07PM (#12266106)
Well that's the thing about salaried jobs: if they're not watching you fairly closely, how would they know how many hours you're working?
Re:Employee #1: Tumblr by glenda on Thursday August 11, 2016 @01:41AM (#12266454)
Companies shouldn't hire employees they don't trust. They may choose to watch out for bad behaviour (i.e. not answering emails when expected), however employees should never need to be watched at the level you're suggesting.
Re:Employee #1: Tumblr by romanhn on Thursday August 11, 2016 @02:15AM (#12266558)
I interpreted that comment as a question of how can we know that someone is working too much (and therefore should be concerned) if we don't know how much they're actually working.
Re:Employee #1: Tumblr by glenda on Thursday August 11, 2016 @11:42AM (#12269127)
Ah yes, that is a lot harder to detect. I think in that case minimum required vacations are a great way to make sure your employees take some time off.
Re:Employee #1: Tumblr by megablast on Thursday August 11, 2016 @04:59AM (#12266945)
Oh of course. Companies should only hire perfect people.
Re:Employee #1: Tumblr by glenda on Thursday August 11, 2016 @11:41AM (#12269123)
Of course not, but you should at least trust the people you hire!
Re:Employee #1: Tumblr by romanhn on Thursday August 11, 2016 @12:03AM (#12266250)
It's not an exact science, but there are plenty of artifacts one would tend to leave around when working extra hours - late night emails, chat messages at odd hours, code commits or comments, whatever.

Don't let it become a pattern. Outside of being unhealthy for the individual involved, it can be quite detrimental for the team. Managers especially can set unhealthy expectations without any conscious intent on their part.

Re:Employee #1: Tumblr by rtpg on Thursday August 11, 2016 @07:17AM (#12267305)
Isn't the point of being salaried is you're being results-based instead of hourly based?

Granted, there's an implicit agreement to do "40 hours" (or whatever the norm is), but that they're paying you for what you produce, not for how many hours you're in the seat.

Re:Employee #1: Tumblr by skybrian on Thursday August 11, 2016 @11:30AM (#12269028)
Yes, the point is that if nobody is watching you, it's up to you to set your own limits on work hours. You can't expect someone else to do it.