Some time back I wrote in this blog about how I just hadn’t made the time to implement the voice-recognition software which I purchased a number of months ago. (Dragon Naturally Speaking). With the meltdown of my primary workstation a couple of weeks ago, it was necessary for me to replace my main workstation. This has been a huge project, resulting also in a domino effect with my internal development network. Thankfully now my changes have all been implemented.
However, now that most of the issues involved with replacing my main work station have been resolved, I decided to spend some time this evening to install, train, and actually use my new software. I must say that this has been a great experience. (P. S. I’m not getting paid by Dragon). I now have it working on my main workstation where I intend to use it daily. Who knows, it may even provide me with a tool to be able to blog more frequently!
So what does any of this have to do with software development? One might also ask, what does that have to do with what has been my recent topic — that of application value? What I’m seeing at this point, is that in a very short time this application has proven value to me. I expect that the more I work with this software, the more valuable it will become to my day-to-day operations.
Training, taking the time for training, experimenting, hands-on experience — there is absolutely no substitute for taking the time for successful implementation. The quality of training during the software implementation phase can have a significant impact on the long-range value of the software application.