Embracing Remote Work: Benefits, Dangers, and Overcoming Challenges
After years of building and running distributed engineering teams, here are the actual benefits, real dangers, and hard-won lessons about making remote work stick.
Remote Work
Definition
Remote Work coverage in this archive spans 9 posts from Dec 2017 to Jun 2021 and is treated as an operating model question: decision rights, feedback loops, and execution clarity. The strongest adjacent threads are engineering, teams, and management. Recurring title motifs include remote, distributed, teams, and engineering.
What the archive argues
- A repeated argument is that small teams ship faster when ownership boundaries are explicit.
- Early posts lean on team and remote, while newer posts lean on remote and changed as constraints shifted.
- This topic repeatedly intersects with engineering, teams, and management, so design choices here rarely stand alone.
Execution checklist
- Write down ownership, escalation routes, and meeting defaults before scaling team surface area.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read engineering and teams before committing implementation details.
Common failure modes
- Using process to compensate for unclear ownership and weak technical direction.
- Adding management layers before tightening decision loops and execution signals.
- Applying guidance from 2017 to 2021 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): Embracing Remote Work: Benefits, Dangers, and Overcoming Challenges
- Then read (operating middle): What I Actually Changed About Engineering Interviews Over Zoom
- Finish with (foundational context): Async by Default: Reducing Decision Latency in Distributed Engineering Teams
Related posts
- Embracing Remote Work: Benefits, Dangers, and Overcoming Challenges
- Hybrid Work Is Harder Than Full Remote
- 2020: The Year That Broke the Playbook
- What Actually Works for Distributed Teams (Six Months In)
- What I Actually Changed About Engineering Interviews Over Zoom
- Your VPN Was Never a Security Architecture
- Your Team Isn’t Remote. It’s Just on Zoom.
- Your Team Just Went Remote. Here’s What to Do Right Now.
References
Hybrid Work Is Harder Than Full Remote
Everyone thinks hybrid is the compromise between remote and office. It is actually harder to get right than either extreme.
2020: The Year That Broke the Playbook
Decloud survived its first real crisis, I took on enterprise work, and the industry learned what remote work actually looks like. A personal look back at a strange year.
What Actually Works for Distributed Teams (Six Months In)
After running a remote-first company for years and watching everyone else scramble through COVID, here's what I've learned actually works -- and what doesn't.
What I Actually Changed About Engineering Interviews Over Zoom
Whiteboard coding over Zoom is broken. Here's what I do instead when hiring engineers virtually.
Your VPN Was Never a Security Architecture
COVID broke everyone's VPN. Good. It was a terrible security model to begin with. The answer isn't scaling your VPN — it's replacing the mental model entirely.
Your Team Isn't Remote. It's Just on Zoom.
Most teams claiming to work remotely are just recreating the office over video calls. Async communication is the actual unlock, and almost nobody is doing it right.
Your Team Just Went Remote. Here's What to Do Right Now.
COVID forced your engineering team remote overnight. Here's the no-fluff version of what actually matters in the first two weeks.
Async by Default: Reducing Decision Latency in Distributed Engineering Teams
A practical operating model for async-first communication that reduces decision latency without sacrificing alignment.