As if anyone cared if they had to wait a total of 3 seconds in a workday.
That depends on when it appears. Some tasks kind of have to feel instantaneous, and there might be a pretty slim margin between okay and frustrating.
But yeah, that's the kind of savings that mostly matter on the scale of regional or national grid planning.
Most engineers already write bloated, abstracted, glacial code that burns CPU cycles like a California wildfire. Clean code? Ha! You’re writing for other programmers’ academic circlejerk, not the hardware.
It’s interesting that everybody else preaches ‘Write for the human first, for the machine second’.
Yeah, the author seems to lean too hard into the "programming is electronics" model, where the opposing end is "programming is math and formal logic"; most of us take some mixed view. And most of us have higher correctness requirements than what a reasonable effort in memory unsafe languages like C and C++ gives us, so we trade away some machine efficiency. In the authors parlance, most of us aren't interested in the demoscene circlejerk; we need to make tradeoffs between maintainability and everything else. Write-once code isn't good enough.
There have been attempts at establishing a third pole of "promptgramming is natural language" or whatever ever since COBOL promised programming in plain English, but the ambiguity of natural language when used to encode a business logic machine means that a "sufficiently advanced compiler" will have to be extremely advanced, on the order of including the manager and the entire engineering methodology.
Ah yes, traditional urban cores, historically entirely without any good food options, either delivered, on the go, or even sit-down at odd hours