Improve productivity so that we achieve more in less time so that we have more time for leisure on a daily basis.
https://en.wikipedia.org/wiki/Parkinson%27s_law
Completing tickets, issues or burning story points means next to nothing if the work you do is detached from reality. And that reality consists of an irrational humans with complex, contradicting demands and needs and an unpredictable future.
Moreover, if you work as an employee, you will spend 40-50 hours a week at the office regardless of how fast or slow you're grinding through the workload. Why? Because that's how salaried work is legally organized.
Then there's limited agency. The article assumes that programmers are free to arrange their schedule. But that's only true if you're an independent contractor who's not deeply embedded in a team. Most programmers - and workers in general - are subjugated to the authority of managers and specific workplace culture.
Trying to rally workers around the battle cry "let's improve productivity" without questioning to what end, well, that's just a bad take on Taylorism.
Then you take what you can do and leave the rest.
On my side I've saved lots of time by simplifying the tools I used, reducing the number of dependencies, frameworks and other stuff and writing simple, "childish" code.
I'm a web developer. I prefer to do simple Ajax, HTML, pure JS and simple CSS and a good framework such as Laravel. For 80% of the projects its enough to "do the job". If the client wants a "nice looking date picker" just go for the default HTML one, saves hours/days and the difference is minimal.
I've stopped looking for "new shiny" tools. In the end people are just looking for simple stuff that works.
Look at Hacker News for example. Minimalist. But "the job is done".
Having the intent to improve often destroys the process itself. It's very subtle and case-by-case, but a bit of leisure and leeway with work is good. I do like monitoring myself, but only if I am kind of just enjoying it? Not really trying to "improve" per se.