logoalt Hacker News

al_borlandtoday at 2:57 PM0 repliesview on HN

I use AI for small, stand-alone utilities, with limited risk/impact. These are things I make for only myself to use.

For anything something else will use, this is a real problem you can’t simply wave away.

> AI “writes bad code,” “introduces bugs,” “creates technical debt”

Bad code is hard to maintain, for the AI as well. While all code eventually becomes technical debt, the throw-away nature of AI code, and the sheer volume it creates, tends to turn it to technical debt more quickly. If code is “cheap”/“easy”, and the AI is bad at maintenance, why not do a full re-write for every update?

Bugs are bad for users and harder to find when you don’t have a deep understanding of the code. Logic bugs are the worst of these, because the AI and linter won’t necessarily find them. Some logic bugs can cause a lot of real world issues before they are reported and found. If doing a full re-write for updates, because the AI doesn’t care, each run is an opportunity for new bugs to get injected into the code.

If I’m expected to understand and answer for the code when there are issues, I need to be able to read and understand it, not just deploy quickly.