High Fidelity Remote Communication
tl;dr: Having worked remotely for many years, Olivier values his communications tools, recommending a specific list and outlining their cost. "A simple look can trigger a strong reaction and a sense of shared understanding. A slight change in intonation can convey doubt or excitement better than a paragraph."featured in #265
Remote Work Compensation: How Should Tech Companies Pay Their Remote Workers?
- Nicole Kow tl;dr: The impact of some companies allocating pay based on their remote employees' geography and others choosing not to pay agnostic to location.featured in #261
featured in #247
Staying Visible When Your Team Is in the Office…But You’re WFH
- Dorie Clark tl;dr: 4 strategies outlined: (1) Live up to your word with deadlines and commitment. "Overdeliver." (2) Consider strategies to replace water cooler missed connections. (2) Come in to the office when necessary e.g. meet new hires, etc... (4) "Ensure you’re easy to work with."featured in #242
How To Negotiate A Remote Work Arrangement
- Susan Peppercorn tl;dr: "The author offers five steps: (1) Demonstrate how it will benefit your employer. (2) Show the impact you can make. (3) Be prepared to take a pay cut if you’re relocating. (4) Use data to prove you can be successful working remotely. (5) Don’t expect a one-and-done conversation."featured in #241
How HashiCorp Makes Writing A Priority
- Rebecca Acree tl;dr: Remote work has made documentation essential and Kevin Fisher, chief staff at Hashicorp, provides this advice to managers: (1) Lead by example, larger companies should start with one team to see what works. (2) Make docs an expectation e.g. integrate writing into your interview process. (3) Establish a process defining what needs documentation i.e. a major change in a team or minor change affecting multiple teams.featured in #232
Proof Our Work-Life Balance Is In Danger (But There’s Still Hope)
- Arik Friedman tl;dr: People are "struggling to delineate between work time and personal time, and were prone to working long hours without pausing for a break." We need to find effective ways of “switching off” or risk burning out.featured in #216
Collaborative Single Player Mode
- Radoslav Stankov tl;dr: Radoslav shares Product Hunt's engineering principles. "The goal is never to get blocked," especially as the team is remote. Radoslav guides us through five principles - ownership, small checkpoints, coding best practices, boy scout rules and data driven decisions.featured in #213
How To Debug Distributed Teamwork, As Suggested By New Research
- Leisa Reichelt tl;dr: Atlassian commissioned a study on the impact of switching to remote work, on both teams and individuals. Leisa outlines 5 takeaways, including a possible "innovation drought" due to lack of spontaneous interactions, employees feeling "invisible," and more.featured in #211
Asynchronous Development For Hybrid Remote Dev Teams
- Dan Lines tl;dr: The five tenets of async development: (1) Async is the default form of communication. (2) Git is the central element of the dev process. (3) Management tools are for planning, not updates. (4) Continuous improvement is a daily practice. (5) Dev teams are the core of the business.featured in #210