The AI coding divide: craft lovers vs. result chasers

Re:The AI coding divide: craft lovers vs. result chasers by ofrzeta on Friday March 13, 2026 @01:27AM (#47361017)

For the sake of argument let's assume we have a common goal: produce a software product that does its job and is maintainable (emphasis on the latter).

Now given that LLMs are known to not produce 100% correct code you should review every single line. Now the production rate of LLMs is so high that it becomes very hard to really read and understand every line of the output. While at the same time you are gradually losing the ability to understand everything because you stopped actively coding. And at the same time there are others in your team who aren't that diligent adding more to the crufty code base.

What is this if not a recipe for disaster?

[ Parent | on HN ]

Re:The AI coding divide: craft lovers vs. result chasers by antihipocrat on Friday March 13, 2026 @01:53AM (#47361116)

I think differences in the business determine whether the maintenance/understanding aspect is important. If developing an MVP for a pitch or testing markets then any negatives aren't much of a consideration.. if working in a mature competitive or highly regulated domain then yeah, it's important

[ Parent | on HN ]