I think you’re right here and it’s the same reason I see AI as a tool in the software profession. You can use it to speed up your work, but you have to have someone fully trained who can tell the difference between looks good but is wrong, versus is actually usable.
I’ve been using copilot for half a year now and it’s helpful, but often wrong. I carefully verify anything it gives me before using it. I’ve had one bug that made it to production where I think copilot inserted code that I didn’t notice and which slipped past code review. I’ve had countless garbage suggestions I ignored, and a surprising amount of code that seemed reasonable but was subtly broken.
This will still require a human lawyer (and/or intern, depending on the stakes) to check its output carefully. I am not now, nor have I ever been afraid that AI is coming after my job. When it does, we’re dangerously close to general AI and a paradigm shift of such magnitude and consequence that it’s called The Singularity. At which point we may have bigger worries than jobs.
I’ve been using copilot for half a year now and it’s helpful, but often wrong. I carefully verify anything it gives me before using it. I’ve had one bug that made it to production where I think copilot inserted code that I didn’t notice and which slipped past code review. I’ve had countless garbage suggestions I ignored, and a surprising amount of code that seemed reasonable but was subtly broken.
This will still require a human lawyer (and/or intern, depending on the stakes) to check its output carefully. I am not now, nor have I ever been afraid that AI is coming after my job. When it does, we’re dangerously close to general AI and a paradigm shift of such magnitude and consequence that it’s called The Singularity. At which point we may have bigger worries than jobs.