Assuming the current way to become senior is the only way?
I could still see a select few being given a foot in the door and leaping over the "argh why doesn't it compile" stage, past the "argh, I need a whole new architecture" stage to become senior in a few years. Every cohort has a few unicorns.
Alternatively, coding goes the way of the calculator. By that I mean, the people that used to be part of the engineering team, doing arithmetic. You just hire domain experts and give them the AI hoping the domain expertise is all you need to get you through the day.
Finance has historically had a lot of people who thought they could code, now perhaps they will get better. Big risk of it becoming a mess larger than back when they got VBA.
I don't see "senior vibe coder" going in any way that doesn't end in constant forest fires that they try to put out with a flamethrower. This happens even with seasoned engineers. Unicorn hunting for the exceptions will be every bit as infeasible in 2045 as it was in 2005.
> You just hire domain experts and give them the AI hoping the domain expertise is all you need to get you through the day.
what domain experts? Clearly they are trying to replace everyone with AI. That's the unsettling part of the whole story; this phenomenon is happening across many sectors who want to try and skimp out on talent.
I'm thinking that the calculator analogy is better and better
An LLM will produce a solution for you, but in most cases you need to know enough about the problem to ask it to apply the right tools. Or even have enough "known unknowns" that you can direct it to search for a better solution.
Like a trivial example: an LLM will happily write a CLI argument parser from scratch. It WILL work. It'll also be complete crap UX wise.
But if you know that a specific library (Cobra, Kong, urfave/cli) fits this specific problem better, you can ask it to use it specifically.
Same with calculators - it'll always tell you the correct answer to whatever calculation you give it. But YOU need to know that this specific problem was solved by a really smart person 100 years ago and there's a formula you can apply to solve it faster - still using the calculator, but now you're using refined algebra instead of brute-forcing a solution
1) that the tools become more Socratic and interactive and educational and walk the engineer through what they're doing
2) juniors pair with a senior who is using the tool and see the process and the decisions being made.
I know the industry wants these things to replace us, but in fact it's more like a power drill than a spinning jenny. It augments and lets the existing craftsmen work better faster, but does not replace / automate really.
>I know the industry wants these things to replace us
sadly, "The market can stay irrational longer than you can stay solvent". It will correct itself long term, but the damage over the last few years will linger for years, maybe even decades to come.
Idk I honestly feel like it makes junior developers more valuable. Junior are devs are often a cost as make as an asset, cause they take a lot of time and attention away from senior devs.
Now a junior can ask an AI like 90% of questions that would otherwise occupy a senior:
- Why does this dockerfile copy these files first?
- how can I find the entrypoints to this service?
- is there anything related to image processing in this entire project?
LLMs let juniors punch above their weight, and it lets seniors go faster. Of course if everybody is twice as efficient, you don’t need as many devs (debatable), but I don’t think junior devs are going anywhere. I hear a lot of CEO hype posts saying junior devs are outdated, but idk it doesn’t make any sense to me!
I could still see a select few being given a foot in the door and leaping over the "argh why doesn't it compile" stage, past the "argh, I need a whole new architecture" stage to become senior in a few years. Every cohort has a few unicorns.
Alternatively, coding goes the way of the calculator. By that I mean, the people that used to be part of the engineering team, doing arithmetic. You just hire domain experts and give them the AI hoping the domain expertise is all you need to get you through the day.
Finance has historically had a lot of people who thought they could code, now perhaps they will get better. Big risk of it becoming a mess larger than back when they got VBA.