- April 21st, 2010
- Write comment
It’s an important distinction, in my mind.
A person who is driven has pre-set motivators to get a job done. For example, someone at a workplace that is driven has the goal set for them; a paycheck, a promotion, etc… Nothing that they’ve created for themselves.
The Driver, however, has the goal in mind, that they’ve set. The path is their choosing, how to get there, what tools they use, orthodox or not.
In most workplaces, being the driver is difficult. Keeping in line with the “industry standards” is part of the IT ideal, and is halting creativity in many organizations, trading the new and inventive for “stable and boxed” systems. Holding off the pitchforks of the nay-sayers, the Driver has to produce quickly and efficiently.
Want a real world example? Here’s one from my experience:
I’m setting up the deployment for Windows 7. Unfortunately, the “industry standard” is to use SCCM and Sysprep. However, there are some issues with deploying SCCM to our live environment that I can’t get into right now. Sysprep has issues with what I’m telling it to do, to I’m ignoring it right now.
I know my goal: Deploy Windows 7 in as small an image as possible, without using Sysprep and SCCM (or ImageX, but that’s another matter entirely).
How am I doing it? AutoIt scripting. 98% of the “sysprep” that I’m doing makes up for the lack of Microsoft Sysprep and SCCM/ImageX. The other 2% is using Ghost Solution Suite for image deployment.
I can image a workstation in 8.5 minutes. It’s roughly 5gb. It’s not kosher in the setup, but the end result meets, if not exceeds the goal, and complies with the “industry standard” on the other side.
I am a Driver. Are you?