
Engineering Practices for Remote Teams

#17 - Remote Work & Asynchronous Communication at Doist - Gonçalo Silva
Topic 7 of 9
Published Nov 30, 2020 · Clip 42:50–54:06 (11:16)
Gonçalo explains that Doist rarely pairs because distributed teams lack guaranteed time-zone overlap; instead they invest in thorough code reviews where the reviewer becomes a co-owner, automation (linting, CI), style guides, and documentation so engineers working alone feel supported. He covers specs (product and technical) owned by teams, and the prioritization strategy of pre-allocating effort across features, products (Todoist vs Twist), support (hero role), and internal work (about 20%), adjusted deliberately rather than renegotiated constantly, with high-level themes filtering the product backlog.