Browse by Tags

• BDD
• Behavior-Driven Development
• C#
• Domain-Driven Design
• Legacy Code
• LINQ to SQL
• Misc
• MSBuild
• PabloTV
• Patterns
• TDD

• 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... Posted Jul 17 2008, 08:23 AM by bogardj with | with 13 comment(s) Filed under: Refactoring, LINQ to SQL

• 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... Posted Jul 10 2008, 07:57 AM by bogardj with | with 11 comment(s) Filed under: Refactoring, BDD, Behavior-Driven Development

• 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... Posted Jul 07 2008, 07:51 AM by bogardj with | with 11 comment(s) Filed under: Domain-Driven Design, Refactoring

• 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... Posted Jun 26 2008, 11:14 PM by bogardj with | with 11 comment(s) Filed under: Patterns, Refactoring, LINQ to SQL

• 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... Posted Jun 24 2008, 08:17 AM by bogardj with | with 20 comment(s) Filed under: Refactoring

• 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... Posted Jun 19 2008, 10:12 PM by bogardj with | with 14 comment(s) Filed under: Refactoring

• 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... Posted Jun 17 2008, 08:00 AM by bogardj with | with 27 comment(s) Filed under: Refactoring, LINQ to SQL

• 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... Posted Jun 03 2008, 10:37 PM by bogardj with | with 12 comment(s) Filed under: Refactoring

• 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... Posted May 06 2008, 07:24 AM by bogardj with | with 11 comment(s) Filed under: Legacy Code, Refactoring, BDD, TDD, PabloTV

• 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... Posted Dec 03 2007, 05:42 PM by bogardj with | with 4 comment(s) Filed under: Refactoring

• Smells to refactorings quick reference guide

  This post was originally published here . Two books I like to have close by are Martin Fowler's " Refactoring: Improving the Design of Existing Code " and Joshua Kerievsky's " Refactoring to Patterns ". It's not that productive... Posted Sep 10 2007, 01:51 PM by bogardj with | with no comments Filed under: Refactoring

• Template Delegate Pattern

  This post was originally published here . I've had to use this pattern a few times, most recently in Behave# . It's similar to the Template Method pattern , but doesn't resort to using subclassing for using a template method. Instead, a delegate... Posted Aug 29 2007, 08:51 PM by bogardj with | with no comments Filed under: Patterns, C#, Refactoring

• When Technical Debt leads to bankruptcy

  This post was originally published here . One of my favorite technical metaphors is Technical Debt . It's easy to recognize a system that is collapsing under its own weight with Technical Debt. Those are the ones that are pretty much impossible to... Posted Jul 05 2007, 05:21 PM by bogardj with | with 2 comment(s) Filed under: Misc, Refactoring

• Refactoring NAnt and MSBuild build scripts

  This post was originally published here . A while back, I talked about the harmful effects of "Copy Paste" . While editing some NAnt and MSBuild build scripts, I forgot about the evil twin of "Copy Paste", which is "Find and Replace"... Posted May 29 2007, 01:22 PM by bogardj with | with no comments Filed under: Refactoring, MSBuild

• Evils of duplication

  This post was originally published here . Everyone is guilty of using "Ctrl-C, Ctrl-V" in code. During development, we may see opportunities to duplicate code a dozen times a day. We're working on some class Foo that needs some behavior... Posted Apr 16 2007, 08:53 AM by bogardj with | with no comments Filed under: C#, Refactoring