I just spent a week fixing a concurrency bug in generated code. Yes, there were tests; I uncovered the bug when I realized the test was incorrect...
My strong advice, is to digest every line of generated code; don't let it run ahead of you.
I just spent a week fixing a concurrency bug in generated code. Yes, there were tests; I uncovered the bug when I realized the test was incorrect...
My strong advice, is to digest every line of generated code; don't let it run ahead of you.
Of course yeeting bad code into production with a poor review process is already a thing. But this will scale that bad code as now you have developers who will have grown up on it.
I think this is the biggest risk. You sometimes get stuck in a cycle in which you hope the AI can fix its own mistake, because you don’t want to expend the effort to understand what it wrote.
It’s pure laziness that occurs only because you didn’t write the code yourself in the first place.
At the same time, I find myself incredibly bored when typing out boilerplate code these days. It was one thing with Copilot, but tools like Cursor completely obviate the need.
We humans have way more context and intuition to rely on to implement business requirements in software than a machine does.