I’ve tried this kind of format too but it didn’t stick for me as i was missing the rich context the sessions were able to provide for me. Specifically the lack of diagrams and other nice formatting that is possible in HTML files. I also tried linear as a broker in between for a while but it just blew up and became too tedious to navigate and ran out of sync fast. Also expensive on token overhead.
Currently what I task it to do is have one or multiple agent threads tied to a project work it and have this really token light skill laid out that leverages eleventy heavily and renders it as markdown file. Than paired with thisbit.ai (I made this and still am developing it) i just comment / voice over on all the bits from the article and have the agent take it from there again.
Also neither codex nor Claude code come even close to the lovely TUI renders of Gemini (Argon 4)
This is a temporary problem. A 10x-100x speedup will allow us to simply wait for the response, instead of finding something else to do in the meantime.
I wonder what the experience is of people here with the ultrafast mode (8x) of Codex.
Why start several threads in parallel to begin with? If waiting is an issue, maybe you should break that one task into multiple steps. That would only produce more output at a lower quality. Nothing has changed about the human thinking capacity. Focus on one thing and get it done.
It's interesting watching everyone build their solutions to this new world of problems. Mine has been to double down on my markdown notes, extending https://app.etherpk.com so that every task (plain markdown) can be viewed under it's wikilink (or several) on a kanban board. An MCP server knows how to interact with the notes graph. I copy a reference to the task, hand it to an agent, and the agent works with blocks under the task from there. It basically means I can give the agent really rich context up front - images, excalidraw drawings etc and the agent can update the task as it goes. Having everything on a kanban board makes it easier to step away from a task to work on whichever really needs my attention and come back. Putting this together with herdr has been very productive. I still have to watch the brain fry, but it is helping. Don't know if I'm selling the idea but I feel like I'm on to something after experimenting with various systems similar to what the author is suggesting. I'm working on making a product of it. The onboarding needs some streamlining but it's available to use for free for local graphs.
My setup is similar but it is still imperfect. Keeping track of what I am working on, and where I am in the process, as MD files in the same repo as the code has been a help.
But I still find myself coming back to a terminal window, the final summary of a long run (20-90min) on display, and asking the agent "where are we? what is next?"
And I still get the burnout feeling after dumping, reloading, dumping, reloading context for the 3 agents I have running simultaneously. That leads me to sometimes avoid the 4 or 5 open PRs, each with 20+ file changes I have to review, the stacked result of the last feature I asked the agent to start before I went out for a walk, or to eat lunch, or to sleep.
Starting loops is so easy now, so low friction. But closing things out, that last 20%, is still a slog. And I have a lot more of it now that agents can generate so much.
With agentic development, we're saying every software developer is now managing a team (of agents). We already kinda know how to do that. Issue trackers, stand ups, design documents. I'm using GitHub issues to manage the queue and it works ok. I don't need to know all of the context for every task, so maybe an aggregated "stand up" would be better.
Why inventing your own issue/work tracking system based on git? Wouldn't it be easier to work with, say, github issues the same way? You create it normally, agent picks up, works, updates the status on it or in the relevant wip PR, then potentially adding "needs more info" label. You'd get all the same tracking benefits and more: better UI, kanban, more tools.
Didn’t invent it. Using open source solution board.md. The benefit of having the board in the repo next to the source code is in giving your agents convenient access to both business and tech contexts in one place.
I’ve seen so many teams having jira living one life that has nothing to do with real codebase.
So instead of tabs, I do cmux’s named tab groups. From there I rank them in my sidebar by priority and makes sure I’m always staying on top of the top prio tab group. The others I’ll only navigate to when I’m free.
I can usually have 3-4 tab groups running at one time. More than that I find to be counter productive
The author's problem is that the are doing too many parallel agent things. It's very interesting that their solution space is "keep doing tons of parallel stuff, but with different tooling" instead of... "do less parallel stuff (and provide stronger attention)".
My perspective was that it seems like your problem is that you're exhausted from doing too much. This led you to a technical solution where you shuffle the order of things, but are still doing too much. Your result, as stated in the post: "I'm still exhausted". So is your solution actually solving your problem?
I still do LeetCode problems occasionally. It feels weird to write code and work through complex logic manually again, but I think it's more crucial than ever these days. It's like physical exercise. If you don't use your brain and keep challenging yourself, your problem-solving skills will eventually atrophy.
When I read things like this I have a mixed feeling of not knowing wether I’m sad cause I’d like to have time to do leetcode too, or wether I’m simply too anxious to let the productivity improvement spiral go and chill a bit.
People exercise for sport because we've automated away much of manual labour, so if you don't exercise, you look and feel like a string bean or a watermelon.
The AI age is trying to automate away our thinking, which runs the risk of making our brains look and feel like the same way as our bodies if we don't actively try to work them.
In the case of exercise, the majority of people don't pursue it in a somewhat post-labour era. I'm certain we'll see even less mental exercise in a post-thinking era. And it's deeply unsettling to think about how that will play out if we don't wake up and put a bit more mandatory/intentional thinking into the way we live with AI.
You use your brain for things like problem solving literally everywhere and there are myriad of possible high intensity brain exercises from video games to meeting new people.
The only thing that will 100% atrophy when not coding is coding skill.
I agree that coding problems are not particularly necessary for preventing atrophy, but it would be going to far to say that people are merely panicking.
I think maybe we're conflating strictly cognitive facilities, facilities that can be maintained through all sorts of means, with intellectual skills and habits that really are in danger of atrophy when we rely too much on AI.
> It is still exhausting. But I don't feel distracted or lost.
So not really solving the issue, just feeling productive for the hell of it. To me, this sounds like those X posts of some techbros LARPing with multiple screen setups where agents are running wild and generating summaries of stuff and are stacked over each other etc, all in the hope of optimizing something (no one knows what exactly).
Just have decent workflow across agents and you won't have to reinvent JIRA hell.
Currently what I task it to do is have one or multiple agent threads tied to a project work it and have this really token light skill laid out that leverages eleventy heavily and renders it as markdown file. Than paired with thisbit.ai (I made this and still am developing it) i just comment / voice over on all the bits from the article and have the agent take it from there again.
Also neither codex nor Claude code come even close to the lovely TUI renders of Gemini (Argon 4)
I wonder what the experience is of people here with the ultrafast mode (8x) of Codex.
But I still find myself coming back to a terminal window, the final summary of a long run (20-90min) on display, and asking the agent "where are we? what is next?"
And I still get the burnout feeling after dumping, reloading, dumping, reloading context for the 3 agents I have running simultaneously. That leads me to sometimes avoid the 4 or 5 open PRs, each with 20+ file changes I have to review, the stacked result of the last feature I asked the agent to start before I went out for a walk, or to eat lunch, or to sleep.
Starting loops is so easy now, so low friction. But closing things out, that last 20%, is still a slog. And I have a lot more of it now that agents can generate so much.
I’ve seen so many teams having jira living one life that has nothing to do with real codebase.
I can usually have 3-4 tab groups running at one time. More than that I find to be counter productive
https://web.archive.org/web/20261108193851/https://sergeykuh...
I still do LeetCode problems occasionally. It feels weird to write code and work through complex logic manually again, but I think it's more crucial than ever these days. It's like physical exercise. If you don't use your brain and keep challenging yourself, your problem-solving skills will eventually atrophy.
The AI age is trying to automate away our thinking, which runs the risk of making our brains look and feel like the same way as our bodies if we don't actively try to work them.
In the case of exercise, the majority of people don't pursue it in a somewhat post-labour era. I'm certain we'll see even less mental exercise in a post-thinking era. And it's deeply unsettling to think about how that will play out if we don't wake up and put a bit more mandatory/intentional thinking into the way we live with AI.
The only thing that will 100% atrophy when not coding is coding skill.
panic about “ai brain fry” is overblown
I think maybe we're conflating strictly cognitive facilities, facilities that can be maintained through all sorts of means, with intellectual skills and habits that really are in danger of atrophy when we rely too much on AI.
So not really solving the issue, just feeling productive for the hell of it. To me, this sounds like those X posts of some techbros LARPing with multiple screen setups where agents are running wild and generating summaries of stuff and are stacked over each other etc, all in the hope of optimizing something (no one knows what exactly).
Just have decent workflow across agents and you won't have to reinvent JIRA hell.