Keep a friction log: write down recurring time-wasters before fixing anything
dSebastien · x · 2026-10-24
- Core practice: Keep a casual "friction log" — a note on your phone or a plain text file is enough.
- Method: Every time something wastes your or someone else's time, write it down. After a few weeks, patterns emerge.
- Decision rule: Only recurring frictions are worth fixing; one-offs usually aren't.
- Why it matters: This beats trying to fix everything too soon — especially useful for optimizing coding and agent workflows, where you want data on actual pain points before investing in solutions.
More from coding & agent
- Yacine says he's reverse-engineering Melee and Rain World with a DeepSeek agent pool — yacineMTB · 2026-10-25
- Dev builds fully automated highway scenery generator with Opus 5.5 — ezshine · 2026-10-25
- Two Key Claude Code Engineers Depart Anthropic, Rumored to Join SpaceX-Linked Effort — mark_k · 2026-10-25
- Flywheel ships local UI: your graphs on your own machine, no account needed — tensorqt · 2026-10-25
- When your skill becomes your brand: the Claude Code skills hall of fame — garrytan · 2026-10-25
- Hybrid Claude + Seedance pipeline renders EDM video with 60%+ archive footage to cut costs — AIandDesign · 2026-10-25