I am doing this talk at Visual Studio Connections on an inspiration from my painful experiences of diving into C# on occasion. There are a bunch of things that bite me over and over since I don’t use C# consistently enough. I also remember spending about 1/2  hour trying to figure out how to say “OR” in C#. Lots of syntax things like how to construct IF may not seem hard, but if you have been doing it a different way for 5 or 6 years, it really is hard to sort out brackets here, parens there, brackets sometime, not others. And all of the problems that cause compile time errors that are not picked up by intellisense are huge pain points as well, especially when the compile time error message isn’t really telling you what the problem is. Sure there are extensive books on the differences, but I am just going to try to point out the things that a VB6 dev probably uses the most frequently and the most naturally, and try to ease some of the pain of the transition. This isn’t so much for the purpose of converting VB developers to C#, but being sure that folks are at least somewhat fluent in C# even if they go the route of VB when they make the move to .NET. This talk will actually be pretty much the same as if I were doing it VB.NET vs. C# as well.

http://www.AcehAid.org

Why being stubborn is good when you are a programmer

I agree. Though actually I have always said I am stubborn and lazy. Stubborn is the “I will NOT let the computer win” part, and lazy is the part the makes me not want to write the same code over and over again. We all know that it takes more time to write reusable code than to just whip out some code to solve a particular problem. But it’s worth it to make it reusable so you don’t have to do it again. Or to write code that will automate more processes. Etc. Lazy, I say.

http://www.AcehAid.org