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