3 ms·

> 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

by _pmf_ 10y ago

> 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.

rebeccaskinner 10y ago
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.

by _pmf_ 10y ago

rebeccaskinner 10y ago

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.