You having 2 out of 14 is excellent...for me.

@everlast: How about the ability to change the title? That would work as well.

Agree with Aquinas (but I still prefer Calvin :D ). This type of site should be banded completely.

On a related note: When are we going to get a down mod?

Good tool, nice update. I like the extension methods.

http://elegantcode.com/2008/06/29/looking-at-rhino-mocks-35-rc1/

Personally, I agree that Asp.Net developers (myself included) need to wake up...just not for the same reasons.

What I want Asp.Net developers to learn is JavaScript. I can't tell you how many times I've seen perfectly decent developer cower at the thought of writing a bit of JavaScript on the browser. It isn't healthy.
Better yet, learn a JavaScript library like JQuery, Prototype, MooTools, YUI, or even the AJAX Library JavaScript extensions ($get() anyone?).

This is something you can use right NOW, not 2 years from now when technology xyz has hit critical mass to be useful.

Because blogs, DotNetKicks, Digg, MSDN, user groups, and various other outlets just aren't sucking up enough of your free time.

But it is rather amusing to listen to Scott Belware rant in 140 characters or less.

Me three. Digg has a "Bury" option. Can we get that here?

@foobar > I'm sure that'll work out well. I mean, who needs indexes when you've got NHibernate?
No, that is being stupid. There is nothing about ORM that trumps Relational theory. Actually, I think you are talking out of your ass because I doubt you've ever used an ORM. They still create SQL, but in a more programmer friendly way. The reality is that you can write really bad queries in either one -- a good ORM will just help you from creating super bad queries.

And you can take your 1,000,000 entry tables. If your database fits on a laptop hard drive it just isn't that big of a deal to me.

>Relational databases were created by computer scientists. ORMs were originally created by Java developers.
ORMs predate Java, go back to SmallTalk. And if you are thinking those guys are Computer Scientist you are out of your freaking mind.

Here is a different one for you: SQL is the Assembly of programming languages. I've said that one before too.

I'm sorry, most of what this guy is saying is crap.

1. learn about single responsibility
2. GridViews are fine for many applications
3. ObjectDataSource can be used effectively, but you should know when not to use it.
4. Everything this guy says about store procedures is pure and utter crap. I don't think he has even tried doing a performance comparison, and doesn't mention parameterizing ad-hoc queries. That is misleading as all get out.
5. You shouldn't be writing SQL anyway! It is called an ORM. Lookup NHibernate, SubSonic, LLBLGen, LINQ2SQL, and pick the one that works best for you.

Great first step, very informative.. Now we just need a LINQ to SQL and LINQ to XML Best Practices document. :D

OK, lets start with the basics: Source Control is vitally important to software developers. If you are not using it shame on you! Go beat your head into a wall until you feel like complying. Really. Subversion, Source Safe, Team Systems, etc; Pick one and use it.

But I have two very petty complaints with the article:
1. Use of overly tiered title. Any title starting with "I, for one, welcome our new <insert noun here> overlords!" should be banned, and further use should lead to sanctions.
2. There is a freaking CAT in a SINK! Why? Because someone, somewhere, thought cats in odd places were cute -- and we have been paying for it ever since. The only redeeming quality about the cat is that the author did use the generally accepted animal speech: "IM N UR SINK, MAKEN IT DURTY".

The simplest way to setup subversion (that I have found): VisualSVN Server. They get everything up and running (subversion and apache) and give you a nice admin tool to go with it. And it is free.

http://www.visualsvn.com/server/

Of course, Anende wanted security (ssl), and I don't think VisualSVN Server does that...but if you don't need it, this is an excellent option.

Of course, you will still need VisualSVN ($50), TortoiseSVN (free), or Aknh (free) to check in on your desktop.

@powerrush - if it had wouldn't I have said "you have a bad font, therefor you must write bad code".

But seriously: think of the poor kid who reads a statement like that and foolishly things Times New Roman is l33t. He/she could be scarred for years.

Then again, does any kid say l33t anymore? Maybe some scarring would be good.

No self respecting programmer should ever use Times New Roman, Courier, or whatever font is used by default in Visual Studio for programming editor. That is a clear sign of not taking thing seriously (you have a bad font, therefor you must write bad code)

If you can't immediately tell the difference between 0 (zero) and O (capitol o), 1 (one) and l (lower l), as well as having clear differentiation between { [ ( and the rest of the special characters at low font size (I don't use a font size bigger than 9), throw the font away. Also, fixed width fonts ONLY!!! You are a programmer reading code for freak sake! Save the other fonts for your blogs.

See here for more detail on programmer fonts:
http://www.codinghorror.com/blog/archives/000969.html
http://www.lowing.org/fonts/

Hmmm, Rob is looking for the adulation of Jeff Atwood.
I'm looking for the adulation of Rob.
I guess Jeff is my god now.

Glad you understand that now. BTW: a real hacker would do with the MVC framework to prove worthiness. :D