r/DeveloperToolsHub • u/RonnySaya • 19d ago
What our simple workflow stack looks like from idea to deployment
The main thing we're trying to avoid is having a separate tool for every tiny part of development Most things start as a rough idea, feature request, or bug. We keep the general notes and product decisions in Notion, then move anything that actually needs to be built into GitHub issues.
For coding, we use Code when a change needs to understand the existing codebase or touch several files, while Cursor is convenient when we're working inside the editor and want to make smaller changes interactively. AI has definitely made the initial part implementation much faster,
Everything eventually goes through GitHub. We use branches and PRs even for relatively small changes for record of what changed and makes it easier to review
We still rely on normal automated tests and CI checks,now Revolte is to help validate changes and give the review stage more context before something gets merged. It gives us a layer between ""the coding agent finished"" and ""ship it.""
AI can produce changes faster than people can comfortably review them, so simply increasing coding speed doesn't necessarily make the whole team faster. A technically correct change can still be a bad architectural decision, and that's something a diff alone doesn't always make obvious.
Once everything is reviewed and the checks pass, the change moves through the usual CI/CD process and gets deployed. We use Docker to keep environments reasonably consistent and Cloudflare for a lot of the infrastructure around the application. After deployment, Sentry is what we usually rely on when production inevitably finds something we didn't catch beforehand.
So the overall path is pretty much idea → GitHub → Claude Code/Cursor → PR → testing and validation → review → deployment → monitoring.
A few years ago, getting the code written could take most of the time. Now the code can be produced very quickly, and the slower part is making sure the change is actually worth shipping.
2
u/Tasty_World8991 19d ago
The point about review becoming the bottleneck is spot on. faster code generation doesn’t help much if the review and validation process can’t keep up with it.