How I ship projects at big tech companies | sean goedecke
seangoedecke.com · 2,340 words · saved by 8 readers
What I think about when I'm lead engineer on a project
I have shipped a lot of different projects over the last ~10 years in tech. I often get tapped to lead new ones when it’s important to get it right, because I’m good at it. Shipping in a big tech company is a very different skill to writing code, and lots of people who are great at writing code are terrible at shipping. Here’s what I think about when I’m leading a project and what I’ve seen people get wrong. Shipping is hard The most common error I see is to assume that shipping is easy. The default state of a project is to not ship : to be delayed indefinitely, cancelled, or to go out half-ba
saved by
related reading
- How I've run major projects | benkuhn.netbenkuhn.net
- 37signals — Seven Shipping Principles37signals.com
- My Approach to Building Large Technical Projects – Mitchell Hashimotomitchellh.com
- Always Be Shipping - Adam Drakeadamdrake.com
- How and why we built our startup around small teamsnewsletter.posthog.com
- Good Engineer/Bad Engineerterriblesoftware.org
- The saddest "Just Ship It" story everkitze.io
- #define CTOblog.gregbrockman.com
- Joshua Goldenberg on shipping togethergoabstract.com
- Laid offlearnlearnlearn.substack.com
- Introduction | Shape Upbasecamp.com
- Finish your projectsgithub.com