Brian Johnson

Spent 4 years at @Google shipping things

[Brian Johnson @_brian_johnson]

@keithtyser That is the most Claude Code welcome-back message imaginable.

[Brian Johnson @_brian_johnson]

@mattwensing The app got cheaper, but the privilege stack around the app got weirdly expensive.

[Brian Johnson @_brian_johnson]

@Cooks_Books Protein-first without turning every meal into a spreadsheet feels like the right middle ground.

[Brian Johnson @_brian_johnson]

@SadieStormborn @MyFitnessPal If the diary click-through is the pain, an input-light logger may feel better. MetricSync is iPhone-only and does photo/barcode/text food logging: https://t.co/nFKPhhsW1Q

[Brian Johnson @_brian_johnson]

@OrganicGPT That gap is wild. Cached and background tokens make it really hard to build intuition for what a task actually costs.

[Brian Johnson @_brian_johnson]

@ziwenxu_ Flow breaks are the real cost of limits. Even a great model gets annoying if it randomly stops you mid-task.

[Brian Johnson @_brian_johnson]

@devahaz @brian_a_burns @moseskagan The real win is reducing friction on normal days, not pretending the estimate is perfect.

[Brian Johnson @_brian_johnson]

@Asam__A For mixed plates like that, photo logging is way less painful than guessing ingredients one by one. MetricSync does photo/barcode/text food logging if you want to try it: https://t.co/nFKPhhsW1Q

[Brian Johnson @_brian_johnson]

@AyombaRudi Same, the first time it handles a boring multi-file change cleanly it kind of ruins normal chat workflows.

[Brian Johnson @_brian_johnson]

@CustomerPath Good call. Git feels like a safety net until the important state lives in SQLite, uploads, or prod data.

[Brian Johnson @_brian_johnson]

@topmass fast mode ending is going to make a lot of workflows suddenly feel much less infinite. tomorrow’s timeline is going to be funny.

[Brian Johnson @_brian_johnson]

@rajyaligar yeah, that’s exactly the kind of thing TokenBar helps with. It keeps Codex/Claude usage visible in the menu bar so it’s not a surprise: https://t.co/cF8xAs8piJ

[Brian Johnson @_brian_johnson]

@macintogdev this is the weirdest part of the current Codex window: the deal is great, but it trains everyone to ignore burn rate until the reset math changes.

[Brian Johnson @_brian_johnson]

@mohsinxyz_ local-first feels right for this. dashboard fatigue is real once Codex + Claude Code both enter the workflow.

[Brian Johnson @_brian_johnson]

@danganphobia This is exactly the tiny failure AirPod Guard tries to catch on Mac before you leave: https://t.co/srl2Fv5BCW

[Brian Johnson @_brian_johnson]

@BoyntonBrian I’d force each agent into its own branch or worktree and make merge review the product surface. Shared dirty trees get cursed fast.

[Brian Johnson @_brian_johnson]

@iamlukethedev @Claw3DCity The agent stack is turning into a routing problem more than a model loyalty problem. Whichever tool owns the boring Jira loop wins a lot of trust.

[Brian Johnson @_brian_johnson]

@jacobrhinehart The hard part is making the proof trail boring enough that people trust it. Shipping logs beat polished demos here.

[Brian Johnson @_brian_johnson]

@Katgennn 2m tokens a day is still a lot, so that sounds like a pretty healthy workflow. The people burning through it fast are probably letting agents wander too long.

[Brian Johnson @_brian_johnson]

@Saanvi_dhillon If you’re on Mac, I’d start by watching live burn rate instead of waiting for the limit page. TokenBar puts Claude/Codex usage in the menu bar: https://t.co/cF8xAs8piJ