http://jamesmckay.net/2007/06/case-sensitivity-is-evil-but-we-still-have-to-live-with-it/ because there are few things that are less logical than business logic Fri, 16 Jul 2010 12:27:57 +0000 hourly 1 http://wordpress.org/?v=3.0 http://jamesmckay.net/2007/06/case-sensitivity-is-evil-but-we-still-have-to-live-with-it/comment-page-1/#comment-1501 Sam McGeown Mon, 02 Jul 2007 10:30:27 +0000 http://www.jamesmckay.net/2007/06/case-sensitivity-is-evil-but-we-still-have-to-live-with-it/#comment-1501 Surely the easiest way to manage the case sensitivity (or not) issue, and any naming issue, is to follow a well thought out convention? Capitalisation or no, there is no excuse for poor naming! Things like using the underscore on private properties are always a good idea, but also making sure that the name of the property is descriptive enough that it's not going to become an issue within it's scope. It's about disciplined programming, producing "good" code is not necessarily the same as "working" code...but I know I'm kind of preaching to the converted here because you use conventions! The hardest part is to produce "good", "working" code within the time restrictions of a business environment. Surely the easiest way to manage the case sensitivity (or not) issue, and any naming issue, is to follow a well thought out convention? Capitalisation or no, there is no excuse for poor naming! Things like using the underscore on private properties are always a good idea, but also making sure that the name of the property is descriptive enough that it’s not going to become an issue within it’s scope. It’s about disciplined programming, producing “good” code is not necessarily the same as “working” code…but I know I’m kind of preaching to the converted here because you use conventions! The hardest part is to produce “good”, “working” code within the time restrictions of a business environment.

]]>