Hernan Wilkinson - 10Pines | Blog

Sign in Subscribe

Hernan Wilkinson

A case against nameless objects

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.

Is Java Dead?

The answer is: of course not!!, but now that I got your attention surely due to the title that mimics the lately hot "Is TDD Dead?" discussion started by @dhh, I would like to concentrate on the real objective of this post that I think it is really more important:

10Pines, una empresa diferente

10Pines, una empresa diferente

Hace unos años atrás cuando nos juntamos para formar 10Pines teníamos muchas dudas sobre lo que pasaría, sobre cómo nos iría, sobre la factibilidad de hacerlo, dudas lógicas de cualquier emprendimiento y cambio. Pero había una visión basada fuertemente en nuestras experiencias laborales pasadas que todos compartíamos y tenía que

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.

OOSCM: Object Oriented SCM - Beyond files - ESUG 2010

OOSCM: Object Oriented SCM - Beyond files - ESUG 2010

OOSCM (Object Oriented Software Configuration Management) is a tool we are developing to better support traits that are unique to object oriented development. Current SCM tools (CVS,SVN,GIT,Monticello, etc) are file based solutions, the file is the minimum versionable element, but when developing with objects files are not

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

Mutation testing

Mutation testing

During the 70s, mutation testing emerged as a technique to assess the fault-finding effectiveness of a test suite. It works by mutating objects behavior and looking for tests to “kill” those mutants. The surviving ones are the starting point to write better tests. Thus, this technique is an interesting alternative

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