Contents tagged with OO
-
Curing Singletonitis
A few years ago I have blogged about Singletonitis. Another place, different people, yet the same problem appears again – singletonitis. The issues I have outlined back then where
-
NoSQL is Gaining Weight
Looks like more people are looking into OODB. This post I found recently is experimenting with db4o, as well as has a healthy discussion in the comments section. This is ties into what I felt and thought a while ago after reading a book on db4o.
-
UML and Sequence Diagrams Online Generators
I am a fan of quick tools that help you sketch out thoughts. These two do exact that type of work.
-
Too Loosely Coupled Code – One Year Later
More than a year ago, I have posted a blog entry related to what I was trying to implement in one of the projects. Unfortunately, not my team could understand what I was trying to do, neither I was able to make myself clear. Either way, I ended up closing the blog with a question “can code be too loosely (coupled), or your code is so coupled, that anything else is difficult to digest?”. Now I can answer my own question question.
-
Convention over Configuration
Convention over is defined in Wikipedia as follow:
-
State Pattern with FluentNHibernate
FluentNHibernate is an amazingly nice DSL to use for quick NHibernate mapping implementation. Today I had to refactor some of the code we did at work, in order to persist a state of an object. The original code was implemented using State pattern, which allows simple division of responsibility and easy decision making at each given step. I have decided to create a simple example of State pattern persisted with FluentNHibernate in order to demonstrate how powerful it is and what kind of freedom it can give to developers.
-
Sick of Relational Databases
I have started to read a new book about OODB. The reason I decided to get the book and go through it is because I am SICK of the traditional RDBMS and the way it forces us to go through loops and hoops to create domain driven applications.
-
Test Helpers and Fluent Interfaces
Today was a great day. One of the things we do with the team is experiment how we write our test. Experimenting seems the most effective way of figuring out what should be our testing approach. At this point we are mostly doing specification driven tests (unit tests).
-
Depend Upon Abstractions - reiteration.
I was reading through the book when combined several subjects together, such as "help tests" and "error handling", and realized that the core "Depend upon abstraction. Do not depend upon concretions." principle is underused by myself.
-
Singletonitis
While reading Joshua Kerievsky book "Refactoring to Patterns" could not go silent about abuse of Singleton pattern he described. The question that was asked in the book "When is a Singleton unnecessary?" - "Most of the time". Honestly, I can recall at least a few times when I was sick with Singletonitis: different Utilities, Session related classes, Context related classes, Resources related classes, you name it.