The current generation is throwing a massive slop grenade at the next. Here, catch!

Technically, you can use an LLM to learn what code does, how a function works, why some convoluted workarounds are necessary, etc. If you really take the time to do that, you should also add lots of relevant comments to the code, something the LLM certainly won’t do. When you look at the code two weeks later, you’ll still be able to debug it on your own or tell an LLM to carry out very specific tasks for you. Either way, this route takes time and effort, which is why most won’t do it. The temptation to skip vital steps is too great. That’s how we’re currently driving to a software maintenance dead end.

Sooner or later, the code is such a mess that you can’t fix it by throwing more AI at it. Humans have to understand exactly what the code does and why it works that way. When people start dealing with these slop grenades every month, they realise how important it is to have proper guidelines about using LLMs responsibly. It’s about time someone starts teaching these guidelines that haven’t been written yet