• Riana Ferreira

    How to toe the line with RSpec, Stubs, and RuboCop

    By Riana Ferreira,

    Recently I set up the Rubocop gem for a project. I wanted to use it to ​ensure that my code base aligned with the community Ruby Style Guide. When I ran the tool, I came up against the following error message:

    This message didn't give me any idea of what the problem was, nor what I should do to avoid it in the future.

  • Mikel Lindsaar

    Top 10 Reasons to Outsource Development

    By Mikel Lindsaar,

    Today I was asked by a client to give them some reasons why they should outsource to reinteractive instead of hiring an in house team. They needed to convince their Board the pros and cons of setting up an internal software development team from scratch versus using reinteractive. The project under discussion was the implementation a bunch of key features for their platform as well as a partial rewrite of key aspects.

    Unsurprisingly, I've been asked this question several times by our clients, and my response has almost always been the same; do both.

  • reinteractive

    Some Quick Tips for Tips for Testing Your Rails App

    By reinteractive,

    by Leo Liang

    There might be times when you need to mock a certain value for ENV without overriding other values. This can be easily achieved as follows:

  • reinteractive

    Some Quick Tips for Tips for Testing Your Rails App

    By reinteractive,

    by Leo Liang

    There might be times when you need to mock a certain value for ENV without overriding other values. This can be easily achieved as follows:

  • Gabriel Gizotti

    How to Write a Quality Pull Request

    By Gabriel Gizotti,

    Recently my colleague Daniel wrote an article about Our Code Review Guidelines. But there is another component to this equation: the quality of the Pull Request (PR) that originated it.

    Several years ago, when I was a newbie Rails developer, I submitted my very first pull request to an open source project. It had only a very basic description about what it was doing, with no further details about why or how. This was my PR in its entirety:

  • Daniel Draper

    Our Code Review Guidelines

    By Daniel Draper,

    Here at reinteractive, we care deeply about the quality of our code. We have many processes in place to ensure that the code we produce for our clients is of the highest quality, one of which is a mandatory code review. Before any feature makes it into staging, it must be reviewed by at least one, and preferably two, other developers.

    To quote Wikipedia, a code review is a systematic examination of source code. It is intended to find mistakes overlooked in the initial development phase, improving the overall quality of software.

  • reinteractive

    State Library – Recognition of Excellence for Innovation & Disruptive use of Technology

    By reinteractive,

    The State Library of NSW’s innovative approach to engage online volunteers has received an Excellence award for Innovation and Disruptive use of technology by OpenGOV Asia in a recent awards ceremony.


  • Mark Biegel

    Making iOS & Android apps with Rails & Turbolinks

    By Mark Biegel,

    So you want to build an app? One of the first decisions that needs to be made is one of time and resources. For a business, it is crucial to know your market in order to successfully launch your product. But what about the App market? Which platform you do you choose to launch to first? Apple? Android? Web?

    At this point you might have already considered a HTML5 web app so you can be cross platform and launch to everyone. Or perhaps you decided against it, due to poor performance and not having a “native app” feel.

  • reinteractive

    A holistic approach to your web application

    By reinteractive,

    Back in 1976, the idea of personal computing was somewhat different to that of today. The Apple I computer sold 175 units, and was considered revolutionary for its time. It came with one small catch – you had to build your own case.

    A modern comparison to the original Apple I computer would be the raspberry pi, which has sold an impressive 12.5 million units. It too, requires you to build your own case.

  • Andrew Jennings

    Transparency in Software Development

    By Andrew Jennings,

    Software has been around for more than fifty years and there have been a lot of learnings generated in how to best manage the process of building software. Before the internet it was quite common for a large software project to be initiated, worked on and completed without more than a handful of people knowing what was going on. This lack of transparency led to many dissatisfied stakeholders and sometimes even the software being taken to the trash upon delivery. How do modern software practices avoid the pitfalls of black box software development?

    At reinteractive we use Pivotal Tracker to get all of the features translated into User Stories that are clear for the developer to implement. Once a User Story is completed by the developer the User Story must be accepted by the Product Owner. The Product Owner is the person who decides what the features should and should not do and has ultimate authority. If the Product Owner rejects the developers work Pivotal Tracker will notify the developer that the User Story is reopened and the developer will then attack the User Story again. It is very important for the User Stories to be accepted or rejected quickly because a developer will only hold a complete understanding of the code for a short amount of time.