| I think some of this might come down to stack as well. I watched a t3.gg video[1] recently about Convex[2] and how the nature of it leads to the AI getting it right first time more often. I've been playing around with it the last few days and I think I agree with him. I think the dev workflow is going to fundamentally change because to maximise productivity out of this you need to get multiple AIs working in parallel so rather than just jumping straight into coding we're going to end up writing a bunch of tickets out in a PM tool (Linear[3] looks like it's winning the race atm) and then working out (or using the AI to work out) which ones can be run in parallel without causing merge conflicts and then pulling multiple tickets into your IDE/Terminal and then cycling through the tabs and jumping in as needed. Atm I'm still not really doing this but I know I need to make the switch and I'm thinking that Warp[4] might be best suited for this kind of workflow, with the occasional switch over to an IDE when you need to jump in and make some edits. Oh also, to achieve this you need to use git worktrees[5,6,7]. [1]: https://www.youtube.com/watch?v=gZ4Tdwz1L7k [2]: https://www.convex.dev/ [3]: https://linear.app/ [4]: https://www.warp.dev/ [5]: https://docs.anthropic.com/en/docs/claude-code/common-workfl... [6]:https://git-scm.com/docs/git-worktree [7]:https://www.tomups.com/posts/git-worktrees/ |
[1]: https://code.visualstudio.com/updates/v1_103#_git-worktree-s...
[2]: https://code.visualstudio.com/updates/v1_103#_chat-sessions-...