Great post. I agree that a critical factor in why I'm getting good results from LLM-assisted coding is that _I know this shit_. I flag the model when it's going down the wrong path, and I include hints in my prompt that I know will steer things in the right direction.
If you don't know how to do that, you're getting shit quality output.
"It works today, because the people reading those docs have the engineering expertise to act on them. What happens when they don’t? Honestly, I don’t know. Maybe AI in five years is good enough that it won’t matter. Maybe the problem stays manageable. I can’t predict the capabilities of models in 2031."
https://techtrenches.dev/p/the-west-forgot-how-to-make-things
@troed This is the truth! I am trying to teach my students that they have to invest the time and manual labour in programming to build up their intuition of what works and what doesn't. With that intuition and experience, they will be able to use LLM:s profitably.
But skipping the basics, and going straight to vibe coding has the potential of doing more harm than good to the company they will be working for.
