Hi, I’m Leslie Koorhan, and I’m doing the .NET blog. This is very exciting for me
as we are transitioning (as I’m sure many of you are) into the latest development products
from Microsoft, Visual Studio 2008 and the .NET Framework 3.5. So I have a
bunch of things to talk about, with all that new technology, but also some great
things that I like about Visual Studio 2005 and the .NET Frameworks 2.0/3.0
But, let me talk a little about myself as an introduction: I have been in the computer
business for too many years to admit, started with PCs back in 1982, using dBase
II on a CPM platform machine. I developed and taught FoxPro and Visual FoxPro for
8 years, spanning at least 6 versions in that time span. I have been working with,
and teaching, Microsoft SQL Server for the past 13 years, spanning now 5 versions
of that product. I learned VB6 and then have been involved with .NET since it was
in beta, back in 2001. I “converse” in both Visual Basic and Visual C# with no particular
preference. (There’s something to like about both.) And I have been a Microsoft
Certified Trainer for over 12 years. In the future, I will be talking about the
new certification paths for Visual Studio 2008, some of the new .NET technologies,
some of the old ones as well.
If you have anything to say, feel free, and let me know any questions you might
have about developer products. For certification information now, try
http://blogs.msdn.com/gerryo. And as always, for learning, use my favorite
site: www.microsoft.com/learning
Problems in Software
Tags:
Lately, I have been reading a book called
"Dreaming in Code", by Scott Rosenberg. It is about a coding project for a product devised by Mitch Kapor (formerly of Lotus fame) called Chandler. But there are three chapters in the book that I think every developer or IT manager should read: Chapter 0 - Software Time, Chapter 9 - Methods, and Chapter 10 - Engineers and Artists. Some of this material covers the very act of programming, the problems with management, and the idea of whether our base programming model is flawed. All in all, the material should be required reading for every programmer whether experienced or new to the business.