Last week, Cauê and I were refactoring some classes in our systems and faced an interesting situation.
In our application we have a notifications system. It is quite simple; notifications are read from a text file and shown in a small information box in the home page. The MVC controller –it’s a Java application and we […]
Archive for the 'everyday tales' Category
Everyday Tales: We Call it Unit for a Reason
Published by June 7th, 2010 in agile, case study, components, everyday tales, java, object orientation and software design. 1 CommentEveryday Tales: Anatomy of a Refactoring – Part 3
Published by March 10th, 2010 in agile, books, case study, domain driven design, everyday tales, layers, object orientation, software architecture, software design and trends. 4 CommentsWe finished last post with this funny situation: the abstraction that represents Facebook depends on our Domain Model.
It was a bit obvious that what we needed was not only system abstractions for Facebook, Twitter and the like but Bounded Contexts. We need to acknowledge the fact that these domains are not part of our model, […]
Everyday Tales: Anatomy of a Refactoring – Part 2
Published by March 10th, 2010 in agile, books, case study, domain driven design, everyday tales, layers, object orientation, software architecture, software design and trends. 1 CommentRead the first post here.
In the previous post we were facing the problem demonstrated by the diagram below.
Our FacebookMessageParser needs an instance of AllSocialNetworks so that it can create valid Users coming from Facebook. The only implementation we have for the AllSocialNetworks interface is UserRepository, and this implementation needs a FacebookMessageParser. That’s a circular dependency, […]
