Kinda funny that the day after I sign up with FeedBurner, Mike Gunderloy posts a rant against FeedBurner saying

Nine times out of ten when I try to subscribe to a new feed using FeedBurner these days, I get: "Error when subscribing to feed for http://feeds.feedburner.com/XXXXX/: Timeout when downloading feed". I've reached the point where I largely don't even bother trying to subscribe if you go through FeedBurner.

Interesting... let me know if you have problems, and I'll ditch 'em.

I finally signed up at feed burner.  If you're subscribed to this blog, please take a few seconds to un-subscribe from the old URL and use the new one on the right-hand side of my blog (http://feeds.feedburner.com/ColinNeller)

Thanks!

I like studying other people’s code… when they know what they’re doing!  I’ve noticed that this is particularly helpful when I’m new to a technology.  The problem is that the code you’re studying may not be as good as you think it is.

Case in point: I was recently reading over anther programmer’s stored procedure.  At the end, I saw the line “select SCOPE_IDENTITY()”  Eh?  SCOPE_IDENTITY?  What is this?  Every example I’ve seen would have said “select @@identity”… come to find out, 99% of the time, this is the wrong way to do it.

Jeff Attwood recently posted on studying other people’s code:

You won't become a better programmer by passively studying other people's code. Similarly, you don't magically become a better writer by reading a lot of books. You become a better writer by.. wait for it.. writing.

I agree: unless you go through the motions of leveraging a technology yourself, you won’t completely understand it.  Until you actually do it, you don’t yet know what you don’t understand.  I also agree with Jeff’s next statement: “Studying code is reasonable advice. It's helpful.”

Absolutely!  After having done it yourself, it’s much easier to pick out the things that the other author did differently.  Finding these differences makes you find out ask which way is better.  This process enhances your ability to make choices in a given scenario.  It also makes you aware of in future code you write or review.

A quick search on Google ("http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=deskbar&q=@@identity+vs+SCOPE_IDENTITY")  revealed that this issue is not a new topic – but I wouldn’t known anything about it if I hadn’t taken some time to read through someone else’s code.

The only way I can find to change the template for the "New Stored Procedure..." command in SQL Server Management Studio is by digging around in the file system:

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\sqlworkbenchprojectitems\Sql\Stored Procedure\Create Stored Procedure (New Menu).sql

This short and easy to remember path seems to be the file that matches the command.  If you find a better way, please let me know!

I have to admit, I’m a little confused.  Joel Spolsky – well-known in the software development blogger community – wrote a post in June of 2004 commenting on Microsoft’s dedication to backwards compatibility.  He cites the following story as an example of this dedication:

I first heard about this from one of the developers of the hit game SimCity, who told me that there was a critical bug in his application: it used memory right after freeing it, a major no-no that happened to work OK on DOS but would not work under Windows where memory that is freed is likely to be snatched up by another running application right away. The testers on the Windows team were going through various popular applications, testing them to make sure they worked OK, but SimCity kept crashing. They reported this to the Windows developers, who disassembled SimCity, stepped through it in a debugger, found the bug, and added special code that checked if SimCity was running, and if it did, ran the memory allocator in a special mode in which you could still use memory after freeing it.

Spolsky goes on to say that in the “Raymond Chen days” this was not unusual for Microsoft.  A quick search of Raymond Chen’s blog for the word “compatibility” confirms this – 66 posts containing the word at least once.  To really get a feel for the importance that Microsoft placed on supporting current customers, you need to read a few of these posts by Chen.
 
In Spolsky’s article, he praises Microsoft for their previous dedication to backwards compatibility, and then laments what he sees as Microsoft’s trend away from backwards compatibility…

Enter March 2006 – Vista is behind schedule.  The New York Times publishes the article “Windows Is So Slow, but Why?”  Their analysis?  Microsoft puts too much emphasis on backwards compatibility and not enough on new innovation. 

Eh?  So who’s right?  Spolsky or The New York Times?

The fact of the matter is that Microsoft is the market leader.  They have a “slight” majority of the market share, and with that majority they feel the need to help their customers make the jump to the next version.  They know – rightly so – that companies don’t have time to sit around and re-write applications that already work fine.  If companies won’t spend time to re-write, then the customers who require those applications can’t upgrade to the latest and greatest (Vista.)  If no one upgrades, Microsoft doesn’t get paid.  And being a business (a fairly successful one at that), Microsoft feels the need to insure some return on their investment – pretty simple.  In addition, they’re not going to start loosing customers any time soon.  The same companies that won’t do a slight re-write for the next version of Windows, surely not going to do a complete re-write to run their apps on a Unix, Linux, or Mac box.

Would it be nice to have Vista before Christmas?  Sure - I’m sure Dell would love it even more - but no one would buy the product when they realized that the applications they want to run no longer work.