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.
"Los verdaderos desarrolladores no usan if". ¿Por qué alguien querría eliminar el if? ¿Qué tiene de malo? Aquí les cuento por qué y cómo lograrlo.
Working on a project with a lot of legacy code always leaves good lessons. This time I’ll present you what I like to call “evil defaults”, pieces of code that can do a lot of harm in any software project.
How can we make our code less error-prone? In this post I explore some of the ways we can do so. Join me!
This post will try and maybe fail to convince you that using `null` in your code is an error. For those of you willing to listen, here are my reasons to stop using it.
"Real devs don't use if". Why would somebody want to eliminate the if clause? What's wrong about it? Here I tell you why and an example on how to do it.
One of the things that makes TDD difficult to apply on existing code (or just “legacy code”) is the dependencies that the object subject to test may have. The more “dependencies” the object
Today we all know now that variables should not be called x or y, not even i nor n, when we use the famous “for”... but do you really know why? have you
One of the recurrent problems I see when teaching OO design is the “names” used by the programmers to name classes, methods, etc.
Patagonia is a conference registration web based system written in Pharo using Seaside, whose main purpose is to fulfill the ESUG conference registration needs. It was developed at 10Pines under the sponsorship of
When talking about Smalltalk, there is definitively an over use on the possibility to add messages to Object class. It is so easy to do it, that people usually do it just to