I am a huge fan of O/R mappers like Hibernate and JDO. They insulate developers from the database mechanics, speeding up development and boosting productivity. They also add a layer of insulation above the database itself, which aids portability. However, insulating developers from the database layer completely is not always a good thing. Developers still need to be aware of the performance impact of the code they are writing at that moment
New "pragmatic" Java book, leveraging open source.
A Slashdot discussion exposes some of Java's bad rep.
According to its developers, a milestone release of the Apache Geronimo server is tagged in CVS and awaiting binary release by the ASF. But don't get too excited about it just yet--the release is for earlybirds and hackers.
The J2EE reference implementation (RI) doesnt get any respect.
Microsofts ability to market itself in technical papers is nothing less than amazing.
Many features of the J2EE specification are reviled by ardent Java supporters... What is the magic that keeps Java developer's loyal?
When working with Picocontainer and Inversion of Control type 3 (IoC-3) component techniques inside of Shocks, I ran across an odd problem with Java Strings.
My brain has been slowly digesting the concept of code rot, triggered by skimming random articles or blogs that have recently mentioned the term. Code Rot. It's a good word. We've all experienced it. But it's another thing to understand it. What is code rot??
Test-Driven Development is Example-Driven Development, and if you're not careful, TDD can be like teaching to test.
Like many people, I want a way to run some one-time set up and tear down logic and the approach I usually take is to drop some code into a static initializer block in an abstract test case.
No process (I would trust) is going to promise you a 42% productivity increase. In Sabre's case, most of this increase was due to the people who took the four values of Extreme Programming to heart.
People should think of open source code portability
on two levels; system/library calls and graphical calls.
Another week, another games ramble.
The history of computer games can be viewed a myriad of different ways. For me, the big historical events have been the growth of new genres.
Well I've been playing for about a week in the City of Heroes beta. I'm not wrong often, but when I am I do my best to own it. I've described this in the past as The Greatest Game That Will Never Ship. I was wrong. Its simple, but done, and will be going live on the 28th.
Web Services and XML
Tim Bray sorts out the best practices from the best guesses among the web services "standards" and concludes with a plea for WS-Simplicity: "building applications with whats here today and what works today: XML, HTTP, URIs, SOAP, WSDL, and thats about it."
You've probably heard of the latest scripting language for the JRE...Groovy. My first reaction is similar to my reaction to all those "Blah, blah for Dummies" books.
Has Sun been paying too little attention to Microsoft. Or too much?
How long will corporate America put up with the high prices and low quality of the software industry? A handful of major corporations have decided "enough is enough" and have banded together to form their own "software co-op". What impact will this have on our industry?
Satya Kolachina talks about why he wrote Linux Application Development for the Enterprise and what he hopes the book accomplishes.