>>Experienced developers develop fluency in their tools
>>You can see that right?
I get it, but this as big a paradigm shift as much as Google and Internet was to people in the 90s. Some times how you do things changes, and that paradigm becomes too big of a phenomenon to neglect. Thats where we are now.
You have to understand sometimes a trend or a phenomenon is so large that fighting it is pointless and some what resembles luddite behaviour. Not moving on with time is how you age out and get fired. Im not talking about a normal layoff, but more like becoming totally irrelevant to whatever that is happening in the industry at large.
That could totally be something that we encounter in the future, and perhaps we'll eventually be able to see some through line from here to there. Absolutely.
But in this thread, it sounds like you're trying to suggest we're already there or close to it, but when you get into the details, you (inadvertently?) admitted that we're still a long ways off.
The narrow-if-common examples you cited slow experienced people down rather than speed them up. They surely make some simple tasks more accessible to inexperienced people, just like in the translation app example, and there's value in that, but it represents a curious flux at the edges of the industry -- akin VBA or early PHP -- rather than a revolutionary one at the center.
It's impactful, but still quite far from a paradigm shift.
From actual software output it seems to me like the big SaaS LLM:s compete with Wordpress and to some extent with old school code generation. It does not look like a paradigm shift to me. Maybe you can explain why you're convinced otherwise.
Some quite large organisations have had all-hands meetings and told their developers that they must use LLM support and 'produce more', we'll see what comes of it. Unlike you I consider it to be a bad thing when management and owners undermine workers through technology and control (or discipline, or whatever we ought to call the current fashion), i.e. the luddites were right and it's not a bad thing to be a luddite.
I very much want to include more ai in my workflows. But every time I try it slows me way down. Then when people give examples like yours it feels like we are just doing different tasks all together. I can write the code you mention above much faster than the English to describe it in half a dozen languages. And it will be more precise.
Perhaps the written word just doesn’t describe the phenomenon well. Do you have any goto videos that show no -toy examples of pairing with an ai that you think illustrate your point well?
> can write the code you mention above much faster than the English to describe it in half a dozen languages
Especially if you’re fluent in an editor like Vim, Emacs, Sublime, have setup intellisense and snippets, know the language really well and are very familiar with the codebase.
Which were all tools I had to learn and slowed me down while I was learning them. So I’m extremely sympathetic to the idea that ai can be a productivity enhancer.
But those had obvious benefits that made the learning cost sensible. “I can describe in precise English, a for loop and have the computer write it” flat sounds backwards.
>>You can see that right?
I get it, but this as big a paradigm shift as much as Google and Internet was to people in the 90s. Some times how you do things changes, and that paradigm becomes too big of a phenomenon to neglect. Thats where we are now.
You have to understand sometimes a trend or a phenomenon is so large that fighting it is pointless and some what resembles luddite behaviour. Not moving on with time is how you age out and get fired. Im not talking about a normal layoff, but more like becoming totally irrelevant to whatever that is happening in the industry at large.