Environments When developing a piece of software, it is important to think of what kind of environments you may need. Here are a list of questions targeted at helping you identify the needs: Where do you develop? Locally On the we Where do you run you tests? Specific machine Load tests Test-suite Regressions Where do you test a feature that has not been merged? »

Pull Request as a Skill

Pull Request as a skill As Github gets more and more traction (yes! I’m writing this blogpost on Github) some things I’ve learned as an engineer is that not everything is a given. For example, reviewing a pull request (or code in general). I’ve been lucky to have a manager who taught me the importance of a reviewer. It is not somebody who just looks at the code, gives a thumbs up and moves on. »

Acceptance Criteria

Ticket Acceptance Criteria User story: As an engineering manager I want well written acceptance criteria so that completion for a task is well understood, being met, and providing desirable output. This will save time and money in additional effort being required for additional tasks or fixing undesired behavior. It will lead to happy stakeholders that are having their needs fulfilled. Acceptance Criteria: The stakeholders have read and agreed to acceptance criteria to meet the desired outcome. »


Communication When discussing between people, many assumptions are made. It is important to make those assumptions explicit. For example, let us take a house. Can you picture it? Yes? How do you know that you are picturing the same house as me? Let me describe you the house I was imagining and you tell me if it was the same: My house had the following: 243 square meters 4 bedrooms 3 windows a chimney 2 floors … You see the point! »

FactoryGirl (1-1)

FactoryGirl (1-1 Associations) This blog post goes about a common problem I’ve haven’t found much documentation on. It follows issues mentioned of multiple places like here and variations of it. I’ve written some code to illustrate the problem on my Github FactoryGirl-Problem to accompany this. Problem How to create factories such that the association is a 1-1, and all models can be created independently. Models # app/models/user.rb class User < ActiveRecord::Base has_one :profile end # app/models/profile. »