Geeks With Blogs
Lessons Learned Preserved for Posterity Lessons Learned I've learned a lesson, and have preserved it for posterity.
Don't Use NOLOCK, Use HOLDLOCK
Normally I very much agree with the things Jeff Atwood has to say. In the case of this post, however, I must take issue. What begins with a decent intro into the concept of deadlocks eventually ends with Jeff deciding to use the NOLOCK table hint to allow dirty reads of a table that had been locked by an update statement. He concludes with a complaint that Microsoft seems to think that Stack Overflow is a banking institution and therefore worthy of data integrity instead of the mere programmers blog/wiki/link ......

Posted On Thursday, August 28, 2008 9:36 AM

Hidden Surprises in .NET 3.5 Service Pack 1
Ok, imagine the following situation: You are a developer and you want to keep up with the latest technology, so you update Visual Studio 2008 with Service Pack 1, installing .NET 3.5 Service Pack 1 as part of the update. You then proceed to continue with your ASP.NET application, building a nice neat AJAXy application. Everything works fine on your box, it's awesome, the in-your-cube demos go great, everybody's happy. So you build and deploy your new hotness then sit back and wait for the pats on ......

Posted On Thursday, August 21, 2008 10:15 AM

Whose Fault Are Poor Requirements?
I had thought I would do my first Lesson Learned about my control for the upcoming Silverlight Contest, but recent events changed my mind. A phrase has been bandied about alot at work lately, a phrase we've all heard and uttered in one form or another at least once in our software careers. It exists in numerous variations, but essentially boils down to this: "The software is bad because the requirements were bad." I've seen it happen far too often: somebody complains that "<x> is broken" and ......

Posted On Monday, July 28, 2008 10:33 PM

Copyright © Randolpho St. John | Powered by: GeeksWithBlogs.net