When I saw the press release on the get Google Social Scene API I thought it sounded mildly interesting but not really compelling. Then I read this from a link on [url]http://www.simplebits.com[/url]: [url]http://bokardo.com/archives/why-im-excited-about-the-google-social-graph-api/[/url]. One of the annoying things about facebook, Myspace, linked-in, gmail, etc. is that all the contact/friend info is separate in each one other then facebook importing email contacts and the like.
Andy Brummer's blog
These are the TFS rules that Microsoft turns on for their development.
Microsoft has released a pre-activated VPN image of windows xp with IE6 installed so you can test for IE6 compatibility with IE 7 installed on the same machine.
I came accross this article, which goes into one of the major software design misconceptions out there. I've heard this echoed many times: XML doesn't have to be compact, the network will get faster; Java doesn't have to be fast computers will get faster, etc.
I've also seen many systems bogged down with fundamental designs enforcing poor performance. Most of the time the problem is designers that don't understand the impact of shared resources on a web server. They worry about CPU cycles on individual requests when they use a property heavy remote object, or abuse a database with multiple small requests in a transaction.
One of my major frustrations with web development has been the lack of good testing tools for the user interface. Back at Dell I worked on one tool which we developed using the .net httpRequest objects and some scripts to check the html and step through some pages, but writing tests was entirely too tedious and broke often. Plus it didn't handle client side well.
I've been using Framework Design Guidelines for a couple of months now, and reading Brad Abrams blog for longer. It's a great book BTW. Not only does it go beyond the usual naming convention standards, it let's you know what to expect from the .net framework and how to write code that works well with it.
One of the suggestions and also one of my pet peeves has to do with returning collections. You should always return a collection even if it is empty and never return null. Null doesn't add any information to the caller and just forces them to write extra code which has no real meaning other then handling an edge case.
There have been a few posts about the new ATLAS framework for ASP.net and all the usability enhancements it enables on the front end. I think LINQ/DLINQ is just as cool for the back end.
It's a functional style syntax for doing queries over objects, xml and databases in C# code. It allows you to take a loop over a collection of objects with the nested if statement as a filter and replace it with a more SQL type syntax where you just loop over a filtered result.
Rico Mariani posted a follow up entry to The Performance War -- Win it 5% at a time.
The Performance War: Using counts to help navigate flat performance reports it's about the approach he uses when he has cleared all the big items out of the system and is working in the hard endurance phase of performance tuning.
Microsoft released the code for the built-in ASP.NET 2.0 Membership, Role Management, Site Navigation, Session State, Profile, Web Events, and Web Part Personalization providers (basically all of the built-in providers that ship in the .NET 2.0 Framework Redist).
This is a simple console application which moves all opportunites to a specific stage.