Just like in software, some of the most beautiful solutions come from constraints. Think, the optimisations that game developers implemented because of the frame budget.

I’ll confess the reason it hit us so hard is because the code quality was so low and wasteful on allocations that it didn’t hide the problem as well as previous versions.

So I plan the next work, while the current is still running and if that's a task that can't have parallel work, I have a bunch of time to keep planning the next steps for other systems.

And then there's time for reading through the changes and applying corrective changes to the code or the meta-skills.

I use CMUX and setup workspaces for each topic I'm working on, each workspace has number of tabs. That helps keeping track of everything I'm working on, but also means no topic gets left behind until I close the workspace. So they accumulate

But maybe that was a me error and worth a second shot.

It’s just that the rush is more frequent, addiction intensity scales with dose and frequency.

The addiction part, the ADHD part and the pending test part.

The fear of becoming addicted to AI is real and I don't think I'll be capable to stop it, considering we're asking people who struggle with avoiding quick dopamine to use it professionally in their daily work life.

My Pro went to Max(5) to Max(20) pretty quickly and I was burning through that weekly limit still, without large agentic workflows that burn tokens. Just me and 4-5 terminals. Sometimes I was happy to hit the limit because I was forced back to normal life.

I've gone back to Pro to stop what was happening.

Now I'm self-aware enough to notice the trend and put up safe guards, but that's because I've always had to adapt my environment to control my behaviour because I know direct behaviour control is abnormally challenging. I fear for those who won't see it coming, until they're in deep.

The second it works, bake the workflow into the harness. Yesterday I was doing just that, and the whole agent loop disappeared because the process could've been condensed into a one-shot request (+1 MorphLLM fast apply) from careful context construction. (It was an Autoresearcher)

Seeing the idea explored in such depth is great, I really am concerned about this.

Guess we’ll see how my diagnosis goes.

But maybe that’s enough tokens to feed an entire lifetime of user behaviour in for the digital twin dystopia?

There's no harm in a string, only in the execution.

I create Tools as Actors, which you preconfigured for the LLM context (in-house agent loop). The tools being preconfigured means you setup their environment before they can be executed. If it calls a bash tool for instance, the Tool Actor gets called and then it runs that command against an attached remote VM.

Or filesystem operations, are just read/writes inside a .zip file, which is overlayed onto the target project at build time.

This article is spot on, and I probably say that because it's self reinforcing.

But I like to have that forced hour to stop, it’s moment to take a breath.

It depends on the kind of work though, some things are more token intensive.

If I had more income, I would also buy 4x 96g Optane drives of p0 swap disks and a few ssd's for p1 swap disks. To evaluate how well you can get a 1T model running in these absurd ram prices.