I worked for several startups over the years, but none of them had core values. Only well-established companies have core values, - so is the myth - and even there, they might have been only a cute decoration on the wall, nothing more. Nobody knows about them, nobody lives by them.
At Hireology, we know our company's core values by heart. Every single leadership team meeting on Monday starts out with reciting our company's core values. Here they are:
- Pathological Optimism
- Create Wow Moments
- No A$$holes
- Eager to Improve
- Own the Result
A company's core values might not describe the Engineering Team's core values when it comes to writing software. I felt our team needed something more specific to guide our decisions. Here is the letter I wrote about a year ago, when I announced our Engineering Core Values.
The company core values define the culture of our company, but it does not describe our engineering values.
The goal of the Engineering Core Values is to keep our team focused on what makes a product great from our perspective. When you write or review code, when you evaluate a change, try to consider these core values. If we follow these three simple guidelines, I am confident our application will be an outstanding one, and we will succeed.
Here they are, our Engineering Core Values:
- Performance is paramount
- We collect data
- Trusted code
2. We collect data We believe in the value of capturing data. An event never happened if we have no data about it. As our business grows, data will be increasingly important to us. Capturing all the changes would be an overkill, but our data analytics engine will collect more and more data as we grow it. Our Rails app's database will always be an online transaction processing (OLTP) database, it will never store historical data for analytical purposes. The data analytics engine will do that.
3. Trusted code When we took over the app from contractors the application had no tests at all. Zero! Look how far we have come!! Today we have more than 1600 specs and 89 automated scenarios! Whenever you check in code, make sure the code is something you trust. What does trusted code mean? You feel confident about changing a routine you wrote two weeks ago. Specs and acceptance tests are surrounding your code, you know your change will not have unwanted and unexpected ripple effects. You trust that code, knowing your change will not break two other things later in QA or in Production.
Thank you, and please keep these Engineering Core Values in mind.Attila
I printed our Engineering Core Values announcement and put it on the wall outside of my office, where all our employees can see it. We need to live by them, it can't be just an ornament on that wall.