14
Coding with AI got messy until I changed my approach
For a while, I let AI tools write all my code because many say it's the best way. But I found the code was often hard to follow and full of odd choices. In one case, for a simple app, the AI made a function that broke when we tried to change it. So I began drafting the core code myself and only asking AI for tips on tricky parts. This slowed me down at first, but it led to cleaner and more reliable software. Now, my whole team does this, and we have fewer issues to fix later.
3 comments
Log in to join the discussion
Log In3 Comments
henry_grant1mo agoMost Upvoted
Reminds me of using navigation apps without checking the map first. You follow every turn without knowing why, then get completely lost if there's a detour. Letting the tool do all the thinking makes you helpless when things change. Using it just for directions while you keep your own sense of the route works way better.
7
veraf751mo ago
Try writing the tricky logic yourself first, then ask the AI to check for missing edge cases. I had one spit out code that never checked for empty data... cost me hours to debug later. Drafting the skeleton yourself forces you to think it through, then the AI just fills in the boring parts. We do this now and catch way more bugs before they happen.
2
the_patricia1mo ago
Question whether we need to draft everything ourselves these days. AI code helpers have gotten pretty good at catching empty data checks if you prompt them right. I've seen teams rely on AI for first drafts without major issues, saving time on simple logic. Maybe the extra manual step only matters for key systems, not everyday coding.
6