> The people I know who are like this are what I'd describe as "9-5" employees, don't learn anything outside of work, and basically do the bare minimum at everything.
If you're a creative person, like a developer, it's inefficient.
Context switching is expensive, and going home for the day is a big context switch.
If it's 5:00 and you have 30 minutes left on something, most likely it'll take something like two hours tomorrow to get back into and finish it.
If you always go home exactly at 5, it means you are either constantly being inefficient and doing the context switch, you are not doing anything late in the afternoon to avoid the context switch, or you are extremely good at both estimating and optimizing your time so all your tasks are quantized within working hours. While things may work out to look like the third case sometimes, I find it hard to believe anyone is that good that it can happen literally every day, which leads me to believe they're often doing one of the other two things.
And just to take this further: there's a massive context switch for the dev team when a burned out developer leaves after 1-2 years, compared to the 9-5 dev who's still there and happy.
From your perspective or the company's perspective?
From the company's perspective an unmotivated 9-5 employee not as good of a hire as one who deeply enjoys the work subject and actively learns about it on their own.
From your perspective reduced job security because you probably don't perform at the level of someone internally motivated.
Even if that is not true there are enough of these sentiments floating around to affect decisions.
EDIT - If you disagree, a well worded comment carries more weight than a downvote and avoiding the discussion.
Context switching is expensive, and going home for the day is a big context switch.
If it's 5:00 and you have 30 minutes left on something, most likely it'll take something like two hours tomorrow to get back into and finish it.
If you always go home exactly at 5, it means you are either constantly being inefficient and doing the context switch, you are not doing anything late in the afternoon to avoid the context switch, or you are extremely good at both estimating and optimizing your time so all your tasks are quantized within working hours. While things may work out to look like the third case sometimes, I find it hard to believe anyone is that good that it can happen literally every day, which leads me to believe they're often doing one of the other two things.