inaka

Latest blog entries

/
SpellingCI: No more spelling mistakes in your markdown flies!

Feb 14 2017 : Felipe Ripoll

/
Fast reverse geocoding with offline-geocoder

Do you need a blazing fast reverse geocoder? Enter offline-geocoder!

Jan 18 2017 : Roberto Romero

/
Using Jayme to connect to the new MongooseIM REST services

MongooseIM has RESTful services!! Here I show how you can use them in an iOS application.

Dec 13 2016 : Sergio Abraham

/
20 Questions, or Maybe a Few More

20 Questions, or Maybe a Few More

Nov 16 2016 : Stephanie Goldner

/
The Power of Meeting People

Because conferences and meetups are not just about the technical stuff.

Nov 01 2016 : Pablo Villar

/
Finding the right partner for your app build

Sharing some light on how it is to partner with us.

Oct 27 2016 : Inaka

/
Just Play my Sound

How to easily play a sound in Android

Oct 25 2016 : Giaquinta Emiliano

/
Opening our Guidelines to the World

We're publishing our work guidelines for the world to see.

Oct 13 2016 : Brujo Benavides

/
Using NIFs: the easy way

Using niffy to simplify working with NIFs on Erlang

Oct 05 2016 : Hernan Rivas Acosta

/
Function Naming In Swift 3

How to write clear function signatures, yet expressive, while following Swift 3 API design guidelines.

Sep 16 2016 : Pablo Villar

/
Jenkins automated tests for Rails

How to automatically trigger rails tests with a Jenkins job

Sep 14 2016 : Demian Sciessere

/
Erlang REST Server Stack

A description of our usual stack for building REST servers in Erlang

Sep 06 2016 : Brujo Benavides

/
Replacing JSON when talking to Erlang

Using Erlang's External Term Format

Aug 17 2016 : Hernan Rivas Acosta

/
Gadget + Lewis = Android Lint CI

Integrating our Android linter with Github's pull requests

Aug 04 2016 : Fernando Ramirez and Euen Lopez

/
Passwordless login with phoenix

Introducing how to implement passwordless login with phoenix framework

Jul 27 2016 : Thiago Borges

/
Beam Olympics

Our newest game to test your Beam Skills

Jul 14 2016 : Brujo Benavides

/
Otec

Three Open Source Projects, one App

Jun 28 2016 : Andrés Gerace

/
CredoCI

Running credo checks for elixir code on your github pull requests

Jun 16 2016 : Alejandro Mataloni

/
Thoughts on rebar3

Thoughts on rebar3

Jun 08 2016 : Hernán Rivas Acosta

/
7 Heuristics for Development

What we've learned from Hernán Wilkinson at our Tech Day

May 31 2016 : Brujo Benavides

/
See all Inaka's blog posts >>

/
Opening our Guidelines to the World

A photo of Brujo Benavides wrote this on October 13, 2016 under guidelines, inaka, work .

In a Nutshell

In an effort to provide visibility on our internal processes both for our clients and for the people who want to work in our company, we're publishing our work guidelines on Github. We've done this in the past for particular languages, such as Erlang and Swift. The main difference this time is that what we're sharing is not tied to a particular language or technology, it applies to our company as a whole.

We're open now!

A Little Bit of History

A couple of years ago, approximately when the company moved past its 25-employee-size landmark, we realized that our culture was not going to build organically just by itself anymore. It was something we (as company employees) should actively care about. So, Martina (our CEO) and I built a team of Standarizers (we could've probably found a better name). Their mission was not to set standards, but to discover them.

We believe that what we now call guidelines is something that you can't impose on the people, but when it naturally flows, you can see it, and document it.

Such a discovery process is a collaborative effort. We carry most of our collaborative efforts on github, so it felt natural to keep our guidelines there as well.

With the help of the standarizers team, we wrote the first version of our guidelines. Then, with the help of everybody in the company (through issues and pull requests) we made them grow.

Eventually, we ended up talking about them and sharing bits and pieces of them with people outside our company. That was when, inspired by some people we admire (like Yegor and Oren), we decided to just make them public!

What You'll Find There

So, what are these guidelines all about?

Our guidelines are written as if they were intended to be read by a newcomer (i.e. someone just joining our organization); but even if that's not your case, and you are not (yet :P) interested in working with us, you can still find many things that can work as sources of inspiration for you to define how to work in your own company. And, of course, our guidelines are in constant evolution; so if you have recommendations for us or you want to let people know how you work on your own company, please don't hesitate in writing about it on the comments.

Part of the subjects covered there are:

  • The roles and responsibilities of the different employees within the company;
  • The tools we use and how we use them;
  • The methodologies we practice;
  • The standards to which we subject our work and the products we build;
  • The benefits we provide to all of our employees;
  • Our commitment with the communities behind the languages we use.

But the most important part that we included in the guidelines are our core values and the lessons we've learned over time. That's what we really want to emphasize and what we believe is key for new employees to understand and share.

Quick Note about our Parent Company

The guidelines you'll find in our repo apply specifically to Inaka, but since we are part of Erlang Solutions, they are of course influenced by and in sync with the ways in which the whole company (Erlang Solutions) works.