- Bought a vanity domain earlier this week from @dnsimple and now my phone is blowing up with solicitors, scammers, a… twitter.com/i/web/status/9… 12 hours ago
- Big news. twitter.com/auth0/status/9… 13 hours ago
- It seems that all technical advice boils down to "Stop, Think, Execute, Verify." Skip any one item on the list and… twitter.com/i/web/status/9… 1 day ago
- Hey, @shanselman I recently interviewed on @2ndCareerDevs and think it turned out really well. Would love to be a g… twitter.com/i/web/status/9… 1 day ago
- Hey, @ShawnWildermuth I recently interviewed on @2ndCareerDevs and think it turned out really well. Would love to b… twitter.com/i/web/status/9… 1 day ago
SSDNUG Presents: Eric Lee on Anti-Patterns in Legacy Code November 12th
October 16, 2009Posted by on
The South Sound .NET Users Group is pleased to present Microsoft’s Eric Lee on the evening of November 12th from 7:00 PM – 9:00PM at Olympia Center in downtown Olympia. This presentation promises to be an enlightening evening with not only an outstanding member of the .NET community offering sage advice, but also honest upfront discussion from a developer with over 15 years of experience working in the belly of Microsoft’s most successful divisions.
About Eric’s presentation “Common Anti-Patterns in Legacy Code”:
One of the most dreaded phrases in software engineering are the words “legacy code”. You know what that means: old, nasty code that gives you ulcers and makes you tear our your hair. In this presentation we’ll swap horror stories, discuss ways to make legacy code a little more manageable, and learn some principles that will help you avoid writing legacy code of your own.
About Eric Lee:
I’ve worked for Microsoft for over fifteen years as a developer of testing tools and other applications in the Office division and in Microsoft Game Studios. I’ve inherited multiple legacy systems during my career and have had to suffer through the resulting pain. I’m sad to say I’ve probably also written a legacy system or two. As a result I have some opinions about the sorts of things that makes code either maintainable or a legacy nightmare.
View Larger Map