Be the first to like this
When writing software we never get directly to a good code design, to a design that minimizes the cost of change. Instead we improve the design of our code by gradually refactoring it. We put into the code the knowledge we learn by experimenting with it. In general, a loose coupled design is better, is less resistant to changes. Knowing patterns of refactoring, and simple heuristics to identify refactoring opportunities increases our efficiency in getting to a good code design.
In this presentation I demonstrate how by refactoring in small steps, by following some simple rules and by applying some simple heuristics of increasing the cohesion of our classes and functions, we can get to a looser coupled design, to a better code design. I will walk you through this process by taking a piece of C# code and work on it during the session, improving it together with you.