Basic, but good information that I wish everyone knew.

The content is great. I wish there were another theme available though. Tiny white text on black feels like a million tiny daggers stabbing the back of my corneas.

I just replaced UltraMon with this.

A little over a thousand views so far, and no one's figured out the question at the end!

I didn't know that. Good information.

Microsoft Bob would've been a hit, if only it had come in the Cute Librarian edition.

What I wouldn't give for everyone to get in this mindset.

As someone who inherited an application that stores half its dates as datetime and half as identically formatted varchars, I think this should be required reading for anyone who wants to design a database schema.

Maybe old, but also good.

After seeing a 200k LoC project we outsourced last year come back with 0 comments, I have to agree that it's better to be safe than sorry and require a certain level of commenting. In the end, that project literally got scraped, because even the people who wrote it were unable to maintain it a year later.

That deserves a kick, just for the title!

jQuery is great. And, works along side ASP.NET AJAX without conflict.

Good information that everyone should be aware of.

No offense, but you're missing the point.

The majority of ASP.NET applications that you'll find online have relatively massive viewstates (though, I've noticed that dotnetkicks has a very lean viewstate. way to go, guys). Even if you can compress all of the response HTML to negligible sizes using gzip, the viewstate round-trip alone is usually significant enough to try to avoid when not necessary.

You're also ignoring the performance cost of reinstantiating all of the controls and running them through their life-cycle in order to render the UpdatePanel's HTML.

Compounded across a respectably sized user base, the savings are absolutely worthwhile. Especially given how easy web methods are to implement.

The ViewState is already compressed. You won't achieve anywhere near that kind of result compressing the ViewState. I'd be surprised if you compressed it even an additional 10%, best case.

I'd assume /kick on a URL that isn't in the database yet will automatically go to /submit. So, using /kick is more robust when you may have people hitting the bookmark on pages already in the database without knowing it.