Yep. I think the author fails to understand that coding is only a small part of the process of writing production software.
As the old saying goes, "you can save hours of planning by doing weeks of coding."
You then have to spend a significant amount of time trying to guide people to focus on the right things. And that is draining.
- the code, obviously
- infrastructure
- documentation
- wireframes, mock ups
- user manuals?
- monitoring
- ...
Software engineers shouldn't be the ones who address all the points above (otherwise that leads to burned out developers like the author).