Do you need a staging environment? We've written this short blog post to share how an alternative approach is saving us time, and helping us ship better code.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

Squeaky uses a flat branching process to ship code to production. We only merge code into the main branch when it is ready to go live. This means we don’t have to wait for changes to be validated in development. We believe it’s helping us to ship faster, and lower the number of issues on production.

Why we don’t use a staging environment

What’s wrong with staging environments?

<p>Interesting approach - I’m working on a big enterprise project and we have staging -&gt; rc -&gt; release flow (really things are even harder), but it works good for us and I don’t think that approach suggested it the article will work for really big project. But this is something I will think about organising release processes for smaller projects</p>
