Coding too much and sleeping too little is a setting I'm not too unfamiliar with. You know you should sleep a bit more and code a bit less when you have nightmares about debugging and are wondering what method of which class to call to shut off the wakeup alarm in the morning. I'm coding on a project with a few friends these days and came over some interesting code, probably caused by the setting above:
public string MyProp{ set {value = value; }}
Hmm... useful property...
if (valueQueues[queueId].Count != null) return valueQueues[queueId].Dequeue();else return null;
Hmmm.. Nullable types is an interesting thing, but I don't think this is the right setting to use them...
Remember Me
Page rendered at Saturday, February 04, 2012 3:34:50 PM (W. Europe Standard Time, UTC+01:00)
Hans Olav Norheim is a certified database and application developer, working as a developer on the SQL Azure team at Microsoft in Redmond, WA. Hans Olav is passionate about databases, naturally SQL Server in particular. When not in front of his computer, Hans Olav can be seen up in the sky flying a glider, climbing a rock, in a boat or out with friends.
Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.