Content pfp
Content
@
0 reply
0 recast
0 reaction

Andrew Lee pfp
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
7 recasts
27 reactions

Andrew Lee pfp
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 pfp
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

0xRider pfp
0xRider
@0xrider
Sounds like this works well for a small startup. Curious if you think a medium sized org (100-250 ppl) could easily adopt the same practices? I’ve found at larger companies lots of people are code averse even for small incremental things or reviewing RFCs
1 reply
0 recast
0 reaction

Andrew Lee pfp
Andrew Lee
@startupandrew
Yes, I do think it can be done! It takes serious commitment though -- you need to be willing to hire & fire based on willingness to learn these tools across all functions.
0 reply
0 recast
1 reaction