Blog

It has come to my attention of late that there is some clear separation in the testing world about how we write our tests and the level they are written at.  In this separation I see 2 groups of people:

- The first group enjoy testing their applications at each level of the stack; model tests for models, controller tests for controllers, view tests for views, or if you prefer integration tests to test the integration of models, views, and controllers and all your other code as a whole, i...

I discovered Travis CI the other day. It's a distributed platform providing web-based continuous integration for your projects. Erm... right?

In simpler terms; Travis tests your projects against a wide variety of setups. It monitors your code repository and re-runs the tests when a change is detected. This is especially useful if you're building something that needs to work with significant tolerance regarding environment and platform- gems, for example.

After getting over the fac...

Recently, I've been building gems in an attempt to get some content out into the open-source community and learn a thing or two along the way.

There was one in particular that gave rise to some interesting challenges. The bulk of the gem involved parsing a complex data structure, manipulating it in some way, then composing it back to the fathoms of complexity from whence it came. In plainer terms; it reads a file, does all the things, then writes a file- still with me? In this instance, t...

@sleepyfox asks:

"I'm having trouble with my Agile team, how do I make them more self-organising?"


Dear sleepyfox,

You will struggle to "make" a self organising Team due to the very nature of the dynamic- however you can help to guide them in the right direction by empowering them to direct themselves within the boundaries of the Sprint with the support of the business. This will help them to feel more invested personally in the success of the project and so take more r...