Building at BV: How we work - What’s important

I've been at BrandVerity for almost 3 years and I'm really proud our willingness to try new things.

When I joined our process was pretty informal. We used a poster board and moved sticky notes in a kanban type setup. Everyday we'd have a stand up and we'd talk about the tasks, sometimes in great detail.

If something was urgent we'd add it to the board. If one of the engineers thought something needed to be done, they would do it. To be honest it worked pretty well for the small size of our team (5 developers at the time).

Fortunately, we were able to keep growing and we quickly discovered that the stickies on the poster board didn't quite work for us anymore.

As the team/company has grown we’ve tried several new processes. Some of them we’ve kept, some didn’t work for us. But we always try to meet these high level goals:

Our systems are built with some principles in mind:

• Scalability
• Resilience
• Transparency
  

Here’s a very basic overview of our architecture. I'll start with a very high level overview and break it down as we go. I’ll also talk about how our principles are expressed in our system.

Overview:

At the highest level we have 3 major parts - The frontend, data storage and the backend. The frontend

Howdy!
In this series of blog posts I’ll go through some of what it’s like to be an engineer at BrandVerity.
Some of the topics include: