All nighters are extreme and an unsustainable idea, I learned as much in college. But I do sometimes put in long hours (maybe for a week or two at most) to push

All nighters are extreme and an unsustainable idea, I learned as much in college. But I do sometimes put in long hours (maybe for a week or two at most) to push through a project I really enjoy, solving a problem for the company that is technically fulfilling. I don't mind much as an employee that I don't own the upside, because I also don't own the downside. I get a lot of satisfaction having built a quality piece of software that the customers got real value out of. I've found the key is to not do this regularly. I view it like running. Normally, you gotta jog, that way you have the reserve strength to sprint when you really need it. Anecdotally, the place I work for in the US doesn't expect or even want people to work all-nighters, if a project is that under-resourced, it needs to be halted or more resources need to be allocated. Under-resourced projects always fail and waste a lot of time and money. This is only the culture I've observed at my engineering dept though, FWIW.