Loosely Coupled

I would really like to post more often, but frankly, I've been too busy. The New Year brought a change of job scenery and I've been really busy getting up to speed and learning a ton of new things. That's not to say I haven't been writing at all. As I come up to speed here, I'm taking the opportunity to capture what I learn in a development wiki. My new team has a wiki instance in place, but it's been lightly used to this point. I'm a huge fan of using wikis for development . I like to leverage the wiki as a focal point to capture technical ideas and documentation for the team. Most people seem eager to contribute, so I hope it takes off. One point here, we're using the wiki included with SharePoint . It's not nearly as hard to edit as MediaWiki (the Wikipedia wiki engine), but I still prefer MoinMoin (used by many Apache projects). The heart of the software being built here relies on Ontology , and leveraging the data stored in that ontolog...

I downloaded some of the Air samples and the first thing it wants to do is install the application on my machine. I expected an Air application would be fairly lightweight (like a client-side Java application), and as long as I had the Air runtime on my machine the application would run - no administrative rights required. Not so. And too bad. Installing Eclipse is simply an unzip. There is no need to add entries to the registry or provide administrative rights. It's simple and that's the way it should be. I wonder why Adobe didn't follow this model?

I started this podcast project so I could learn some things I haven't had time to experiment with in my "real" job. Things like playing more with Ruby, trying out Behavior-Driven Development, and experimenting with Agile practices (plus I really wanted a better podcatcher program and I needed something to do over the winter). While I haven't produced much real code yet, I've created some simple prototypes and wanted to comment on some things I've been looking at. Reading an RSS feed My first prototype was a very simple Ruby program to read and parse an RSS feed. I had found some code here using the standard Ruby RSS Parser so that's where I started. At first I thought it was broken, but after about a minute and a half it returned. This wasn't going to cut it, so I started to look for alternatives and quickly found the feed-normalizer gem. Some quick coding and the total time to access the RSS feed was reduced to about 10 seconds. Not bad...

I just listened to an interview with Tim Berners-Lee , inventor of the World Wide Web. While most of the interview focused the Semantec Web , what I found most interesting, were his thoughts on Rich Internet Applications. Of course he thinks this is an exciting development, but with various technologies (Flash, JavaFX, Silverlight) competing in this space, he feels that standardization would help speed its adoption. He points to how standardizing HTML in an open and royalty-free way helped to speed the adoption of the Web. Standardizing this technology would be a great step. Right now, these technologies run as a plugin on the browser. Once standardized, browsers could build this functionality right in, making adoption seamless. Open-sourcing the technology is not enough. The biggest problem with standardization is that it takes so long. It's a good thought, hopefully it will gain some traction. ****** More news on the DB front. The more I delve into the database schema and...

On my last web application project, we realized the JSP/JSF presentation layer we implemented was not cutting it anymore. Transitions between pages were too slow, users wanted more dynamic feedback and drag and drop functionality. The project was put on indefinite hold shortly after that but I wanted to talk about some of the technologies I researched to address these problems. AJAX Ajax seems like the mainstream choice. While AJAX could help address the transition time and feedback issues, I don’t believe it could help add drag and drop. What worries me about AJAX stems from my experience with CSS. Even though CSS is a web standard, some browsers still implement CSS differently. I’ve had to place hacks into my CSS to account for these inconsistencies. It is a pain. Like CSS, web browsers could implement AJAX (XMLHttpRequest) functionality slightly differently. For me, I’d rather stay away from AJAX if at all possible. Adobe Flex I first noticed the power of Flash in ...