When I started working as a web developer, PHP was the first language I learned that was 100% web oriented.
Back then I believe it was PHP3 or something like that. At the time, PHP was pretty new to the web, PERL was the main denominator.
PHP today is hated and loved, and I’m not going into that path here, I’m very programming language agnostic. My mantra is “use what’s best for the job”. However, back then PHP was getting lot of traction, mostly because it was very easy to work with and to setup/deploy. Nothing, even today, beats the LAMP stack.
If your read my previous post about Clean Code, this will fit right along.
This post is about choosing the right and correctly variables/classes or functions names for your code.
Picking up a good name convention in some cases eliminates the need for comments, because your code will explain what’s going on.
It shouldn’t be a secret, in fact I don’t want it to be a secret.
This so called “art” can define the future of your application, the sanity of your team, or worse, the future of your company.
Am I exaggerating ?
Not really. If you are a programmer with a few years of experience you’ve probably already seen this countless times, hell, you’ve probably done this already which is the so called messy, undocumented, untested and hard to read code.