Dan Shipper details his structured four-thread Codex workflow for tracking personal metrics, projects, and routing inbox content
Engineer Nick Dobos shared a parallel workflow consolidating 20 threads.
Oh this is cool. Definitely taking some ideas from this.
I've been doing something kinda similar by having
- 2 planning threads, one for personal life & basic human life routine, one for coding projects
- a council of advisors, general caht.
- I often condense threads into one larger tracking thread. I have like 20 skill ideas brainstorm and research threads I've chucked in via new chats, which then get archived and rolled into a single parent braintsorm thread that track them all.
Dan Shipper 📧@danshippercodex power-user best practices: - a few different "pulse" threads that run every morning to check the status of stuff i care about, e.g. proof metrics, all company meetings, etc - a "log" thread for ongoing, everyday activity i want to track. for me that's my "writing log"—want to track what im writing about, and working on from piece to piece - "inbox" thread which gathers all of my emails right now, but eventually will pull in all of the main important things from each "pulse" thread - "router" thread which knows about all of the other threads, and is also hooked up to my email to push emails into each thread appropriately