I use MadCap Flare, an XML-based help authoring tool, regularly in my work as a Technical Writer. Until recently, I was a Windows user, so running Flare (a Windows-only application) was never a problem. Not too long ago though, I switched over to Mac for various reasons (none that are worth exploring here – that poor horse is already well beaten).
The first obvious challenge this presented was, how would I run Flare, since it runs only on Windows? Well, I didn’t make the jump to Mac without first considering this – I knew of a few solutions. Since keeping two machines around just did not make any sense whatsoever, the first viable option was just run Windows using Boot Camp. Anytime I needed to use Flare or another Windows-only app, I could use Mac’s Boot Camp and reboot into a natively installed version of Windows and go along my way.
The problem – I use Flare a lot – booting back and forth did not sound like how I wanted to spend all of my time. I needed something better.
The solution – virtualization – use software to run the second operating system on top of my native operating system.
With virtualization, I had a few choices. Mac has a program called Parallels, which allows you to run another operating system (Windows, for example) on top of the Mac operating system, for around 80 bucks.
There’s an Open Source solution, VirtualBox, offered by Sun, that will also run on Mac (or Windows, Linux, or OpenSolaris).
And also, there is VMware’s Fusion for Mac, which, like Parallels, for around 80 bucks will let you run your second operating system on top of Mac OS X.
In the end, the choice ended up being made for me – my company bought licenses for Fusion (since we develop software that runs on VMware, it was the logical choice).
Once installed, I used Fusion to load a pre-built Windows XP virtual machine. Once booted, the virtual version of Windows is no different than Windows running on a dedicated device – I was able to install Flare, adjust my environment settings, and I was ready to go. The real beauty of using Fusion, though, is Unity mode. This allows you to run your Windows applications as if they’re running natively, on Mac. Basically, Unity mode strips away the Windows OS front-end and allows the Windows apps to be launched directly from Mac OS X. They appear right in the dock when running, just like any other Mac application.
Even better, Flare (and any other installed Windows application) can be found and launched using Spotlight – note the tag “Doc Dev” after MadCap Flare in the following image, that’s Fusion letting me know that this app lives on my Windows virtual machine, which happens to be named “Doc Dev.”
Virtualization offers a ‘best of both (or any) worlds’ scenario. For me, that was sticking with the Mac OS X operating system and having access to the tools I need to get my job done, regardless of whether or not they were actually built to run there.
Certification for Technical Communicators – do we really need it?
Some of those in the Tech Comm profession may feel (and rightly so) that we spend a lot of time attempting to legitimize our existence – whether it be to our current employer, as a required member of a development team, or generally feeling the need to prove the value we provide. There’s often a cloud of insecurity looming not too far above the heads of those that carry the Tech Comm banner – granted, today, there are many insecurity clouds of many sizes looming over a lot of folks in the software industry – but Tech Comm folks have a much more mature relationship with their personal clouds.
Will an ‘official’ certification help to assuage any of those feelings by helping to cut through the dark nebulosity’s hanging above? Probably. Maybe, for some.
But there is still much to be said for *just* doing your job well – being a positive, contributing member to whatever team you belong to and *earning* the respect of your co-workers and superiors, through results. Would a certificate help with this process? No. Most software developers (and yes, even some in management positions) aren’t interested in what it is that a Tech Writer even does, let alone, whether or not they’re certified to do it.
Now, maybe this isn’t as important for those of us that have been around for awhile. Maybe I’m taking this too personally, as a Tech Comm guy who no longer belongs to the Society For Technical Communication (STC) and has been doing this job for nearly a decade. But maybe for future writers, certification can help give them that little edge needed to stand out in a pile of resumes. Maybe.
Or, on the other extreme end of that spectrum, maybe it’s just an attempt by an organization to further legitimize its existence and add some clout – hopefully attracting more members in the process (and earn some money along the way – the certification program will not be free, after all).
Now I let my membership lapse a long time ago – after only a couple years. I felt the overall relevancy of the organization had waned, even in the short time I belonged. The association looked good on a resume when first starting out – so I had read – so I joined, but after I had established myself and made my way along that Tech Comm path, I lost interest. That said, I still watch curiously from a distance, and participate vicariously through various twitter and blogs and it does seem that the focus has begun to change, recently, and for the better. The organization does appear to be doing a better job at keeping up with current trends – and – of even more importance, they have a lot of support from a lot of very talented people.
I’ll wait and see where this goes – and I’ll never say never, again – but I’m interested to hear what other tech writers have to say.