So in case you haven't noticed the change to my profile I recently became a full-time contractor. In addition to working previously as an analyst programmer for Tourism Western Australia, I started consulting half a day per week to assist the Department of Education and Training with the migration of a number of sites to MOSS 2007. Last August I started looking to move on from Tourism to get out of government and the associated politicking, make private industry dollars, and extend myself a little bit (fortunately I was smart enough to turn down an offer from Commander). The consulting gig proved contracting isn't so bad so when a Developer Coordinator contract position was advertised back at Tourism I couldn't help but take the plunge.
Working as a consultant for DET is quite rewarding. SharePoint and MOSS actually behave in the DET environment. While they've gone down the customised branding path they've also stuck with OOB web parts so to date I haven't faced any really tricky problems; as the 'expert', I'm in a position I like to be in. Apart from that, a single developer has managed to put together three sites in a around three months so it's good feelings all around. http://www.westernaustralia.com/ and http://www.tourism.wa.gov.au/, by comparison, took nearly eight developers (on and off) and half the organisation a year or more to launch. That said, we were one of the first branded sites to roll out on the MOSS 2007 platform and we had many, many, many technical problems with an early MOSS beta.
I'm three weeks in to my contract at Tourism and I've been surprised at the differences not only between quasi-permanent employment and contracting but at the differences in conctracting for different agencies. I'm also reading The Peter Principle at the moment and trying to assess whether this Tourism "promotion" has allowed me to arrive at my level of incompetence!
Apart from the 40-hour week versus a 37.5-hour week and being conscious of the fact I'm no longer entitled to sick leave, public holidays, or anual leave, I'm also keenly aware I really need to earn my keep now--in other words, there's no room for incomptence. I was on a fixed-term public service contract (salary, holidays, sick leave, etc but with a finite contract term of two years) as an analyst programmer and was cheap to employ; as a contractor I earn a lot more money and cost my employer a lot more money. More importantly, my contract runs for a mere six months and in that time I have to prove my worth by working to a controlled work package to produce the expected output. Luckily I've been in a position to define the schedule for delivering that output.
At Tourism I work directly for the CIO and I'm tasked with fixing content deployment and some other big-ticket items. The Tourism CIO is an alright guy but he's reasonably new to the organisation and intent on running a far more controlled IT department than his predecessor. While I welcome the change, moving from the previous free-for-all situation to such a formalised, process-driven environment is a swing back in time for me as a former EDS employee. I know my abilities and know I will deliver what I'm asked to deliver (process or no process) so to have a really hands-on superior managing me so closely--at least initially--has felt overbearing at times. EDS was very formalised and process-driven but my managers trusted me and as a young go-getter I never felt the opportunity to become incompetent.
It's unfortunate that despite coming back to work for the same organisation I have to prove myself once again to the new CIO (our previous CIO left a year earlier). Realistically, I'm doing very different work in my new role so I'm happy proving myself to everyone, at least a little bit. I've also been paired with an architect mentor to assist me in making the transition. I'm comfortable with the mentoring arrangement and looking forward to learning as much as possible but I'm also confident in my own abilities, I know the software, and with such a shortage of developers in Perth I'm simply the best person for the job. I don't mean to sound arrogant but in reality I've been doing a lot of what's required of my current role for my entire career of four years.
At the moment this adds up to me questioning my abilities and desire to produce quality output. Sure, I need to win the new CIO's trust and to do that I have to deliver what's expected of me on time. I'm also finding I need to win my own trust and prove me to me.
All up, I'm enjoying consulting. Like most people (I assume), I'm happiest when I'm productive and at the moment I'm really pushing myself to be productive so I don't fall behind schedule. At the same time, I'm thriving on the added responsibility and despite being a developer type, I really love being outside my box and engaging with the team and the organisation. I've definitely found the lack of interaction with folks over the past two years a big downer.
Either way, it will certainly be interesting to see how I feel about all this in another six months!
Post a Comment
Spam comments will be deleted
Note: only a member of this blog may post a comment.