Geeks With Blogs



Add to Technorati Favorites

An Archived Managed World This blog has moved to

Okay, this is related to Rory's post about “paper bag” coding. I am going to go out on a limb here and predict what future “paper bag” code we will see.

The prediction that is coming to mind right now is that the ability to have partial types will lead some developers to code-maintenance nightmares. While I believe that partial types are a wonderful solution to the code-behind issue with ASP.NET and XAML, I believe that inexperienced developers who do not understand the proper use of partial types will hang themselves, in the process dying 5-times over. Some may say it's not possible dying 5-times over, but as a programmer, I am perfectly aware that is indeed more than possible.

The problem I see is that, for some unknown reason (perhaps to organize their code “better“), a programmer will declare a class partial and write the class in two different files. Well, when someone comes along to read that code, how do they know which file the class functionality they need to alter is in? Or if they need to add new functionality, where do they add it? Maybe a new file with another partial class definition?

I know while most of us won't make this mistake, there will be others that do. As proof of this concept, I reference exhibit A, your honor.

Anyone know of a good doctor that's an expert on self-stress-induced ulcers? Maybe I need a shrink instead? Oh why, oh why, must we developers be sentenced to read others code.

Posted on Tuesday, December 23, 2003 12:07 PM | Back to top

Comments on this post: Partial Coding Prediction

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Jason Olson | Powered by: