Author Archives: JohnHowell

Welcome to the new ".Net Code Space" blog formerly of http:\jmarkhowell.blogspot.com.  I’ll do my best to catch up on all the wild things that have been going on in the .Net and Windows world as well as continue with the … Continue reading →

Unit tests can be a touchy subject for some developers.  For some, they dispise doing them at all, while others go completely overboard with them.  I’m in the middle.  I don’t believe that they’re a cure-all for bad code, but … Continue reading →

 I was around when Java first came out and lived through the sometimes nightmarish stability problems in the early releases.  Java was out before .Net was even alphaware and it brought a great deal to the table.  But something went wrong or … Continue reading →

As most of you have seen, I’ve been OOF from blogging lately.  The deal is that the transition from AL to WA and everything that it has entailed has been, shall we way, overwhelming.  I’ll share some of the tribulations … Continue reading →

OK, I’ll admit, I might be the only one to get excited over this, but: Orcas for Vista RC1 Available

Recently, Borland announced that it was getting out of the Software Development Tools market and was going to concentrate on Software Delivery Optimization (SDO) and Application Lifecycle Management (ALM). Last month, they ‘restructured to more closely align to this new … Continue reading →

Sorry to have the blog so quiet lately, but I’ve flown over 7,000 miles, moved over half a ton from attic, basement and shed and shredded an unimaginable amount paper over the past few weeks. I’m preparing for relocation. Strangely … Continue reading →

I’m a blue badge! I’m official! This is a little overwhelming and I think I’m not quite sure what to think or how to feel. For the past two weeks I’ve been immersed in impatience waiting for when I could … Continue reading →

While working with a couple of source control software packages over the last few months, I have been frustrated by what I saw as a lack of usability with the UIs. What I thought should have been intuitive took too … Continue reading →