DEV Community

Henry Godnick
Henry Godnick

Posted on

7 tiny systems that saved my focus (and my AI bill) as a solo Mac dev

#ai

If you’re building with AI all day, two things quietly eat your output:

1) token spend drift

2) feed-switching drift

I kept treating these as separate problems.
They’re not.
They’re the same leak in two different places: untracked loops.

Here are 7 tiny systems I use now as a solo Mac builder.

1) Start every coding block with a hard budget

Before I run a long Claude/Cursor/Codex session, I set:

  • max spend for this block
  • max retries before I intervene
  • definition of done

If I skip this, I always overrun.

2) Track token spend in real time (not end-of-week regret)

I built TokenBar for this exact reason.
It sits in the menu bar and shows live token/cost movement while I work.

The behavior change is immediate: when you can see burn in real time, you prompt tighter.

3) Kill “background feed tabs” during deep work

My old pattern: waiting for a run → open X/YouTube/Reddit “for 2 min” → lose 25.

Now I use Monk Mode to block feeds (not whole sites) during build windows.
I can still use the platform for specific actions, but infinite scroll is gone.

That distinction matters.

4) Force context batching

I run AI tasks in themes:

  • architecture tasks together
  • UI cleanup together
  • bugfix tasks together

Switching contexts every 5 minutes destroys both quality and cost efficiency.

5) Add a “2 retries then inspect” rule

If an agent/tool has retried twice, I pause and inspect context instead of letting it brute force.
This single rule saved me a lot of token waste.

6) Treat doomscrolling as an engineering bug

If your default environment keeps pulling attention, that’s not a motivation issue.
It’s a systems issue.

Fix environment > blame willpower.

7) End each day with a 3-line log

I write:

  • what produced leverage
  • what burned money/time
  • what I’ll change tomorrow

This compounds fast.


The meta lesson

I thought I needed better models.
What I actually needed was:

  • cost visibility
  • attention guardrails
  • tighter loops

Better systems made every model feel better.

If you’re a solo dev, fix these first and your output will jump without adding more tools.

Top comments (0)