I think you make a good point. There is an issue of people talking over each other. The reality is, we don't all do the same work. It's possible my job and someone else's involves having to deliver very different code where the challenges to it differ.

One person might feel like their job is just coding the same CRUD app over and over re-skinned. Where-as I feel my job is to simplify code by figuring out better structures and abstractions to model the problem domain which together solve systemic issues with the delivered system and enables more features to work together without issue and be added to the system, as well as making changes and new features/use-cases delivery faster.

The latter I find a creative exercise, the former I might get bored and wish AI could automate it away.

I think what it is you are tasked with doing exactly at your job will also mean that your use of agentic AI actually makes you more productive or not.

I think we are all working without data here, it's all conjecture.

I went with OP's hypothesis that you are not faster, you throw things at the wall, wait, and see if it sticks, or re-throw it until it does. This reduces your cognitive load, but might not actually make you more productive.

I'm assuming here that "you are not more productive" already accounted for what you are saying. Like in a 8h day, without AI, you get X done, and with AI you also get X done, likely because during the peak productivity hours of your day you get more done without AI, but when you are mentally tired you get less done, and it evens out with a full day of AI work.

There's no data here, it's all just people's intuition and impression, not actually measuring their productivity in any quantifiable way.

What you hypothesize could also be true, it the mental load is reduced, can you sustain a higher productivity for longer? We don't know, maybe.

Someone proved that there is market demand which could make it profitable.

In the past, there was not much reasons to go into space, commercially, so who would have paid for it? But today there are many more use-cases for sending things to space that are willing to pay for the service.

Exactly, that's what I'm saying. Commit AI code under its own name. Then the code under your name can use the AI code as a black box. If your code that uses AI code works as expected, it is similar to when using libraries.

If you consider that AI code is not code any human needs to read or later modify by hand, AI code is modified by AI. All you want to do is just fully test it, if it all works, it's good. Now you can call into it from your own code.

If I follow what you are saying, employers won't see any benefits, but employees, while they will take the same time and create the same output in the same amount of time, will be able to do so at a reduced mental strain?

Personally, I don't know if this is always a win, mostly because I enjoy the creative and problem solving aspect of coding, and reducing that to something that is more about prompting, correcting, and mentoring an AI agent doesn't bring me the same satisfaction and joy.