June 2004 Entries
I noticed in a week-old post about Visual Studio 2005 enhancements that one thing being looked at is “rich formatting.” Now, that doesn't really say much, but I'd like to see a customizable code formatter built into the IDE. Personally, I don't like what VS does to my code by default - it's not bad, but I prefer a few minor changes. I'd also like to force things in certain places to keep them logically grouped together. I know that some of this can be handled by FxCop, but as far as I...
I was looking at the MSDN Architecture site a couple weeks ago and noticed several new features (new as in, it wasn't there 6 or so months ago). Check them out whenever you get a chance: Microsoft Architects Journal, update newsletter, and events...
I saw two articles that I thought were going to be pretty promising, but was partially disappointed. I approached the first, Death by UML Fever by Alex Bell, with the attitude that someone would be complaining about UML. I was expecting to hear someone explaining why UML was soooo bad and why nobody should use it. I have to say that I was actually surprised - both good and bad. The article didn't detail why people should stay away from UML. As a matter of fact, the article didn't say much at all....
Now, I haven't investigated this or anything, but I noticed that my comments count jumped in the past few days. I went to check my email to see if I'd received any emial about the replies, and was surprised to see 17 emails from the same “person,” with the same subject. Here's the evidence: 1, 2, 3*, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13...(there were a couple more, but I didn't pay attention to where they were before I caught on). And here's a sample email: Comments from Michael Flanakin's...
As a follow-up to one of my most popular posts, I recently saw a few letters in response to Kathleen Dullard's article, Save the Hobbyist Programmer. There were 3 letters, but only one stuck out in my mind (of course). Thank you, Michael Caldwell. I commend and stand by you and your letter (second letter, continued on second page). Well said...
One of my biggest problems with working in .NET (and especially back in my ASP and VB days), is that most .NET (or respective technology) developers don't approach n-tier development appropriately. The general ideas are sometimes followed, but even in those random cases, they are usually half-ass. Granted, this is just my experience, but I'd feel confident enough to say that this is the case in over 75% of the projects. I was surprised and relieved to see an an article discussing the importance of...