I leave it unless there's something I was planning on doing like wfh the next day or work a tad over the weekend.
It's weird for me individually since I walk, though, so either I have a much heavier backpack or I'm carrying a laptop through the city. So I try not to do it much :P
It's a big company, so there's a mix of people who always take it home in case they get sick overnight and want to wfh and people who will never ever take it home. And the people who take it home to do all their code reviews and such at midnight since they think 9-5 has to be "real" coding work.
Former Java engineer turned Ruby engineer who is trying to understand Ruby and Rails, MacOS and a lot of other things. Worked at Flywheel, FNBO, ACI Worldwide.
It seems the more senior people on my team have issues adjusting to the changing job descriptions as they level up, so they want to engineer for 8 hours, not do reviews or interviews or scrum meetings and then code for 2 or whatever is left. So they get burnt out doing the non-directly-engineering work and 8 hours of coding on top and quality suffers.
Former Java engineer turned Ruby engineer who is trying to understand Ruby and Rails, MacOS and a lot of other things. Worked at Flywheel, FNBO, ACI Worldwide.
I could see that happening with burning out on a schedule like that. When I was tech leading team, I had zero time for actual coding tasks. Just scrum, meetings, code review, mentoring and planning. Definitely not how I wanted to spend my day all day, every day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I leave it unless there's something I was planning on doing like wfh the next day or work a tad over the weekend.
It's weird for me individually since I walk, though, so either I have a much heavier backpack or I'm carrying a laptop through the city. So I try not to do it much :P
It's a big company, so there's a mix of people who always take it home in case they get sick overnight and want to wfh and people who will never ever take it home. And the people who take it home to do all their code reviews and such at midnight since they think 9-5 has to be "real" coding work.
That feels like a discussion topic all on its own, whether or not code reviews are "real" coding work.
Yeah, I have my issues with those types :)
It seems the more senior people on my team have issues adjusting to the changing job descriptions as they level up, so they want to engineer for 8 hours, not do reviews or interviews or scrum meetings and then code for 2 or whatever is left. So they get burnt out doing the non-directly-engineering work and 8 hours of coding on top and quality suffers.
I could see that happening with burning out on a schedule like that. When I was tech leading team, I had zero time for actual coding tasks. Just scrum, meetings, code review, mentoring and planning. Definitely not how I wanted to spend my day all day, every day.