Browse by Tags -

Browse by Tags

Separation of Concerns by example: Part 5

In our last example, disaster finally struck our quaint little application. A strange defect showed up, which would be almost impossible to reproduce back on our developer machine. But because we've broken out our dependencies, our CustomerFinder became easier to test. When it became easier, actually...

Posted to Jimmy Bogard (Weblog) by bogardj on 07-17-2008
Separation of Concerns by example: Part 4

In the last part, we finally broke out the caching and data access concerns from our original class. The series so far includes: Separation of Concerns - how not to do it Separation of Concerns by example: Part 1 - Refactoring away from static class Separation of Concerns by example: Part 2 - Specialized...

Posted to Jimmy Bogard (Weblog) by bogardj on 07-10-2008
Entities and the Law of Demeter

The Law of Demeter , and its corresponding code smell, Inappropriate Intimacy , are some of the best bang-for-your-buck code smells that you can address. The basic idea behind each of these concepts is code related to an object should probably be inside that object. It's also known as the Principle...

Posted to Jimmy Bogard (Weblog) by bogardj on 07-07-2008
Separation of Concerns by example: Part 3

We made quite a bit of progress separating out the concerns in Part 2, but there are still some issues with our current design. Other parts in this series include: Separation of Concerns - how not to do it Separation of Concerns by example: Part 1 - Refactoring away from static class Separation of Concerns...

Posted to Jimmy Bogard (Weblog) by bogardj on 06-26-2008
Separation of Concerns by example: Part 2

Separation of concerns is one of the fundamental tenets of good object-oriented design. Anyone can throw a bunch of code in a method and call it a day, but that's not the most maintainable approach. So far, we've looked at: Separation of Concerns - how not to do it Separation of Concerns by example...

Posted to Jimmy Bogard (Weblog) by bogardj on 06-24-2008
Separation of Concerns by example: Part 1

In the prelude to this series, I looked at a snippet of code that took the kitchen sink approach to concerns. Here's what we started out with: public class CustomerManager { [ DataObjectMethod ( DataObjectMethodType .Select, false )] public static List < Customer > GetCustomers( int startRowIndex...

Posted to Jimmy Bogard (Weblog) by bogardj on 06-19-2008
Separation of Concerns - how not to do it

In a recent article on layered LINQ applications in the latest ASP.NET PRO magazine (no link, you have to pay), the author proposes separating your application into three distinct layers: User Interface (UI) layer Business Logic Layer (BLL) Data Access Layer (DAL) I certainly would have agreed, at least...

Posted to Jimmy Bogard (Weblog) by bogardj on 06-17-2008
Failures of aimless large-scale refactorings

At the recent Austin Code Camp, I heard a few stories after my Legacy Code talk about teams attacking their legacy code in prolonged refactoring binges that never seemed to end. Never ending, because no one had a good idea of what success looked like. Once technical debt has built up to a certain point...

Posted to Jimmy Bogard (Weblog) by bogardj on 06-03-2008
PabloTV: Eliminating static dependencies screencast

Nature abhors a vacuum. It turns out she also abhors static dependencies (I have my sources). Static dependencies are the modern-day globals, often exposed through classes named "Helper". I've certainly been guilty of overusing static dependencies in the past, with classes like "LoggingHelper"...

Posted to Jimmy Bogard (Weblog) by bogardj on 05-06-2008
Dealing with primitive obsession

One code smell I tend to miss a lot is primitive obsession . Primitives are the building blocks of data in any programming language, such as strings, numbers, booleans, and so on. Many times, primitives have special meaning, such as phone numbers, zip codes, money, etc. Nearly every time I encounter...

Posted to Jimmy Bogard (Weblog) by bogardj on 12-03-2007

Page 1 of 2 (20 items) 1 2 Next >