Content
@
0 reply
0 recast
2 reactions
Andrew Lee
@startupandrew
Here's how our developer tooling allows us to ship 100+ features per year with a team of 9. I’ll cover 🧵 - Our monorepo - One-command local build - Shared multi-platform code base - CI - Multiple staging environments - Fast deployment & easy rollback
3 replies
6 recasts
22 reactions
Andrew Lee
@startupandrew
Our development environment is central to how we work, not just for engineering, but for *everyone*, in every function. Not only are all of our apps in code, but so is our website, blog posts, emails, marketing assets, etc. Git is the common language we speak across the whole company.
1 reply
0 recast
1 reaction
Andrew Lee
@startupandrew
Every person, from me, to our growth specialist, to our designer, is working directly in code: testing & reviewing things locally, making changes, and shipping.
3 replies
0 recast
1 reaction
Andrew Lee
@startupandrew
How do we enable this? With a monorepo. All of the code for our core product, including web, iOS, Android, backend code, k8s config, etc. all lives in a single repo. This makes setup easy, and it gives us versioning & code review for changes across the entire stack. It also makes testing easier.
2 replies
0 recast
0 reaction
Andrew Lee
@startupandrew
We are obsessed with making our local development environment work with only a single command -- including loading test data. We use Bazel for our builds, and all of our configuration is code, checked into git. This makes getting started fast and keeps everyone's dev env moving in sync as our infrastructure evolves.
3 replies
0 recast
0 reaction
Matt Schoch
@md5
Recently shifted to monorepo approach for similar reasons. We started with nx - any experience there or reason to pick bazel?
0 reply
0 recast
0 reaction
