Nope, the vast majority of s/w grunts deliver good code at an break neck rate, and with quality. That is the nature of most s/w jobs. We never get the time we need based on a 40 hour week and have to crunch it near delivery time.
The non-s/w person does not realize just what a s/w grunt does to get the job done, and it is not surprising.
Been in the s/w business slinging code since the 80s. Defense, semiconductor, telecom, and high tech. Never done business as I was computer science grad. Done avionics, black programs, embedded, robotics, VoIP, AIN, distributed and been doing Cloud server based now for a while.
Working long hours and delivering good quality code that gets the job done is accomplished all the time by s/w grunts. I've had projects where we worked a month for 10 hours every day (required by mgmt), weekends included, to get the release out on time. And it was not paid as we are exempt. But we did it for pride of job, commitment to each other, the company and the customer. And then it would happen again, and again. Nature of the beast. Don't like it, then leave. Seen s/w directors and managers collapse at the office from exhaustion. After getting rested, they come back.
While this is common with working new development, new technology or integrating new hardware, it also happens with legacy systems.
The 5 X 9s mission critical reliability s/w for military, police, hospitals, ATC, is far more difficult than coding a media platform, and it is done by far more s/w grunts than media platforms.
Any competent s/w grunt, science or business, degreed or non-degreed, can join that twitter shop and tear apart that code and figure out what is under the hood and start cranking out new releases and patches in a short time. Its not brain surgery, just hard work.
Heck, I would bet there are some on this board that could be productive day one at that shop, much less a week or month.