de tomKronieken

Darren writes about "A few of my favourite things". All stuff I want to know and understand too.

I want to have a look at Castor (especially since I read some stuff on JDO, which looks like I could use it in my day-time job project), OpenJMS (just because JMS seems to stir so much feelings lately), and XDoclet (programming without programming?). The problem with all these (and a lot of other) stuff is that not only you have to know it, but you also have to think in it. It's not just "Oh, let's use that", but more like "I'm going to use that, how would my problem be solved with that tool?", which leads to the hammer-and-nail syndrome. Still, I want to study those things, since I believe they will reduce my dummy-typing and improve my creativity-unleashment (if that's a word).

In the mean time, I'm proud to say that I know and use Ant and CVS. I'm taking baby steps in JUnit, too (which is also more a way of thinking than a tool).

The role of TortoiseCVS and WinMerge is gracefully replaced by Eclipse, so I don't need to worry about them.

Scarab looks useful, but people are afraid of the "oh no, more administration" syndrome when introducing it into our team. As a result, we're coping with several Excel sheets and workbooks now...

As for Jetty: a servlet container is a servlet container in my eyes. I couldn't care less if my project was run on Tomcat, Jetty, or whatever. That's what standards are for.

One final note: SAP gives away a DB now? It even comes with a JDBC driver. I wonder what the business model behind that is ...