Great question. When we originally started doing continuous deployment 4 years ago (yes, we were one of the very few companies deploying Docker on production!), we semver’d all production releases — front-end and back-end.

From a developer experience perspective, it was a hassle to manage all that unnecessary complexity. I think that it makes a lot of sense for libraries and on-premise products. From a business standpoint, our salespeople, designers, and product managers didn’t understand what those numbers meant.

So, we ditched it.

Our releases are just simple and obvious: “Releasing new Armoury navigator where users can easily search and equip their items.”

When a release is done, our General channel on Slack gets an automated message that notifies everyone that we’ve released something.

Go team!

Cheers,
Jaime Bueza
Engineering at Battlefy

Have a question about Battlefy’s culture, product development, or engineering discipline? Ask me anything!

Special thanks to Ronald Chen for reading drafts of this.

Jaime Bueza is a Canadian entrepreneur and Y Combinator alum. He has delivered software globally for over a decade to clients including Nintendo, Starbucks, Bacardi, T-Mobile, Verizon, Samsung, ADIDAS, Nike, Electronic Arts, Ritchie Brothers, Kiwi Collections, Cox Communications, Microsoft, and Dell Technologies. When he’s not engaging with customers and clients, he’s playing his favourite esports game, League of Legends.

Battlefy is hiring! We value passion and drive but we also believe that diversity is the key to success for every high growth technology startup. We welcome people from all walks of life.

We take care of the people, the products, the profits — in that order.