Right, because the promise the developer is making(in most cases) isn't to to stakeholders or the users but to project managers. If the PM can't fulfill their promises on time, that's on them. Their responsibility is to better estimate what can be reasonably done in a time frame, provide buffers where possible, and shield developers from the business responsibilities that go above them. PMs and stakeholders need to be able to adjust their expectations to reality, not punish their developers by working longer or harder, or by changing the makeup of their development team, because it's not the minutes-spent or # of lines of code that make a good product.

Beyond that, working extra hours and weekends is a bad idea. It should only be done out of desperation because working overtime can quickly become the expectation.

Granted, the lines can be pretty blurred at some companies, namely startups that give lots of responsibilities to their developers. But most non-startups seem to have more refined command structures.