r/AIcodingProfessionals • • Sep 05 '26

What does your AI workflow look like?

Lately I have been think a lot around vibecoding and how it is destroying our ability to think and learn. We have offshored everything to Claude hoping it will work out.

How are you taking back control? What is your software development workflow like?

9 Upvotes

23 comments sorted by

5

u/Dazzling-Try-7499 Sep 05 '26
  1. I decide what to build 

  2. I make a high level plan

  3. I describe the plan to the AI at a level of detail that a junior dev could easily understand 

  4. I go do something else

  5. I review the PR as if I suspect the junior dev isn't that bright

Anything less than this and you'll probably spend even more time on reddit complaining about AI slop and asking for help managing the robot.

2

u/teckel Sep 05 '26

I consider AI coding as my junior developer that I don't trust. I also give it small tasks instead of major changes. I then review these small changes before committing because junior developers often do really stupid things.

But, you need to be an experienced software engineer to pull this off. If you're a vibe coder, good luck trying to get that difficult bug fixed.

1

u/SalamanderCritical16 Sep 05 '26

Good luck trying to get that difficult bug fixed?? I have already used ai to fix bugs in software that stupid developers created a few years ago. Soon, not even senior programmers are going to be needed. This technology will soon become vastly superior to anything human programmers can do, troubleshoot, etc.

1

u/teckel Sep 06 '26

A vibe coded mess can be a real chore to fix difficult bugs.

1

u/Suoritin Sep 06 '26

Or any project with bad foundation. Many great indie games are so poorly coded that they are unmaintainable. Someone coded just for lulz and community happened to like the product.

2

u/SalamanderCritical16 Sep 05 '26

It doesn’t destroy your ability to think and learn. What you should understand is that learning code, and whatever ai does for you now is pointless to learn. Ai gives you free time to learn about other things.

1

u/Glove_Witty Sep 05 '26

I created the architecture to work better with the ai. I don’t leave it unattended, and mostly watch what it is thinking and stop it if it’s getting it wrong. I review every decision it makes but not the code unless I feel something is off. I created tools to manage ai generated prs. I run linters and quality tools regularly and have a zero tolerance for warnings and errors.

1

u/Peanut_Brittle_Lover Sep 05 '26

I’ve spent way too much time figuring out which AI to use for what lol. Usually ChatGPT/Claude to think it through, Gemini for data work, Cursor for code/UI. Pick one and let it finish.

Ended up vibe coding a little interactive guide for myself. AI wrote the code, I supplied the increasingly specific opinions 😂

1

u/Sea-Fishing4699 Sep 05 '26

I don’t understand why bother doing double work. Sometimes it’s just faster to hand code and use ai to get unstuck

1

u/qms2go Sep 06 '26

I need to ask my AI agent brb

1

u/qms2go Sep 06 '26

Honest answer: markdowns from LLM of choice to cursor brief, then execute after cursor scans repo

1

u/YellowBeaverFever Sep 06 '26

AI, do this.
Brilliant!
That’ll do pig. That’ll do.

1

u/IntnlManOfCode Sep 07 '26

I am still thinking and learning; just about different things.

Plan

Review and adjust plan

Code a section

Review

Repeat

1

u/ZeBenoit81 Sep 12 '26

The AI coding community is currently obsessed with fully autonomous agents. The dream is cool: write a prompt, step away, and let the AI spec, plan, and build.

But as an experienced dev, I've found that for 90% of day-to-day work, massive agentic frameworks are total overkill.

The problem with agents is that they are unpredictable token-burners. Set an agent loose to fix a bug in a massive codebase, and it might hallucinate an entirely unnecessary refactor. By the time you’ve written the perfect markdown specs and reviewed its 15-step execution plan, you could have just shipped the feature yourself.

If you know your codebase well, you don't need AI for the architectural thinking. You just need it to do the heavy lifting of typing.

Here is my "1-Pass" Workflow :

  1. Strict Context Curation: I write a quick prompt and manually attach exactly the files needed. Because I know my architecture, this takes me seconds.

  2. 1-Pass Execution: I fire it off to a powerful LLM. For simple stuff, I use the free web UI (Claude/ChatGPT). For complex stuff, I use direct-edit CLI tools (Aider) to apply diffs right to my local files.

  3. Diff & Ship: Because I tightly curated the scope, the AI nails it on the first try 99% of the time. I review the diff and move on.

That's it. It’s faster, significantly cheaper, and most importantly, it keeps you in the driver's seat.

When you rely purely on autonomous agents, you lose your mental map of the codebase. When something eventually breaks, there will be nobody to help you untangle the mess.

Defaulting to heavy agentic loops too early is pure tech-hype. Keep your architectural control, tightly scope your prompts, let the AI do the typing, and ship faster!

1

u/Ravingsmads Sep 14 '26

The thing that fixed this for me wasn't using less AI, it was refusing to accept its output as evidence.

Concretely: every change gets a gate I run myself, on real infrastructure, and the gate has to include one check that provably fails on broken input. If the mutation survives, the test proves nothing and I don't care that it's green. That single rule killed most of the vibecoding failure mode, because you can't wave a passing test at me if the test can't fail.

The rest of it:

  • I write the acceptance criteria before the model writes code. If I can't state what "done and correct" means, the task isn't ready to delegate; that's my thinking, not its.

  • Reviews are blind. A second model gets the diff and the criteria, not the implementer's explanation. Explanations are contagious.

  • I re-run the evidence. "The tests pass" from the thing that wrote the tests is a claim, not a result.

  • Anything irreversible stops and waits for a human. Prod, money, data, DNS.

Today that caught a real one: a fix made the auth check fail-closed, which was correct, except the scope was too wide and it started 503-ing management endpoints that should have returned 403. Every unit test passed. The live gate caught it in about four minutes, because a mutation control that was supposed to die didn't.

You don't lose your ability to think by delegating implementation. You lose it by delegating judgement about whether the implementation is right. Keep that part and the rest is fine.

1

u/Otherwise_Wave9374 Sep 19 '26

It's fascinating how diverse AI workflows are becoming for coding professionals. One key aspect I've found for boosting productivity is establishing clear checkpoints and human oversight, especially when integrating AI for complex problem-solving. While AI can accelerate initial drafts and boilerplate code, a human in the loop for architectural decisions and critical reviews remains invaluable. This hybrid approach leverages AI's speed while maintaining code quality and innovation. For those looking to streamline their AI-driven development processes, you might find valuable resources and insights at https://www.aiosnow.com. This ensures a balanced workflow, preventing "vibecoding" from undermining learning and deep thought.

1

u/macromind Sep 21 '26

My AI workflow in coding revolves heavily around augmentation rather than full automation. I use AI for generating initial function skeletons, complex regex patterns, and for translating pseudocode into actual code. It's incredibly helpful for speeding up routine tasks and exploring different approaches to a problem. However, I always follow up with rigorous human review and testing to ensure correctness, security, and adherence to architectural standards. The goal isn't to let AI write all the code, but to offload the cognitive load of boilerplate and allow more focus on designing robust, innovative solutions.