Some of us love risk, some are happily prudent. Telerik Technical Evangelist and Microsoft MVP Chris Eargle says he enjoys “testing the boundaries of languages and tools,” but as an experienced Microsoft .NET C# developer, he’s mindful of Murphy’s Law when working on a software development project. In his blog “Lifesaving Tips for Developers,” Eargle shares his personal essential rules for coding survival that can help .NET developers avoid or mitigate worst-case scenarios in their coding projects. Here are some of the eight tips.

“Avoid code that elicits ‘Hey ya’ll, watch this!'” Eargle cautions against using “weird code constructs” in software; deliberate glitches might be fixed later or worse, might introduce a bug that prevents the software from working properly.

“Use version control.” Version control tools have advanced considerably since the “sneakernet” days of sharing source code via .zip files and physical storage media. Today, says Eargle, “there is no excuse not to use version control.”

“Clean up unmanaged resources.” Unmanaged resources in a .NET application can create memory leaks or continually increasing memory usage in the app, says Eargle. To avoid such problems, you should clean up unmanaged resources and, if necessary, use a memory profiler to identify the source of memory hogs in an app.

For the complete set of tips, see Chris Eargle’s blog post.