Article 003: Social Media
URL: https://thelongrun.work/articles/003-development-used-to-be-synchronous
Medium
Tags (5 max)
- Technology
- Software Development
- Software Engineering
- Productivity
- Programming
Subtitle
“IDE-centric work assumed tight feedback loops. Async breaks that assumption in subtle ways.”
LinkedIn Posts
Post 1: Publish-day
Visual: Before/after desk comparison. Left (2015): Triple monitor setup, mechanical keyboard, ergonomic mouse, cable management, the works. Right (2026): Single phone on a minimal stand. That’s it. The desk is almost empty.
I asked Claude to refactor a module yesterday. It changed 2,000 lines across 40 files.
I reviewed it in 15 minutes. Approved. Merged.
Was that… enough?
Development used to be synchronous. You typed, you saw the result, you adjusted. Each change was small enough to hold in your head.
Now the changes arrive in chunks too large to fully comprehend. Review becomes sampling. Experience becomes knowing where to look.
I wrote about what this shift changes — and what it demands of us: [URL]
What’s your threshold? When does a diff become too big to truly review?
Post 2: Insight (target: 2026-02-09)
Visual: Cold coffee, steam long gone, sitting next to a laptop. Screen shows “Build complete — 2,847 files modified.” The coffee was hot when this started. Now it’s abandoned. The smell of a desk no one’s sitting at.
I used to write specs to understand what I wanted to build.
Now I build to understand what I want.
Implementation is cheap. Working software has become my design document. I prototype, evaluate, refine my thinking, then build again.
The iteration loop moved upstream.
Post 3: Reflection (target: 2026-03-02)
Visual: Expensive ergonomic keyboard, slightly dusty, untouched. Next to it: a phone showing Slack notifications and PR activity. The keyboard is a museum piece. The phone is where work actually happens now.
Since writing about synchronous development, I’ve noticed how I review differently now.
I don’t read every line. I can’t — the changes are too large.
Instead I ask: Do the tests pass? Does the architecture look right? Does this match what I asked for?
Trust has shifted from inspection to process. I’m not sure how I feel about that yet.