The benefits of a resume wiki

Wed, 01 Nov 2006 12:04:38 +0000

One of the immediate benefits of having my resume as a wiki is that I can play with the structure of the content very easily.

The main page is built using the following:

(:include Profile:)
(:include Experience:)
(:include Skills:)
(:include Education:)
(:include OpenSource:)
(:include Events:)
(:include Interests:)
(:include References:)

taking Experience as an example it is built using the following:

(:include PaogaProductManager:)
(:include PaogaTechnicalMarketing:)
(:include EvectorsPartner:)
(:include NovissioFounder:)
(:include HipboneTechnicalConsultant:)
(:include MetadyneDevelopmentManager:)
(:include UnlSeniorIntranetDeveloper:)

where each of these included pages contains the actual wiki markup describing one position that I held.

Now I've had some feedback to say that the resume I built was too long which is right: it reflects my lack of recent experience building or using resumes. The wiki format means I can address this without losing the value of what I've done already.

I am now creating abridged versions of these pages, e.g. "PaogaProductManagerAbridged", which have a "Read more..." link to the full text. By composing these instead I can instantly create both abridged and non-abridged versions and let the reader switch back and forth depending upon how much detail they want.

I've also added a license to the bottom of the main page describing the terms of use of my resume. It's intended to allow legitimate use whilst retaining control over the text. I've no idea how enforcible it is: after all I never gave permission to those agencies who amended previous CV's to include stuff I've never done like Visual Basic. But I figure you have to start somewhere.

Curiouser and Curiouser! on resume

The benefits of a resume wiki