We recently made the decision to remove Recompose entirely – which was a large endeavor. It touched over 200 files, and in some places was deeply coupled to core functionality of our app.This post covers why we decided to replace Recompose.
In our last post, we explored the pros and cons of Recompose and why we decided to remove it from our codebase. This post includes the strategy we used to approach the large task of implementing that refactor.
Here's how Rainforest QA made the decision to upgrade our DevOps teck stack and move from Heroku to Google Cloud Platform (GCP) and Google Kubernetes Engine (GKE).
We’ve been using Heroku extensively at Rainforest QA since early 2012 to run our automated QA testing service. It’s stable, it makes economic sense, and it precisely suits our needs. Here are the main arguments I hear against Heroku, and why I think they are (mostly) fallacious.
In this post we're going to look at optimal environments for webapps. This is part two in a series - the first post looks at what are environments for?
In this post we explain the basics of how to handle database migrations properly and show some real world examples. Learn how to achieve zero downtime database migrations.
Version control is something that every shipping team uses, but there's not a lot of talking about the right way to do it. Used properly it can improve your code culture and help you move faster.
Everyone should be able to benefit from MongoDB's power and simplicity, and so I've outlined some common and not-so-common things that hackers should know about MongoDB.