mhoyeWhat if I could convince you that taking the same time to explain detailed requirements and carefully validate results with a junior colleague instead of a chatbot would not only give you two people who understood the code instead of zero, but if you do it a few times in a row you eventually get a senior colleague out of the deal for free.
Nicolas Rinaudo@mhoye so, don't get me wrong, I agree with you wholeheartedly and am making this argument regularly at work. But it's important to view the other perspective: an LLM will follow your instructions far, far faster than a junior developer. Hell, it will follow my own instructions far faster than *I* would.
It's hard to make the argument that speed is not the important metric here - to show that LLM-generated code is at best average, by definition. That a human gets better every single time they perform a task, in a way LLMs don't. That a trained junior can train other juniors, and if you do it right, you get exponentially more developers, where an LLM stays the same.
The problem is that:
- managers in our industry often care less about quality than about speed of delivery, because you can always fix later (which means, really, they'll have made a bundle and left before consequences must be dealt with).
- the asshole developer, which is unfortunately (in my experience) the majority of us, cares about feeling better than the rest, not about making everybody better.
josch