How a small team ships reliable software every week

The habits, tools and reviews that let our engineers release often without breaking what clients depend on.

Engineering Team · 1 min read
An open-plan software office with the team at work
An open-plan software office with the team at work
On this page
  1. 01Keep every change small
  2. 02Safety nets we rely on
  3. 03Listen after you ship

Key takeaways

  1. 01Small pull requests get real reviews; big ones get skimmed.
  2. 02Tests, staging, feature flags and rollback are the safety nets.
  3. 03Release mid-week and watch errors closely after every deploy.

Reliability is not about moving slowly. Our clients run hospitals, banks and shops on our software, so a bad release is felt immediately. The answer we have found is to ship smaller changes, more often, with safety nets at every step.

01

Keep every change small

A change that can be reviewed in fifteen minutes gets a real review. A change that takes two hours gets a skim. We split work so each pull request does one thing well.

02

Safety nets we rely on

  • Automated tests on every pull request, with the critical paths covered first.
  • A staging environment with realistic, anonymised data.
  • Feature flags so unfinished work can ship switched off.
  • One-click rollback, rehearsed regularly.
03

Listen after you ship

Error tracking and a direct line to client support close the loop. The first person to notice a problem should be us, not the customer.

Written by

Engineering Team

Voleergo Solutions. We build and support business software for teams across Kerala and beyond.

Talk to the team

Want this working in your business?

Book a free call and we'll show you how it applies to the way your team works.

Voleergo team · online

Hi 👋 Have a project in mind? Chat with us on WhatsApp.

Chat with us