3 ms·
> A developer that always leave at exactly 17.00 and adamantly refuse to come in on a Saturday, gives a very clear signal that they don't give a shit about the
by noir_lord 13y ago
> A developer that always leave at exactly 17.00 and adamantly refuse to come in on a Saturday, gives a very clear signal that they don't give a shit about the company, the product or the team. They're there to get paid.
If once in a while something crops up that requires staying after 5 then that is fine however the expectation should be that all the developers go home at 5pm
> While most employers realize that your work isn't (or should be) your single burning passion, it is very negative for team morale when one of the guys always flakes out when the clock hits 17 regardless of the fire in the kitchen.
If there are constant fires in the kitchen you might want to find out who keeps lighting them, if's not the guy leaving at 5 then I fail to see the issue.
> I knew a developer who always left at exactly 17.00, because "that's what they are paying me for". On several occasions, he deployed breaking changes to production five minutes before leaving. Other devs had to come in and work very late to get the system back online. While he is technically in his right to leave at 5, he causes his team much grief and as such is not an asset.
Pushing to production shortly before going home is a separate issue to whether he leaves on time or not, a developer leaving on time should be expected, a developer pushing breaking changes and leaving should not.
The other stuff I wholeheartedly agree with.
- oddevan 13y ago> Pushing to production shortly before going home is a separate issue to whether he leaves on time or not, a developer leaving on time should be expected, a developer pushing breaking changes and leaving should not. This. I strongly believe in finishing what I've started and not leaving things broken. I also strongly believe in work-life balance which to me means working hard until 5 but leaving then. EC1: If you're confident that your work ethic is sound, then there sounds like there's a significant culture mismatch here. I know it's not easy to think about going somewhere new, but you may have to consider that sooner rather than later. I honestly wish you the best of luck no matter how this shakes out.
- MortenK 13y agoYeah I might not have been entirely clear in my post, but I write: "The other side of the coin is that lots of software companies, really has little to no control over software development... This is a company where crisis' occurs daily or weekly instead of maybe once every couple of months." That's entirely agreeing with your point: The standard should be a well run team where everybody goes home after their 7-8 hours. If there is constant fire in the kitchen, then it's certainly not up to developers to constantly do overtime. In my post I do actually suggest to OP he gets out, if he is indeed in such a situation (which again, it sounds like).
- eitally 13y agoThe expectation should absolutely not be that everybody leaves at 5. Why not? Because the expectation shouldn't be that everyone arrives at 8:00:00. As white collar professionals, one of the perks we typically have is flexibility in setting some aspects of our schedules, whether that means taking a couple hours for an appointment, having untracked personal time versus a fixed PTO/sick accrual, or what have you. The flip side of this is that there should also be commensurate flexibility from the other party. Abuse either direction is unacceptable, but mandating precise work hours doesn't mesh well with humanity.