12 tmux sessions are easy. anyone can spin them up. what slows me down is the context switching between them. if you are seriously building what you build while running paid work and life and relationships in parallel, the bottleneck stops being execution and becomes context maintenance. i don't wake up asking myself what work i should do first these days. i wake up asking which part of the context has not been updated in the last 12 hours. that is where the work actually is. there has to be a better mental model than the one i have.

I create a RESUME.md for each project that is updated any time an agent works on the project. This way, any agent is up-to-speed upon loading the project. I also have a 7am message sent to my phone with all recent progress and outstanding tasks, and an email once-a-week that is a more detailed description of outstanding tasks and achieved targets.

@sudoingX tmux n+1 or top of collective tmux app window in your own app : checks all other tmux and tells you what to work on next .. add a focus + context for you. There comes a time where we stop giving context to the ai sessions and the ai sessions will give you context.

I am working on that @sudoingX I suffer audhd and I fell the same way and need organization but have soo many projects now with AI going on at once I want overview. I got the skeleton for data for telemetry and metrics through grafana/prometheus setup now working on design and am collecting ideas for what would be the best components to place. If you ever want to chat DM is open. Tauri > Vite > Rust backend. Right now those buttons open up a Tauri Window and have it setup to have a terminal there just havent gotten to it yet. So total of 8 windows that will have kanban style components (css grid style some can be bigger then others) that can display data. Hard to describe the whole vision here but current dev so far.

@sudoingX Let me think about this too. I am in the same boat: full time job, family, so I need to make sure every free hour I have is used to the maximum.

@sudoingX milestones, issues, roadmaps, pre-planning, and lots of docs. do it well enough you can chase issue numbers until they are gone. Do reviews and audits in deliverable units.

@sudoingX at that point, it is time to bite the bullet and finally learn yourself an Emacs for great good!

@sudoingX Separate Hermes. Will be nice if they share some memory, but better to have one for creative work, other for accounting and other for personal use.

@sudoingX I noticed that as well. Bandwidth is the real bottleneck right now.

@sudoingX You're describing middle management