This post goes into a lot of details about their point of view - that the programmer developing software has to run it a lot of times, so if it's inefficient (in terms of CPU cycles) it'll slow them down. I was hoping they'd quantify that, but they don't.
Overall their argument makes sense, but if the slowdown due to "too many CPU cycles" only has a practical effect in taking a few extra milliseconds overall then IMO the programmer isn't slowed down in any practical sense.
My impression is that the article author isn't aware that this system exists and is used in other democracies. It's used in Australia, and is pretty effective IMO.
I'm much the same. For me, though, the best all-nighters have come from when insomnia hits and I can't stop thinking about a bug. Then I cave in, get out of bed, and hack away.
It's essential to have a flexible employer though.
Overall their argument makes sense, but if the slowdown due to "too many CPU cycles" only has a practical effect in taking a few extra milliseconds overall then IMO the programmer isn't slowed down in any practical sense.