Even though we are a Rails development team, we use WordPress for our blog. We love Rails, but WordPress provides a robust solution for our blogging needs. And lately, we have been experimenting with Docker + WordPress.
So, why Docker?
There are quite a few straightforward reasons why we use Docker with WordPress, namely:
- Docker reduces clutter.
- We can run a couple of Rails applications and WordPress instances on the same server.
- It helps with version conflict management in Rails apps
- It allows for the duplication of a production server into staging for testing purposes.
Not so long ago a customer requested that we provide the highest server reliability that we could. The application was pretty big, with about seven servers per environment. We needed to increase reliability in web servers and databases. In this article, I’ll explain how we achieved that from the database side.
While searching for options, we found that MongoDB (which was the database engine we were using) offered several options that increase your database reliability, i.e.:
MongoDB – Sharding
MongoDB – Replication
We went for MongoDB Replication –also known as Replica Set– because our customer needed a solution ASAP, and the configuration needed is minimal. Besides, it offers whole database replication, which we needed to implement other security measures, like backups.
Enough context for...
Have you seen a team that doesn’t understand the reason behind developing certain feature? Have you had a sprint review where more than a half of the features are rejected? Or that the team develops a huge feature that doesn’t add any significant value to the product? If you’ve seen this in your project, it might mean that your Product Owner is doing something wrong.
We can consider the Product Owner to be the main stakeholder. She should own the product and determine direction. The reality is that the Product Owner role is different from that of a project manager, since she has the passion, the vision, and, unlike a project manager, has to say no to people. Let me explain.
When we start working with Angular, we come to this question very quickly: how can we set our controllers to communicate with each other? Which option is the best?
It is typically assumed that in Angular.js there should be only one controller per view. Sometimes, however, we have no choice but to have two controllers within the same page, and they will need to interact with each other.
Are you happy with the app you use to do feature estimation in your Scrum process? We weren’t either. How about the way you collect feedback after a sprint is done? We’ve got you covered.
Introducing Planning Poker: the tool to manage Scrum pointing sessions AND retrospectives in the same place, under an Open Source license, for free! How sweet is that? In this post, we’ll tell you why we built this app, and what were we looking for (spoiler alert: you will see those expectations fulfilled in our app). Then, we’ll show you how it actually works, on a step-by-step tutorial to master the main features. Finally, we’ll refer to the technical stack and the reasons behind choosing those specific technologies....
If you are one of those devs who uses the terminal a lot and ends up with way too many tabs open, or practices pair programming, then this post is for you. During the last months, I’ve started using Tmux a lot. Since I’ve found it to be very useful, I thought I would write a post where I share a few recommendations and pro-tips. I’ll show you what Tmux is and how to use it in combination with Vim to make a more effective and elegant use of the Terminal.
So, this is what we’ll cover:
- Tmux basics.
- The best of Tmux
- Fast text navigation and copying
- And a very neat pair programming feature
- Tweaks to improve Vim integration.
- Colorscheme background
- Static cursor shape
- Indentation at pasting
As a part of our series of interviews with members of the TangoSource team, today I’d like to introduce you to one a growing talent on our development team. Introducing César, he’s been part of the team for two years now, and we are proud to have him on board.
Q. Could you please introduce yourself briefly?
A. My name is Cesar Gomez, and I was born and raised in Colima. I am 26 years old, and I’ve been into web dev professionally for the past two years. I started as a trainee at TangoSource in January 2013. I remember that when I was 16 I couldn’t even turn a computer on,...
The World Wide Web Consortium (WWC) introduced Canvas with HTML5 last year. We think it’s a pretty interesting drawing tool. So, we decided to experiment with it and share our findings in the form of a short tutorial in this blog post. We’ll cover the basics and mention a couple of recommendations for deeper learning.
Certainly, the concept of ‘remote work’ sounds very tempting…
(Photo credit: Jan Kaláb)
… but don’t let that fool you! Working remotely is a double-edged sword.
I have found three main areas you need to take care of if you want to stay productive while working remotely: discipline, communication, and time zones. Keep reading to see why I am saying this, plus some tips that will prevent you from performing poorly. And who knows, perhaps you’ll end up having a better performance working remotely than if working onsite.
I remember the first time I worked remotely, it felt awesome! I could start or pause work at any time I wanted. And that feeling of freedom, of being able to go to the kitchen and grab...
A couple months ago I heard one of our team members say that “Scrum wastes a lot of time on meetings” and that “most of them are not even necessary”. If we look at this idea from the developer’s point of view it’s understandable, being part of a Scrum ceremony, listening to everyone when sometimes the topic has nothing to do with her role or feature, might seem boring. But did you know that a single team member can screw up an entire project (even without noticing) by not following a scrum process correctly?
According to the methodology, there are some events in which the developer has to participate, but there are other equally important tasks that the developer needs to do...