DEV Community

Oliver Davies
Oliver Davies

Posted on • Originally published at oliverdavies.uk on

Daily or quarterly?

Imagine this scenario.

You have two options on how frequently you can deploy code changes to your application.

Option 1: Every day.

Option 2: Once a quarter.

No more, no less.

I'd choose daily.

I much prefer to deploy changes as often as possible rather than waiting.

I'm much more confident when releasing small changes - even if it's a small refactor, such as changing a variable name or extracting a small helper method.

It might even seem too small to release.

But the smaller the release is, the easier it is to find and fix any issues, and knowing that the next release would only be the following day makes it easier to fix forward instead of rolling back a large release with months of changes.

Here's the thing

Whilst it may seem counterintuitive initially, it's much less risky to release small changes often compared to large changes infrequently.

Which option would you choose?

P.S. Need help or want another pair of eyes on your code? Book a 1-on-1 consulting call or an online pair programming session with a 100% money-back guarantee.

AWS GenAI LIVE image

How is generative AI increasing efficiency?

Join AWS GenAI LIVE! to find out how gen AI is reshaping productivity, streamlining processes, and driving innovation.

Learn more

Top comments (0)

Billboard image

The Next Generation Developer Platform

Coherence is the first Platform-as-a-Service you can control. Unlike "black-box" platforms that are opinionated about the infra you can deploy, Coherence is powered by CNC, the open-source IaC framework, which offers limitless customization.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay