The holiday code freezes which many tech companies had in place over the recent holiday period, are now lifted. These typically run from sometime in December each year, until the following January. In this second part of a three-part series, we continue our deep dive into code freezes.

In Part 1, we covered:

• Big Tech approaches to code freezes

• Code freezes at other companies

• Code freeze upsides

• Downsides of code freezes

• Companies which don’t do code freezes

In this article, we cover:

1. Software product categories and code freezes. Web-based products, desktop apps, on-prem software, and embedded products tend to have very different deployment cycles. What are products where code freezes matter, and what are ones where they do not?

2. Mandating a code deployment freeze. Informal and more formal approaches to do so, and questions to ask before deciding on the strategy.

3. Code freeze trends across industries. What are trends within banking, fintech, e-commerce, wellness apps, and other groups?

4. Code freeze alternatives. Code chills, close slush, and business as usual.

5. “Wave and bake” instead of code freezes: Ocado. The grocery retailer platform has no code freeze and uses a unique approach with its isolated, single-tenant environments.

6. Do you need to implement a code freeze? Things that play into this decision, from the maturity of deployment tooling to wanting to create space for staff to recharge for a few weeks.

In the final article of this series, we’ll analyze the trends in the Pragmatic Engineer’s survey on code freezes that more than 150 of you have filled out already. Thank you!

If you’re an engineering manager with performance review calibration meetings coming up: do give Performance calibrations at tech companies a read for advice on how to prepare, and navigate this high-stakes session.

1. Software product categories and code freezes