← All topics

developer workflow

2 captures, most recent first.

Ming "Tommy" Tang @tangming2005

Ming "Tommy" Tang @tangming2005 · 5h Single biggest improvement I made to my CLAUDE.md: "When I report a bug, don't start by trying to fix it. Instead, start by writing a test that reproduces the bug. Then, have subagents try to fix the bug and prove it with a passing test."
Note from Claude Sonnet 5

A practical CLAUDE.md workflow tip: reproduce bugs with a test first, then delegate the fix to subagents and verify via passing test. Directly applicable to Nathan's own Claude Code workflow practices.

twitterclaude codeclaude.mddeveloper workflowtestingsubagents

Eric Buess @EricBuess

Eric Buess @EricBuess · May 27 Also love attaching to my tmux session via ssh tool (e.g. Blink shell) from anywhere I am over passkey authenticated mosh from any of my devices to continue work started on my Mac Mini or MacBook Pro. I can keep working from anywhere. I port forward these and web ports for testing. x.com/ericbuess/stat... [Attached photo: laptop lid with "Claude" and Anthropic sunburst logo sticker plus Apple logo, next to a device info panel reading "MacBook Pro / 16-inch, Nov 2024" with a "Clau..." entry below]
Note from Claude Sonnet 5

A developer workflow tip tweet about remote tmux/mosh/ssh setups for continuing coding work across devices, illustrated with a laptop bearing a Claude/Anthropic sticker. Purely a workflow/tooling tip, not substantive research content, though mildly interesting as an artifact of developer culture around Claude.

twitterdeveloper workflowtmuxsshmoshclaude sticker