Les invasions barbares
Some reflections about the controversy generated by the changes at Basecamp, diversity and the power that tech workers have.
El camino del Samurai
En nuestra profesión, como en muchas otras existe la creencia de que para crecer hay que dejar el trabajo técnico y escalar por la pirámide gerencial. Sin embargo no todos desean este cambio. Por suerte en nuestra área, el trabajo técnico nunca es aburrido: los desafíos cambian constantemente.
Fluent assertions in Elixir
Fluent assertions provide a live documentation of what the code actually does. Here's a small library I wrote in Elixir to make them.
Is Go simple?
Golang authors and promoters claim one of the biggest benefits of the language is being *"simple"*
To Care or Not to Care
That is the question! A week ago I had an interview with a potential new client who owns a startup company that is related to sports activities. This potential new client, let’s
Trapped by transparency or trapped by culture?
Transparency has become one of the most popular demands in the recent years and for good reasons. Not so far ago, we went through one of the biggest global financial crisis, caused by
Software Existentialism
A few days ago, in an interesting discussion I was having in a local Agile forum, someone posted the phrase: Doing the right thing precedes doing things right The phrase caught my attention
Refactoring legacy code story
Is the following story familiar? A client knocks to your door, asking for help with a software developed by another vendor. He complains about developers always being late to deadlines and every time a new version is delivered there are plenty of things that are not working properly.
deploy ruby on rails on windows 2008 server and iis 7.0
Deploying Ruby On Rails in a Windows environment can be very painful. I couldn't find any blog which really helped me, so I decided to summarize all the necessary steps I followed to
Benefits of agile software development
Incremental deployment: minimize time-to-market Since agile processes deliver working software at the end of each iteration (typically around 1-4 weeks) and requirements are prioritized by business value, the organization might choose to release
Agile Myths: Shorter iterations are stressful
One of the first steps a new agile team has to undertake is to choose their iteration length. Although I let teams choose the length they feel comfortable with, my general advice is