I tend to call this "first job syndrome" where someone is so eager to please / perform that they take their work with them and tend to work on a project 24/7 until it is completed. I have never seen this behaviour with anyone who has moved onto a second or third software job, hence why I have given it this title.
What happens over time is that the person starts to "burn out" usually rather quickly, which leads to mistakes and sloppy work .
More often than not this will lead commit logs to source control having messages such as " committing to get my work home" , and a blurred line between what should and should not be committed to the repository. Debug code gets committed , half implemented features get committed , things get treated as "complete" when the code works ( and not when a clean maintainable solution is finished )
I tend to find that this practice lingers the longest with the less competent programmers, and in some cases the "first job" lasts for a decade and this is another topic in itself .
Over time a resentment starts to build up with people that take a more disciplined approach, being constantly tired due to chasing a bug until 3am the night before leads to daytime grumpiness and reduced productivity.
I have found that the optimum time for productivity tends to be somewhere between 30 and 40 hours a week. Too much less than that and you don't get decent sprints, too much more and you tend to start to make mistakes which in turn cause more work to be created.
I am not saying that one should completely avoid "crunch time" prior to releases , but one ( and most importantly management ) should understand that for every hour spent past a certain threshold will cost 3 or 4 in the longer term productivity wise, ( so 3 weeks of 60 hour crunch balances itself out with 4 weeks of effective zero productivity afterwards )
At a worst case scenario this could even be seen as a norm or even have a less competent programmer appear to be more competent than they really are due to the fact that they are more likely than not brute forcing solutions )
The only advice I can offer is to call it out for what it is, make sure management know what's going on ( and from their perspective they will be rightly pissed that there are hours of work which could be customer billable which are not being billed )