Warp’s tech stack

• Rust for the terminal
• Go for our server
• React and Typescript for our web app

What tools do engineers use?

• Design: Figma
• Builds/CI: GitHub Actions
• Source control: GitHub
• Issue tracking: GitHub issues for external tracking and bug reports. Linear for internal issue tracking.
• Error reporting: Sentry
• Monitoring/logs: Sentry, Metabase
• Chat: Slack
• Wiki: Notion

<aside> 💡 Can developers pick their own tools? Yup, except everyone uses Warp as their terminal, since that's our product. 😊

</aside>

How to make a change to Warp’s codebase

When multiple developers are working on the same codebase, it’s important that everyone follow the same procedure for making changes.

How to make a change?

1. Create a local branch from the main (server) or master (client) branch. It’s where the up to date code lives and features and bug fixes start from.
2. Make a small, incremental change, test it locally.
3. Review your own code before sending it to someone else to review.