A little while ago, I was running an audit on a server that is usually pretty hands-off for me. It’s been pretty stable, so I’ve had no reason to pay it much attention. When running the job audit, I saw the following, and it reminded me I need to tighten up my enforcement of naming conventions. :-)
Those columns are [IsEnabled], [ScheduleName] and [Frequency]. Wanna guess which ones were jobs I created? Yep, the ones that don’t use words. :-) My shorthand for those two job schedules breaks down like this: D = daily, R = recurring, then the interval. So those two jobs run Daily, Recurring, every N hours.
Other schedules I have on that machine are:
- Wk_Su_0900 – Weekly, Sundays at 9 AM.
- Wk_M-F_0800 – Weekly, Monday through Friday at 8 AM.
- D_1600_Ex_Su – Daily at 4:00 PM, except on Sunday.
This is what I like to refer to as a ‘self documenting’ name. The name describes the object. It’s what I shoot for when developing a naming convention for development standards. This way, even without a verbose description, I can look at the object name, and have a pretty good idea of both what it is, and what it does.
What types of naming conventions do you use?
Thanks for reading.