apprenticeship Desafíos y Aprendizajes construyendo un Bot de Slack Juli y Debi nos cuentan su experiencia construyendo un bot de Slack, los obstáculos que se toparon en el camino y la sorpresa que se llevaron por lo simple que puede resultar hacerlo!
software engineering Los defaults malvados Trabajar en un proyecto con mucho código heredado siempre es una fuente de grandes aprendizajes. En esta ocasión les presento a los "defaults malvados", como a mí me gustan llamarlos. Son partes de código que pueden hacer mucho daño en una aplicación. Veamos cómo…
api IAR: a mnemonic for a clean controller design ¿How do you design HTTP controllers? ¿How do you make sure responsibilities are correctly assigned? ¿How do you reduce maintenance issues? I'll introduce you to three letters that might help you remember the essentials of every controller…
best practices The principles and habits of healthy software Throughout the last few years of my career, two words have been present almost every day: principles and habits. I believe both can help us be better people and drive positive change around us – in general, but in software in particular.
experiencia Lidiando con emergencias: algunas lecciones aprendidas ¿Qué hacer y, sobre todo, qué no hacer cuando un sistema se cae? Algunas ideas para atravesar lo mejor posible esta experiencia y obtener aprendizajes en el proceso.
best practices A case against nameless objects We name objects, we name variables, we name classes, messages, functions, and types. We name all the time because names allow us not only to reference "something" but also to understand what that "something" means.
tdd Las 12 propiedades deseables de los tests según Kent Beck Un análisis sobre el artículo "Test Desiderata" escrito por Kent Beck, en donde se listan 12 propiedades deseables de los tests.
agile This is not a User Story, or is it? Thoughts about telling and managing stories We surely agree that there’s nothing better than users telling the dev team such stories. But, How should we call them? User stories, backlog items, story cards? And even more important: what is the most efficient way to write and manage these stories?
agile Anonymity vs. Agile maturity... (vs?) Does anonymity play any role in agile teams? Even more, can we pretend to pursue a mature agile environment when members of the team are afraid to take ownership of their opinions? Let's think of a few tips to evolve into trust and self-confidence on agile teams.
best practices Chernobyl Driven Development: 10 lessons learnt from the miniseries Inspired by the success of the series about the Chernobyl disaster, these are 10 lessons learnt from it so you too can make sure your project is a bomb.
programming When we get stuck Have you ever been in that position where your code does not progress? Being such a common problem in our daily work, I have been able to collect some helpful tips that help to overcome this state, which prevents us from keeping our usual flow.
learning From a newbie, to a newbie It's been less than a year since I joined 10Pines, and a little more than two since I started working officialy as a programmer. I don't like calling myself a junior developer because seniorities can be easily misused, as their meanings depend on what the person using these terms is
ruby Ruby On Pains Have you ever heard about the Rails way? I would like to introduce some pains that I've seen and keep seeing in all the Rails projects due to the Rails way... ActiveRecord How many times do we need to find an object in a Rails project? How many times do
best practices Two ways we understand code: Unitary vs Integral understanding There is an often unresolved question in software about comments and documentation. It is said that code should be "self-documenting", thus comments can be a sign of a lack of clarity in the code.