What's the biggest benefit of coding with an AI pair?
Hi ProductHunters,
What's in your opinion the best part of chatting with an AI while coding?
I start first:
The best part? Analyzing ideas, questioning architecture, and brainstorming concepts.
Being able to talk through your thoughts with someone (or something) while shaping your idea — it’s not just cool, it’s incredibly useful.
StackOverflow was fun — when someone had your exact problem.
But it never gave you feedback on the bigger picture.
Curious to hear your take!
31 views
Replies
I generally do not ask high level architecture questions or when I do, I do that to break the task into tickets. My case may be different because I am a software engineer. My main benefit is when the ticket is clear, I can assign it to an AI pair and move on to other things, for example, looking at Product Hunt.
I spend a lot more time away from the desk these days. My usual flow is:
Take the broad idea, ask AI to break into tasks (I use a Git/GitHub based flow)"
Check tasks, see where I could modify for clarity or architecture
Once a couple tasks look good, I assign the Claude Code/Gemini CLI, etc. and move on
Come back, test Git branch manually (I use branch based development workflow, with CI which was created by Claude)
According to test results either ask to fix issues or merge the Pull Request (development workflow states that Claude should create branch, commit, push, etc.)
There is another thing I do NOT do with AI
Ask AI for all tasks upfront - generally I have noticed it is good to produce code one ticket/step at a time, seeing what is the high level structure that is being generated and accordingly create next set of tickets. Without it, if I generate all tickets in the beginning, I may have tickets that refer to updated structure in the project since changes are always happening
@brainless yeah I agree and share your point, I could have explained not clearly my point, when talking about architectural topics I meant more overall project structure rather than bare metal things ( that's one of my preferred task to tackle ).
about "all tasks upfront" I need to agree once more, and furthermore it just isn't the right path ( 95% of the time ) because if your project is big enough, new requirements and needs will show up later into development and you'd need to rewrite all the initially scheduled tasks.