TechPrufer
Get started
Slack
Slack logoSlack · Feature trail

Remote Development Environments

3 posts · Jun 2019 – Jun 2022

What this trail covers

This thread tracks the evolution of Slack's developer productivity tooling, focusing on the implementation and adoption of remote development environments. Initial posts detailed the challenges of local development setups, including dependency management, resource intensity, and cross-platform inconsistencies. This post introduces the Remote Development Environments project, which provides engineers with on-demand, isolated AWS EC2 instances for coding, testing, and debugging. The system leverages Chrome Tracing to diagnose performance issues in the Electron app and explores potential browser-based self-profiling APIs.

All Slack trails
  1. Remote Development at SlackThis post details the inception and implementation of Slack's Remote Development Environments project. It describes the transition from local development with HHVM and Docker to a cloud-based solution using AWS EC2 instances. Key technical contributions include the development of a `slack remote-dev` CLI command for provisioning environments, integration with AWS Auto Scaling Groups for maintaining a fleet of ready instances, and the use of VSCode Remote SSH for a seamless development experience. The post also covers strategies for environment customization via `~/.remote-dev-home`, short-lived instance management for cost-effectiveness, and the ability to easily scale instance specifications (e.g., from C5.2xlarge to C5.4xlarge) to accommodate evolving needs like frontend builds. It presents adoption metrics and qualitative feedback from engineers.
  2. Development Environments at SlackThis post details the technical implementation of Slack's remote development environments, including the use of `slack sync-dev` (a wrapper around `fswatch` and `rsync`) for file synchronization, local webpack builds served over localhost for frontend changes, and the evolution of dev environment scaling from a shared instance to on-demand EC2 provisioning and deprovisioning. It also highlights the development of over 60 command-line tools to simplify development tasks.
  3. Chrome Tracing for Fun and ProfitThis post details the use of Chrome Tracing to diagnose performance issues in Slack's Electron desktop application. It explains how to collect and analyze trace data using `chrome://tracing` and the Electron `contentTracing` API, demonstrating its utility in identifying inter-process communication bottlenecks that are not visible in standard DevTools performance profiles. It also touches upon the future possibility of JavaScript self-profiling APIs for browser-based debugging.