Okay, go hire an accountant who only knows how to use a calculator - no formal training. Should be fine, accounting is just maths and a calculator is a tool to do maths with.
And honestly, even this analogy is too generous, because at least to use a calculator you have to know what the symbols mean. Vibe coding doesn’t even require that much.
Honestly, a calculator isnt even a fair comparison. A calculator can be reverse-engineered and proven to produce a certain output from a given input. Even scientists say AI is a black box. It cant be given any guarantees to what it will produce.
Would you hire an accountant that doesnt know how to use a calculator and can only do work by hand.
First of all, you don’t want to talk about analogies missing marks and then pull something like this. You didn’t just miss the point, you missed the barn wall behind the point.
The whole point of the article is that the new generation of developers won’t have the skills to spot the errors the AI makes. So, in your analogy, the accountant already has the skill and experience to know what to ask and fix mistakes the tool makes, and they can figure out how to use the tool, they’ll just be slower than without it.
In my analogy, we have an accountant who was trained to use the tool, not to do the work, which is exactly what’s happening in development now. Their work will be subpar and will run into blockers constantly because the tool gets stuck in a loop and the “developer” using it can’t code well enough to tell what it did wrong.
So, to answer your question: If the calculator was known to consistently confidently make shit up and leave glaring errors in its work, yes, I would absolutely hire a competent professional who doesn’t use one over a cookie-cutter vibe-numberer who can’t do it without one. Similarly, I’m not going to hire someone who can’t use a search engine without help either.
Well yeah. Lots of professions that used to exist just don’t anymore because of that stuff, or at least only exist as a small niche where before they employed tons of people. Like “computer” used to be a job people had doing math by hand.
WTF this thread is wild. These people literally think 100% of dev jobs need full stack software architect level expertise and also that code can only have two states: correct or incorrect. LOL
That’s a nice strawman you built there, but it’s wrong. The issue is not that “every dev needs to be a senior dev to use AI” nor is it “code is binary: right or wrong” (🥁). The whole point of this article is that new developers are entering the industry but they’re not building the skills that would eventually forge them into senior devs. They’re relying on generative AI for the foundational work, even when assigned a learning exercise by a senior dev, without understanding the “why” behind the output of the LLM they used.
The articles point is correct that’s not what I am saying, it’s what you guys spiral into LOL. „Let’s not use AI cuz it can be wrong sometimes“ „I’d rather have no AI than ‚wrong code‘“ just yesterday (as if it was called for) a YouTuber put out a piece that is making fun of you for that very reason.
So you’re just going to repeat your strawman bullshit as though that makes it what I said?
le kek the article is right but you and everyone agreeing with it are wrong
Juniors using AI means they don’t develop the necessary skills to become seniors. Seniors using AI find their critical thinking and problem solving skills negatively impacted (https://www.mdpi.com/2075-4698/15/1/6).
I understand that empirical evidence isn’t really your bag and you’d prefer to bloviate at randoms on the internet to feel superior without having to work for it rather than learn to communicate or bother to understand anything you read, so now that I’ve reiterated my point - which is that the article is correct - twice for you, I’m going to block you so you can re-read what I wrote in the first fucking place and reconsider being such a twat.
Aaaaah yes mental offloading with AI and AI use in general are the same. That’s why a junior should never use AI at all - not for prototyping, not as legacy code - cuz he will be never becoming a real senior that way. Omg you guys just keep on giving
So does the same apply to mathematics and calculators? Tradespeople and power tools? Writers and spellcheck?
It’s a bloody tool, why are people so against it? The same crap happens whenever something new comes out ANYWHERE.
Okay, go hire an accountant who only knows how to use a calculator - no formal training. Should be fine, accounting is just maths and a calculator is a tool to do maths with.
And honestly, even this analogy is too generous, because at least to use a calculator you have to know what the symbols mean. Vibe coding doesn’t even require that much.
Honestly, a calculator isnt even a fair comparison. A calculator can be reverse-engineered and proven to produce a certain output from a given input. Even scientists say AI is a black box. It cant be given any guarantees to what it will produce.
Yes it does. People cant even use a search engine withlut help. If you dont know what to ask you dont know what youre looking for.
Just like your analogy misses the mark. Would you hire an accountant that doesnt know how to use a calculator and can only do work by hand.
First of all, you don’t want to talk about analogies missing marks and then pull something like this. You didn’t just miss the point, you missed the barn wall behind the point.
The whole point of the article is that the new generation of developers won’t have the skills to spot the errors the AI makes. So, in your analogy, the accountant already has the skill and experience to know what to ask and fix mistakes the tool makes, and they can figure out how to use the tool, they’ll just be slower than without it.
In my analogy, we have an accountant who was trained to use the tool, not to do the work, which is exactly what’s happening in development now. Their work will be subpar and will run into blockers constantly because the tool gets stuck in a loop and the “developer” using it can’t code well enough to tell what it did wrong.
So, to answer your question: If the calculator was known to consistently confidently make shit up and leave glaring errors in its work, yes, I would absolutely hire a competent professional who doesn’t use one over a cookie-cutter vibe-numberer who can’t do it without one. Similarly, I’m not going to hire someone who can’t use a search engine without help either.
If my calculator was wrong 10% of the time, but always produced a result that “felt” correct, that would be worse than not using a calculator at all.
Same thing for power tools or spell check.
Well yeah. Lots of professions that used to exist just don’t anymore because of that stuff, or at least only exist as a small niche where before they employed tons of people. Like “computer” used to be a job people had doing math by hand.
WTF this thread is wild. These people literally think 100% of dev jobs need full stack software architect level expertise and also that code can only have two states: correct or incorrect. LOL
That’s a nice strawman you built there, but it’s wrong. The issue is not that “every dev needs to be a senior dev to use AI” nor is it “code is binary: right or wrong” (🥁). The whole point of this article is that new developers are entering the industry but they’re not building the skills that would eventually forge them into senior devs. They’re relying on generative AI for the foundational work, even when assigned a learning exercise by a senior dev, without understanding the “why” behind the output of the LLM they used.
The articles point is correct that’s not what I am saying, it’s what you guys spiral into LOL. „Let’s not use AI cuz it can be wrong sometimes“ „I’d rather have no AI than ‚wrong code‘“ just yesterday (as if it was called for) a YouTuber put out a piece that is making fun of you for that very reason.
So you’re just going to repeat your strawman bullshit as though that makes it what I said?
Juniors using AI means they don’t develop the necessary skills to become seniors. Seniors using AI find their critical thinking and problem solving skills negatively impacted (https://www.mdpi.com/2075-4698/15/1/6).
I understand that empirical evidence isn’t really your bag and you’d prefer to bloviate at randoms on the internet to feel superior without having to work for it rather than learn to communicate or bother to understand anything you read, so now that I’ve reiterated my point - which is that the article is correct - twice for you, I’m going to block you so you can re-read what I wrote in the first fucking place and reconsider being such a twat.
Aaaaah yes mental offloading with AI and AI use in general are the same. That’s why a junior should never use AI at all - not for prototyping, not as legacy code - cuz he will be never becoming a real senior that way. Omg you guys just keep on giving