New series: what assistive tech really hears on your checkout page. Start with part one →
Shipwright
Home
Career Sep 16, 2026 1 min read 255 views

Desk Setups from a Fully Remote Engineering Team

Sam Whitfield

Sam Whitfield

Engineering manager and recovering QA lead.…

Share
Cover illustration for the article Desk Setups from a Fully Remote Engineering Team

Six desks, six time zones, and one shared love of good lighting. The hardest problems on an engineering team are rarely technical. This post is about the habits and small agreements that let a group of people ship good work without burning out.

Mara’s standing desk in Lisbon
Mara’s standing desk in Lisbon
Elias’s corner office
Elias’s corner office
Priya’s minimalist setup
Priya’s minimalist setup

Around the team

We changed one thing at a time and wrote down why. That record turned out to be the most useful part, because six months later nobody remembered the original problem.

What we would change next time

If you try this on your own project, start with one page or one service rather than the whole codebase. A small experiment gives you real numbers to argue with, and it is easy to roll back if the idea does not fit.

  • Agree on what code review is for.
  • Write decisions down where people will find them.
  • Automate style arguments away.
  • Pair new people with a named mentor.
Sam Whitfield

Sam Whitfield

Author

Engineering manager and recovering QA lead. Sam writes about testing, code review, and building teams that ship calmly.

Related Posts

Comments 5

Ben Carter

Would love a follow-up on how you test this in CI.

Yuki Tanaka

The renaming spree is a rite of passage.

Sam Whitfield Author

Bookmarked. The code sample alone saved me an afternoon.

Fatima Zahra

We run this in production at a fairly large scale and can confirm the caveats are real.

Oskar Nilsson

Solid write-up. The warning about caching bit us hard last year.

Leave a comment

Your email will not be published. Sign in for a faster experience.

Supports **bold**, *italic*, and `code`.