Archives
-
Hi, My Name is Alex, and I am a Resource Waster
Oleg "XML MVP" Tkachenko nailed it. I'm a "resource waster" and proud of it.
-
A Word from the "Wise": Don't Use Exceptions
A while back, I went to a local .NET event which had a number of presentations given on a variety of topics. I attended an intermediate-level talk presented by an out-of-town MVP that was entitled "Advanced .Net Programming," or something like that. One of the sub-topics discussed was error handling, to which our MVP had some rather simple advice: don't throw exceptions. This seemed to be some rather peculiar advice, especially considering how exception handling was such an integral part of the .NET Framework, so I interrupted the speaker to ask for some clarification. He explained a bit further saying essentially that exceptions kill application performance and that you should use return codes because they are faster.
-
CommunityServer: Adding the "Post Date" Sort Order
I've made a handful of modifications to the Community Server software that I use as a back-end to a website of mine (TheDailyWTF.com). Since quite a few people seem to be using this software, I thought I'd share what I've done. If you find this post valuable, let me know in the comments and I'll post more in the future.
-
Author responds to "Worst. Best Practices Book. Ever."
I think I may have been a bit harsh yesterday in my review of Practical Guidelines and Best Practices for Microsoft Visual Basic and Visual C# Developers. Although I stand by my statements, I wanted to expand on and clarify things based on some of the feedback I received (especially one from the author).
-
Worst. Best Practices Book. Ever.
As you may or may not know, I generally critisize things on a daily basis. But this post is much different than my normal (hopefully witty) commentary on bad code. Today I'm pointing out some serious flaws in a book I came acrossed called Practical Guidelines and Best Practices for Microsoft Visual Basic and Visual C# Developers that make the book not only bad (which I can live with) but dangerous for an inexperienced developer. Not only does it fall short of "best practices," but it actually advocates bad practices. In summary, DO NOT BUY THIS BOOK. And if an enlarged & emboldened statement isn't enough, read on ...