I usually develop full stack so will have a front end tab (with multiple Vim buffers), a backend tab (again with multiple buffers), dev servers, a database sql tab (if needed) and a command line tab to grep and git and whatever else.
Might sound kind of awkward but it's muscle memory by now and blazing fast for my use case.
The one thing I have not figured out yet is how to cleanly integrate AI tools into my workflow. A lot of cutting and pasting which feels very clumsy. I don't want to give up Vim nor my basic workflow. I never used co-pilot just GPT.
I used to use your setup, and I was fast. But tmux is much better. (I'm also a full-stack dev btw)
Another advantage, I can ssh into the server, start a tmux session, and work there the same way I do on my local. Doing that your way would require a lot of ssh sessions.
> The one thing I have not figured out yet is how to cleanly integrate AI tools into my workflow
Tips: use `/ask` if you don't want it to make changes, and try to use it for small incremental commits, instead of broad sweeping changes. That may change soon with these reasoning models, though.
It's also good for writing shell commands.
Works better than MySQL workbench and other things like that, for me, because it works in a terminal over ssh too.