First you'll cut the bottom 10%, then the bottom 20% etc. The pie will only be shrinking.
The point is exactly that most of those meetings are happening everywhere for the same reason and thus GPT25 might already know all the answers that you need.
Also given enough general framework skills, I'm pretty sure the AI will be able to build stuff like a good junior dev.
It can generate something that looks like what a person would have wrote based on its compressed probabilities, but that's very different from being an "an artofficial intelligence". At best it's a Chinese Room.
Im pretty sure we could train an AI to suggest the correct API for the intended purposes. Given the fact that we have support of datatypes and documentation what is left to do is to map what you have to what you want.
Also we can reasonably generate classes and controllers already through cli, so why not combine all the nice things we have to something usefull.
Kubernetes is simply an api too
With some framework to compose various prompted endpoints using the same types and conventions, a junior engineer would be totally unnecessary. They couldn’t code as well, and they couldn’t architect as well as a more experienced engineer doing the prompting.
You could even prompt from a spec and begin iterating upon the outputs, revising each manually or with GPT’s suggestions. Say “take this endpoint and refactor it based on the conventions of this endpoint, and make sure (some logic) accounts for (some potential problem)” and boom, it will probably work okay.
If this technology evolves to be able to reliably generate working code to a prompt, the entire field of software dev will shift dramatically. Some junior and some senior devs would prove better at meeting deadlines by AI whispering, and others would have to find new career paths.
It affects both. If a single team was to be split with 5 juniors and 5 seniors, ChatGPT significantly reduces that headcount from 5 juniors to 0, and 5 seniors to 2 or 3.
With many companies cutting costs and with the cheap money getting dried up, no-one is safe. HN may not like it but, the same thing that has happened to digital artists with Stable Diffusion which was welcomed on this site, now has happened to programmers and I see lots of worrying and frowns everywhere.
It appears that StackOverflow (which lots of juniors and senior developers use) has just become irrelevant.
Citation needed. I haven't heard of any massive disruption in the commission art market since stable diffusion went public, and I don't think something less-impactful(a different way to search old stack overflow posts) is going to cause a massive disruption either.
Stack overflow still beats chatgpt in one area that it can never compete. Coming up with new solutions to new questions. If all we needed answered was the same questions, chatgpt would be sufficient since it's essentially a compressed version of our current knowledge. We don't really have a way to update it with "new knowledge" other than "train it again".
I once spoke to an illustrator who said her work was definitely shrinking due to low cost human competition, so much so that she was leaving her profession. I can imagine this did in fact get worse.
Luckily we're in tech, which doesn't work this way at all.
One thing about GPT is that it only knows what we know at the moment. That indicates to me that it won’t be great for learning new technologies until humans generate content it can regurgitate. That alone might give juniors an edge against it (assuming they are gradually replaced by a robot pooping out dumb logic) - they might be able to specialize in learning what models don’t yet know, or what they can’t be good at.
Just guessing here. I’d love to hear a rebuttal to get a sense of where people think things are going.
Though I don’t think GPT is “there” yet, I can see it getting there by 2030. I think it’s seriously worth considering: how will people learn to program in 10 years, how will they remain relevant through periods of their career where an AI can generate better solutions than they can, and how will more experienced engineers adapt to those changes?
Two things happened: one, blacksmithing effectively was taken over by a different skill, that of configuring, servicing and operating industrial machines. There were no junior or senior blacksmiths anymore, seniors probably migrated their knowledge, and the whole field was taken over by non-blacksmiths.
The other thing is that a small proportion remained. Initially perhaps for niche goods that were too difficult or uneconomical to automate. Now blacksmiths do exist, a bit like craft coffee blenders and horse trainers. But the industry was nonetheless wiped out.
Will we see that crafting software will become a job for people trained in AI whispering? Perhaps they will never, or hardly ever, write any code, but will train extensively in software design. Much as a metallurgy engineer might know all crystalline forms of steel but have never swung a hammer.
Day 1 these jobs would likely get filled by senior devs, but there may be no new devs, junior or senior, except for niche applications.
As many of us cannot read machine code and hex anymore many of the juniors won't be able to parse the code output - but it may not matter anymore.
ChatGPT+ will definitely have some affect on junior devs but us more experience folk should be fine... for now..