object design - 10Pines | Blog

Sign in Subscribe

object design

A collection of 9 posts

The Evil Defaults

software development Featured

The Evil Defaults

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.

Limit the Problem Space!

Limit the Problem Space!

How can we make our code less error-prone? In this post I explore some of the ways we can do so. Join me!

There are null reasons

object design Featured

There are null reasons

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.

Trust in objects. They have the right to decide.

object design Featured

Trust in objects. They have the right to decide.

"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.

Language’s type system and their impact in breaking dependencies

Language’s type system and their impact in breaking dependencies

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 has, the more difficult it will be to test it, almost for sure. What makes things even

The Art of Naming

The Art of Naming

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 ever had trouble naming a variable? and what about a method (message) or a class? The truth

About names when designing with objects

naming Featured

About names when designing with objects

One of the recurrent problems I see when teaching OO design is the “names” used by the programmers to name classes, methods, etc.

Design principles behind Patagonia - ESUG 2010

Design principles behind Patagonia - ESUG 2010

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 ESUG. It has been develop using some design principles that were "grown" developing other two systems, being

About inheritance as means of reuse

About inheritance as means of reuse

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 get something working fast, even if the coding is poor. There are a lot of messages (mainly