First was Friendster, after it came Myspace and finally Facebook appeared. The same happened with Altavista that was replaced by Yahoo and time after it was when Google came to be the standard of search machines. This is a post with some examples that proved that there’s always room to improve the “de facto” model. →

It’s an old pattern included in the GoF collection. It’s very popular in the construction of widgets but it’s less known for it’s ability to implement multiple inheritance in a single inheritance language. In this post we will make use of both possibilities.

Reserve exceptions for exceptional cases, they are hard to read and maintain. Don’t use them for control flow. Think of a logger as part of your error handling system. Scope Exceptions by modules using extends and also implements indirections. Minimize the number of catchs. And most important, organize exceptions hierarchy by how they are being captured.

I’m a top-down thinker so I like to bear in mind the big picture when I’m solving a problem. This is why it really helps me doing diagrams of the classes I’m coding. In this post I will include a big UML design of what I consider the basic parts of a web application. →

Very often my coworkers ask me about which are the programming patterns I tend to use the most in my POO designs. In this post I’m linking some of my favorite references.

A year ago I started using AWS services. Before that I’ve had a reserved server in OVH. The ease and the features of Amazon really surprised in a very positive way and this post is dedicated to those who are still thinking if it’s worth it to change.