A while back, I referred to Eugene Meidinger‘s SQL Saturday presentation about keeping up with technology. I came across his ‘blog article where he talks about exactly that. It’s a very good read, and he gives an excellent presentation.
Eugene will be giving this presentation in Rochester on March 24, which happens to be the same SQL Saturday where I’ll be speaking! </plug>
Hope to see people there!
I had two appointments this past week. The first was one for my car to get my oil change and to make sure everything was in good working order (it was). A couple of days later, I had a dentist appointment. It was a routine cleaning (I also had a procedure done — one that I’d been putting off for a while). While the two appointments were for different reasons, they both served the same purpose: to perform maintenance.
Just about everything, especially anything mechanical, is going to break down over time. Maintenance ensures that things remain in good working order. But when we think about maintenance, we usually think about car repair, roadwork, furnaces, and water heaters.
I’m sure many people in tech industries consider periodic hardware and software maintenance. Hardware can break down. Drives crash occasionally. CPUs are upgraded to keep pace with emerging technology and to support software. Speaking of software, bug fixes are constantly made. There’s also the matter of security; virus software definitions are constantly updated, and operating system patches are distributed to ensure computers are safe.
But here’s another question: when was the last time you maintained your documentation? Does your documentation, which was written for, say, Version 1.0, reflect what is in Version 2.0?
The trouble with documentation, even the best-written documentation, is that it can become obsolete over time. Processes and systems change. Interfaces are redesigned. Steps become more efficient, or in some cases, even eliminated. Change happens. It’s one of the sure things in life. Documentation should also change as well. How often has your help desk received calls from frustrated customers saying things like, “your instructions say ‘press the red button,’ but there’s no red button on the interface!”
If your product changes — and it inevitably will — your instructions should change with it. It’s important that systems are maintained. Your documentation should be maintained as well.
My next SQL Saturday is scheduled! I will be speaking at Rochester, NY on March 24!
I’ll be giving the following two presentations:
Hope to see you there!
About a week ago, I received an email from Carlos Chacon of SQL Data Partners inviting me to take part in a podcast. This was my first such request, and I jumped on the opportunity.
The podcast recording took place last night. My topic was along the lines of “writing and communication: why it matters to data professionals.” It was a lot of fun, and I very much enjoyed talking to Carlos and his partner, Steve.
The podcast should air sometime in March. It will be posted on their ‘blog. When it does, I’ll make sure that I post a link to it!
I cam across this article on Grammarly, and I thought it spoke volumes — enough that I’m sharing it in this ‘blog article. Read and enjoy!