Easy to say but hard to do

One of the blogs on my google reader is Coding Horror. I often find this guy amusing and interesting, both in a postive mannor.

Today he was off on an interesting rant, Does Writing Code Matter? and I have a few thoughts on the subject. First and foremost it does! A codeslinger enjoys his ways and has not only a swagger but a look in their eyes. So, again, first and formost, it matters.

However, Jeff went on to make a very good point, one we all already know in the back of our heads. He says “Become a better writer. Become a better speaker. Improve your personal skills. Participate in the community. … That’s how you distinguish yourself from your peers. And that’s ultimately how you become a better software developer, too.”. While I completley agree with this statement it is not that easy. The vast majority of developers are poor at this skill set and either don’t want or can not obtain it. So while it is a lovely idea, it isn’t practical and has nothing to do with writing code.

If I can do it shouldn’t the Database be able to?

Back at the ZIPR I used to get teased about things like BJava (Ben’s Java) and BOracle (Ben’s Oracle) since I would often find annoying and limiting aspects of a Technology and then I would go on and on about what a POS they were.

Now I work a lot with MS SQL Server, which I enjoy working with much more than my old friend Oracle. So this is no way a reflection on one POS Database or another POS Database.

Anyway, if I can tune a query, shouldn’t the Database be able to do it for me? Why is the optimizer more often then not wrong? Why do I need to use join hints and join types? Why will it even allow me to add a redundant index? I’d really like to see some improvements in these areas. I feel so limited in what we can do with DSQL with a POS optimizer. Imagine a world where you write a query and the Database figures out how to make it run fast. I don’t care if it re-writes the query for me. Why should I have to worry about join order and indexing? Can’t the database figure out I need an index and what columns should participate in that index? Java has done a fairly good job with their Hot Spot Technology.

It is time for the Databases to shape up since there is no way they are going to slim down in todays world of unsurpassed data.

Fantasy Football (pickem)

Doesn’t FF just make a leisurley day of football more enjoyable? There is something to be said about rooting for not only teams but individual players. It is sad however that the black out rules often pre-empt the best games on TV. I was not able to see the Dallas vs. Philadelphia game today due to the Niner vs. Raider game with the same time slot and that game was hardly worth watching. I am doing quite well in all of my leagues! I have an algorithm that I follow for Yahoo Pickem.

1. Always pick a team coming off of a bye week.
2. Never pick against New England.
3. Never pick Arizona, they are the new Cincinatti. No matter how much you are tempted
4. Make your picks after the Sunday Night Game while everything is fresh on your mind. This saves you a lot of time during the week thinking about it.
5. Don’t adjust your picks during the week unless a significant injury occures to a key starter.
6. Never join more than one pickem league, this can lead to your down fall if one of your leagues is doing poorly.
7. Always go with your gut!

I’ll be riding to a first place win this year if I can follow my own algorithm.