Archive | design RSS for this section

The Tight Three: SRP, OCP, and IoC

Today I’m going to elaborate on a statement I made in my┬áInversion of Control (IoC) post: …inversion of control falls naturally out of writing cohesive units that adhere to the single-responsibility principle (pdf) and the open-closed principle (pdf). Inversion of control is about responsibility placement. That is, to use IoC is to consider an object’s […]

Continue Reading

Inexperienced Quality

This post was imported from blogger, to see the original, likely better-formatted post see kalebpederson.blogspot.com. >When I first started programming I concentrated on one thing, making my program work.  Not only was that the only thing that I concentrated on, but it was the only thing I was taught.  My studies in computer science didn’t […]

Continue Reading

Don’t Architect, Refactor

This post was imported from blogger, to see the original, likely better-formatted post see kalebpederson.blogspot.com. >The test-driven development mantra is “red, green, refactor,” but we far too often let other things creep into the process.  One of these things is domain knowledge. Back in February, Gojko Adzik described his experience with Keith Braithwaite‘s “TDD as […]

Continue Reading