This is the Century of Consequences. You can check out, but you can't leave.
Domestic appliances were extremely disruptive. (vacuum cleaners, fridges, washing machines, air conditioners, ...) Domestic servants were eliminated. But there was no paradigm shift.
People still live in houses and prepare and store food, and clean their houses and clothes. Minor tasks of domestic servants (making beds, tidying, etc.) were folded in to the job of the homemaker, who was demoted from a supervisory role.
Mainframe computers emptied out accounts departments in large companies, eliminating invoicing clerks, general ledger clerks, stock control clerks, payroll clerks and many more specialised roles. No paradigm shift. Accounting is still accounting.
Typing pools were emptied by the introduction of the Lasrjet printer and the personal computer. Their minor tasks (spell-checking, grammar correction, etc.) were taken over by other people. No paradigm shift, just a task automated.
Telephone operators were eliminated by automatic exchanges (central and customer-premises). No paradigm shift, that came later with digital radio phones ("smartphones"), and didn't cause wholesale job elimination.
The binary distinction between task replacement and paradigm shift is flawed. Reality is much more varied and fluid.
Domestic appliances killed domestic service jobs.
Telephones killed messenger-boy jobs.
The automatic telephone exchange killed telephone operator jobs.
Movable-type presses killed the job of scribes despite the huge expansion in book production.
Various farm machines together killed arable farm labour.
The Laserjet and Wang word processor killed typist jobs.
Mainframe computers killed invoicing clerk, general accounting clerk, and inventory control clerk jobs.
We could go on.
In each case, the minor tasks in each job that were not automated were just folded into other jobs.
Focusing on ATMs and claiming no impact is egregious, tendentious cherry-picking. Machines almost always eliminate occupations.
> they're paying for someone to _figure out_ their exact needs,
Back in the 1980s this was called "systems analysis". The role disappeared a bit before the web came along, and coders were tasked with the job or told to just guess what the exact needs are, which is why so much software is trash.
I don't know, though, Claude Opus is most of the way to being a good systems analyst, and early reports say that having an AI provide descriptions/requirements to a fleet of code-writing AIs gives better results than having a human do it.
This project is an enhanced reader for Ycombinator Hacker News: https://news.ycombinator.com/.
The interface also allow to comment, post and interact with the original HN platform. Credentials are stored locally and are never sent to any server, you can check the source code here: https://github.com/GabrielePicco/hacker-news-rich.
For suggestions and features requests you can write me here: gabrielepicco.github.io