[kuschku]

Most jobs today don't need novel reasoning. This is the equivalent of the steam machine for intelligence.

During the industrialization, machines did not replace all jobs, but they replaced or changed most jobs. The same will happen here.

A typical office job will have a few hours a week of actual, intensive thought. The vast majority of time will be spent doing simple, repetitive work. This work can be automated, or at least significantly sped up, using technology like GPT.

“write an API client for …”, “integrate APIs … and …” can easily be automated. Yes, you'll still have to write the business logic, but that's not the majority of your work today. You could even have it write unit tests based on the JIRA ticket description.

The same applies to many other jobs.

[evouga]

> You could even have it write unit tests based on the JIRA ticket description.

This is a wonderful point: writing unit tests is exactly the kind of mind-numbing tedium that I'm super excited to automate away.

[joshspankit]

> Most jobs today don't need novel reasoning. This is the equivalent of the steam machine for intelligence.

Like the point above; that says more about the work.

It’s going to be really interesting how the middle-class narrative pushes back on AI revealing how little work is actually done during office hours.

[Aperocky]

These boilerplate code can be and are automated away using deterministic frameworks. No need to introduce a blackbox and be responsible to debug the stuff it creates, which sounds far more painful than the alternatives.

[kuschku]

That's true today, but think about all the work you do that takes basically no conscious effort, but is still not automated yet.

GPT can be of use there, as long as you're working with languages that use strict static types and have proper tests, it's easy to automate and ensure there are no mistakes.