Coworker's New Blog and O/R Mappers
Posted on Friday, October 24th, 2003 4:03 PM
Chris just posted his third post which is about Java O/R Mappings and I figured I'd give him a little link love as incentive to keep it up. A quote:
Heh. That would be *me* ranting about the complexity and OR mappers above and happily I seem to be in with good company here (the boss). LONG LIVE SQL! Like I've said before on this weblog, for every layer between you and your data you better have a *damn good reason* for it to be there. Otherwise it just leads to useless complexity and bugs.I was telling a coworker about my current database persistence engine, Solarmetric's Kodo JDO implementation, and received just a bit of a suspicious look. The suspicion quickly turned to astonishment when I told him the reason I use an O-R mapper in the first place, which is speedy development. I think I may have used the word 'agile' in a moment of weakness, though I know it's bad form to drop buzzwords like that in a friendly discussion.
Anyway, he correctly pointed out that JDO adds yet an extra layer (and a pretty thick one at that), slowing down the build and adding more complexity.
...
One thing about using O-R mapping tools: Developers who can't easily compile and run Java programs don't much like the idea that the database should be controlled through objects rather than directly with SQL. I can't really blame them, but the impatience around the office has been building lately. My boss, the Skipper, spotted the O'Reilly Java Data Objects book on my desk, pointed at it, and exclaimed: "The Devil!"
Go leave him a comment on his weblog and tell him how much you agree/disagree. You know, I've been evangelizing weblogging quite a bit since I arrived. I need to write up a short "Russell's Guide to Weblogging" or something...
-Russ