If we want to write better and higher quality software, it is important we keep track of exceptions, crashes and errors happening in our environment, so we can deal with them. We, at Rootstrap, have created this OS exception tracking tool in order to ease the task of monitoring errors.
Working with ActiveAdmin At Rootstrap, my first assignment was to develop a Ruby on Rails application which uses ActiveAdmin (with ActiveAdmin Addons) as a framework to implement the user interface. I had never used ActiveAdmin before and I found myself reading a lot of documentation of the gem, in some
Here at Rootstrap, we don’t believe in reinventing the wheel. We believe in making things simple and high quality of course. In this blog post, you’ll learn how to start working with Stripe and quickly have fully functioning online payments in your apps. WHY STRIPE? Pros Easy to implement and use
We usually try to solve performance problems by using #includes to get rid of N + 1 queries but this doesn’t always fix the issue; in fact, it can even create more queries under some circumstances. This post shows a few examples of when that happens and how to deal with it.
Are you new to Rails? Or maybe just looking for any cool gem to use in your new API? Here is a list of gems we have on our Rails API Base that we consider a must-have in every Rails API project.
What’s Best Buy Ruby? Best Buy Ruby is a new gem developed entirely here, at Rootstrap. It’s basically a wrapper for the different Best Buy APIs. It offers a simple and intuitive interface that allows users to access the required API with as much customizations as they like. Why use it?
Yet Another Active Form | Using form objects in Rails Apps Introducing Yet Another Active Form yaaf, a gem to ease the usage of the form object pattern in rails apps. Form Object Pain Points The form object pattern is widely used across Rails apps, and yet we tend to write
Introduction In the first part of this article we mentioned some important design principles and how they are not respected when overusing patterns and techniques that come with Ruby on Rails. In this part we will continue to investigate these and how we can mitigate the problems they cause to maintainability. Overused
When big development teams build an API, one of the main challenges that we face is being able to work together on different features while avoiding bottle-necks or other common issues such as conflicting perspectives or avoid overlapping efforts on particular features. Because of this, when we started working on
Introduction Software is constantly evolving, both in specification and implementation. Keeping an extensible and maintainable codebase is therefore crucial in order to deal with these changes quickly and easily. Ruby on Rails comes with a lot of good techniques and patterns out of the box that facilitate this. Nevertheless, some