Naming Objects In Your Database 7

[damber]

crikey, with all the time spent typing in this thread, you could develop several databases with all the prefixes you cared to throw at it and still have time to take an extended holiday....

So far, there are about 56,000 typed characters in this thread - ~42,000 (~8,000 words) of which are ESquared's.... ...to explain how one should name things.

Maybe I could paraphrase slightly for those with limited time:
[ol]
[li]keep it consistent[/li]
[li]keep if brief, to the point, but appropriately descriptive[/li]
[li]keep things clearly identifiable where differentiation is needed[/li]
[/ol]

This applies to formatting as well as naming.

Not wanting to diminish the importance of clarity in code, but please don't forget the reason you're building the application in the first place...



A smile is worth a thousand kind words. So smile, it's easy!

 

[ESquared]

please don't forget the reason you're building the application in the first place

That's a good point. And one's effectiveness at maintaining that application in the long run--something influenced by naming--is probably more important than getting the initial features right.

Thanks for the summary. I obviously have no problem typing, now do I?

[COLOR=black #d0d0d0]My alarm clock causes time travel. When I hit snooze, no apparent time passes before the alarm sounds again, but the universe has in fact moved forward through time by ten minutes![/color]

 

[ESquared]

Okay, so I've started a blog. Don't expect much. We'll see.

[COLOR=black #d0d0d0]My alarm clock causes time travel. When I hit snooze, no apparent time passes before the alarm sounds again, but the universe has in fact moved forward through time by ten minutes![/color]

 

[r937]

congrats, erik, for starting it

i hope you will find as much satisfaction writing it as we will reading it

looking forward to your next entry

r937.com | rudy.ca