Thanks to @jadkins for the colorful ending to that cliched saying, which really got me thinking. Sometimes we just make certain aspects of architecture too difficult for no reason. Good design is important and can have significant financial impact if done incorrectly, but chances are the negative impact comes into play during the engineering effort,… Read More »
This past weekend I set out explore some of the extension capabilities of Google Wave. One of the weaknesses that have been identified by many is the lack of integration with email. For me, in particular, because Wave is new, many Waves are being orphaned as those playing and testing out Wave don’t come back… Read More »
There’s a lot of points that will be made in this blog entry. To keep them straight, I will highlight them right up front: Vendors are getting behind SCA because it reinforces a need for tools The importance of architects in software development Untested technologies are being pushed on IT like bad drugs from the… Read More »
It seems that I am not as flexible as I believed I could be on my thinking regarding SOA. I attempted to categorize various SOA engagements in my SYS-CON article entitled “A Classification Scheme for Defining SOA” . I believed that I could hide my dissatisfaction with the lack of clarity surrounding SOA by lumping… Read More »
I’m working on a project with a fairly young engineer (let’s just say I have 12 years on him). He’s so enthusiastic about Spring and Hibernate, and so bought into concepts, such as Inversion of Control and declarative programming. It makes me laugh a bit how guys like him act like this stuff is all… Read More »
It’s taken more than 10 years, but I finally got it through my thick skull: A design is only as good as the potential for it to be put it into practice. I tend to come up with extremely elegant, agile and extensible designs. What I’ve learned, however, is that not everyone sees the elegance… Read More »