Hacker News new | ask | show | jobs
by QuantumNoodle 22 hours ago
Some of the code bases I have at work are legacy spaghetti -- hard to reason about. I too employ the prompt and pray strategy and then see if CI fails. I can only be surgical where I already have a grasp on the codebase, or if I was involved from the beginning.

Morally, I dislike what AI is doing to the profession. Rigor is suffering.

1 comments

It's also possible to point the AI at legacy spaghetti and say "document this in detail" as a starting point for unspaghettifying it.
But won't it take a lot of time and resources to make it non legacy? Sometimes we don't get the luxury or option to work on stuff like this