Lessons learned from shipping the same product, every Friday, for 57 weeks
There is no lesson, just ship, even if its broken.
2 comments
I'd like to think that I get the point of shipping fast rather than getting stuck on making it perfect, but what's the point of shipping something that can make your customer lose money, critical data or perhaps even cause an accident? If we are talking about "the rightmost button is red rather than blue" kind of broken, then I can understand the observation, but it is not generalizable, is it right?
You should have guardrails, that catches these critical paths.
Shipping is a muscle, and every engineer knows how to ship good production code, just that we end up spending too much time, on perfecting tiny details. Just have good engineering discipline. Feature-flags, beta releases.
A good question to ask is why aren't you shipping every week, regardless of how critical your feature is.
Shipping is a muscle, and every engineer knows how to ship good production code, just that we end up spending too much time, on perfecting tiny details. Just have good engineering discipline. Feature-flags, beta releases.
A good question to ask is why aren't you shipping every week, regardless of how critical your feature is.