Heh heh.  I knew it would be a blowout.  Thanks to everybody who commented on the last post.  Thanks for all the traffic, suckers.  Oh, wait, I don't have any ads on my blog.  Damnit...  Anyhow, I'd like to reply to some of the comments in that thread.

ORMs

You have a simple database?  Using an object relational mapping tool is awesome.  I personally love SubSonic and use it in everything I can that involves data access.  ActiveRecord<> FTW!  But the more complex your database becomes, the less benefit you get from using ORM.  With Subsonic, you have to create stored procedures to perform SQL tasks that can't be done via their ActiveRecord pattern (i.e., using SubSonic is too complex or is too slow).  ORMs also usually expect certain quality standards to be upheld in the database.  For instance, if you don't remember to set a primary key on a table, SubSonic won't generate any code for it.  Sometimes you can't control things like this.   

DBAs

You have a DBA or even a team of guys whose sole purpose in life is to create and manage databases?  Then SP's rule!  I'm all about abstracting the data layer behind the walls of SQL Server!  Wouldn't have it any other way!  But most of us have to design, manage, and develop against our own databases or the databases that other non-professional DBAs have created.  And sometimes the people who created the database should have been shot before putting their monstrosities into production. 

I Suck

I appreciate all the people who said I'm a dumbass and don't know what I'm doing.  I love you guys.  You're both wrong and, of course, right.  And the same applies to all of you.  Being a good developer isn't a binary thing; you aren't either a noob or a brilliant developer.  I think being a good developer doesn't mean that you're already at the brilliant end of the spectrum; I think it means that, every once in awhile, you check to make sure you're going in the right direction.