Stop Writing Scenarios That Test Everything Through The View
Following on from my last post, I wanted to mention a common anti-pattern that Kevin's case against cucumber mentioned. Scenarios that are too focussed on the user interface. Scenarios written as an imperative set of instructions for a machine to follow. Scenarios like this.
This Gherkin's Not For Reading
Recently Kevin Liddle made his case against cucumber. In the article he outlines several problems he experiences working with cucumber. One of his key arguments is that non-technical team members don't read the scenarios written by developers.
How to fix your postgres install when you've run `brew upgrade` without backing up Postgres data over a major version
Doh! Third time now. Seriously. I just don't notice that it's a version upgrade, and set it off. Then "oh *!#$"
MVP – A child's eye view
A little background.
Recently, my son decided he would like an iPod touch. (well, really, he wanted an iPhone, but he's to young for a phone...) We felt, if he wanted something that big, he ought to save for it to appreciate the amount of money it was. He had some birthday money saved and so the conversation continued.
Pairing in a Tunnel
We are keen that people can work in the spaces that makes them feel most
comfortable, and allows them to organise their life how they want. Working
remotely gives people that opportunity.