John Workman

working like a dog...mostly on AI stuff

[John Workman @workdog]

@mmontuori0 The issue I'm seeing is caused by a broken route from T-Mobile to CloudFront POP (the 143.204.29.x edge), confirmed by the dead ping. This is why some things are working, and some things are not. Forcing 8.8.8.8 just keeps steering you to a different, working edge.

[John Workman @workdog]

T-Mobile Fiber flaking out today? If some sites load and others hang and chat apps work but file/image uploads fail, it's not your router. It's a flapping route to certain CDN servers.

You can sidestep it by forcing public DNS:
Mac: System Settings → Network → Wi-Fi → Details → DNS → click "+" → add 8.8.8.8 → OK

Windows: Settings → Network & Internet → Wi-Fi → Hardware properties → DNS server assignment → Edit → Manual → turn on IPv4 → Preferred DNS 8.8.8.8 → Save

Then fully quit and reopen Slack & your browser so it reconnects to a healthy server.

Even simpler if you have a VPN: just turn it on. It tunnels past the broken path entirely, so everything works no matter which servers DNS picks.
@TMobile @TMobileHelp #TMobileDown #TMobileOutage #TMobileFiber #TFiber

[John Workman @workdog]

Small feature. Real difference. If you use Claude Code for anything longer than a 10-minute task, try setting a /goal first and see if the outputs feel more connected.

[John Workman @workdog]

Claude Code just added /goal and it quietly changes how you work with it.

[John Workman @workdog]

Think of it like telling a contractor what the finished house should look like before they touch a single wall. The individual tasks finally have a reason behind them.

[John Workman @workdog]

Claude Cowork FINALLY added a default folder/project so you don't have to reset it every time. Just hit the star to save as default. I submitted this as a bug to Anthropic a few weeks ago. I'd like to think they did this just for me. Thank you #ClaudeCowork

[John Workman @workdog]

Repo: https://t.co/DsdRKFFjMP

To copy this: clone it, then open .claude/commands/morning-sync.md and .claude/commands/evening-sync.md. They're ready to run.

Scheduling options: resources/getting-started/setup-scheduled-journaling.md

A star on the repo helps more people find it. Appreciate it.

[John Workman @workdog]

The part of my workbench I actually live in is two slash commands.

One I run before coffee. One I run after the workday.

Together they keep my journal writing itself.

/morning-sync and /evening-sync. Here's what they do.

[John Workman @workdog]

The value isn't automation. It's continuity.

I used to lose Monday-to-Friday. Slack in one place, email another, meetings in Granola, calendar somewhere else.

Now one file per day has everything I did, everything still open, and what's next. Searchable. Quotable. Useful in retros. Useful in 1:1s. Useful when someone says "what did we decide last Thursday."

Whole setup ships in my workbench repo. Link in replies.

[John Workman @workdog]

PSA on Claude Code routines.

They run in the cloud. Fresh clone of your GitHub repo each run. Can commit back.

They CANNOT write to local files on your machine.

If your workflow touches a local Markdown file (a journal, a logbook, a notes folder — anything outside git), you need something that runs locally: Cowork scheduled tasks, cron calling claude -p, or a desktop scheduler.

Routines don't. Worth knowing before you build the wrong thing.