Software Development

Refactoring techniques and Design Patterns have been extensively propagated and advocated for over a decade now. Why we still find hard to change, anaemic or overly complex object oriented structures? What is missing in our design practices?

In this series, we use Fowler’s didactic Video Store program to show practical advanced refactoring strategies that effectively improve design simplicity, expressiveness and flexibility.

This post resumes the Revisiting Fowler’s Video Store series. After making the relevant domain concepts explicit, we focus our refactoring process on another aspect of domain semantics, studying contextual variance under the perspective of the following issues:
1. The Passage of Time;
2. Changes in the Video Classification;
3. Changes in Rental Prices and Terms.

In this post, we bring the domain semantics to our refactoring process. We want a deeper perspective to analyse modularity problems and to direct improvements towards greater relevance to our design objectives.

Have you ever found a program you needed to add, change or even fix a simple function, but you just didn’t know where to start or were afraid of breaking the program’s logical consistency?

Refactoring is a modularity improving technique that is indispensable in the skill set of any professional software developer. In this post, we use Refactoring to effectively adopt an object-oriented design syntax and make a program like this easier and safer to work with.

The perceived credibility of an IT professional goes beyond his or her personal competence and integrity; it is grounded in trustful relationships. This post is a reflection on our professional relationship style. Is it effective to create and nurture trustful relationships?