Software Engineering

Welcome to rx!

rx is a command-line tool that makes it easy to create, use, and share development environments. It integrates with whatever tools you're currently using and gives you a long-running VM in the cloud that is kept in sync with your local machine.

Check out our blog post on why we built rx .

Developer environments you can take with you

Discourse | Documentation | Blog | Twitter

Flox is a virtual environment and package manager all in one. With Flox you create environments that layer and replace dependencies just where it matters, making them portable across the full software lifecycle

Install packages from the biggest open source reposi... See more

Before you start working, figure out:

1. What does the business want?


2. Which criteria should I fulfill to call my work “good”?


3. What do I need to do to complete this particular task?

After you’ve finished your work, check:

4. Did I miss anything?

" Knowledge is powerful, be careful how you use it! "

A collection of inspiring lists, manuals, cheatsheets, blogs, hacks, one-liners, cli/web tools, and more.

Created by trimstray and contributors

📔 What is it?

This repository is a collection of various materials and tools that I use every day in my work. It contains a lot of useful information ga... See more

• Terraform Providers: Terraform is primarily used for defining the infrastructure resources. Its strength lies in its vast collection of providers that offer standardized ways to interact with various cloud services (AWS, Azure, GCP, etc.) and on-premises infrastructure. These providers are essentially plugins that understand the specific APIs and

... See more

Using feature flags

It's always a good idea to put new features behind a feature flag.

This contributes to a rollout strategy that can surface user feedback in a much more contained and safe environment.

When thinking about how to rollout a new feature to users, first think about your peers. Many of the Resend team members also use Resend on their ow... See more

More than reading popular books on Design Patterns, two things that helped me write and structure a large codebase better were

reading a lot of good open source codebases (with similar stack)coding and collaborating a lot on the same codebase

I understand the importance of reading general-purpose design patterns, but they might not suit your programm... See more

Some important formatting rules available in this style guide:

• Use four spaces for code indentation


• Limit all lines to a maximum of 79 characters


• Avoid extraneous whitespace in certain situations (i.e., inside brackets, between trailing comma and close parenthesis, ...)

But remember: The formatting rules should make the code more readable. Sometimes, a... See more

We ship early

We constantly review the scope of a project and work toward a v0, not a v1.

That means identifying the most crucial part of a functionality , and pushing the smallest pull request possible to make that happen. In fact, a PR should always be optimized for the speed with which we can merge it in.