I’ve come up with this list of ways that programmers tend to deal with problems of code duplication.
1) Run with it - hire 1-50 more people so to write and maintain more of the same code. This seems to be a common practice in large corporations. The problem with this solution is that […]
The problem here is that most business applications don’t actually have a lot of “business logic” in them. Other than basic validation of user input, mainly what we do with objects is Create, Read, Update, and Delete them. There simply isn’t always a need to have a lot of fancy domain logic associated with your […]
I’ve been reading a lot of blogs lately by object-oriented people who complain about the increasing separation of code and data in the domain layer. They claim that in good object-oriented programming the behavior and the data are supposed to go together. While this is true in principle, it doesn’t necessarily mean that […]
I’ve had a minor obsession going with aop lately. Maybe it’s that I think there’s something valuable there but can’t quite pinpoint it, or maybe that its that it’s getting way more attention than it deserves. But as I read articles, blogs, introductions, papers, etc… I’ve noticed one consistent thing that always […]
Today I was reading Martin Fowler’s article Who needs an architect? which I thought was excellent. The most interesting comment being this one, which he apparently culled from the talk of an economist named Enrico Zanninoto:
One aspect I found particularly
interesting was his comment that irreversibility
was one of the prime drivers
of complexity. He saw agile […]
I’ve trying to document some solutions that I have come up with, and I am having a really hard time. I’ve been trying to follow the classic design pattern format: context-problem-solution. The problem is that i can’t express any of those things very concisly. At first I tried to break it out […]