From the first word processing system I got permission to learn so I could teach the clerk/typists in the office at Wright-Patterson AFB, to briefing Dr. Marvin Langston, then Assistant Secretary of Defense, on Knowledge Management issues that related to The Pentagon's mission, I've found ways to involve myself in technology projects.

Figuring out how and why things work is something I've been doing since I was a kid. The radio and turntable were carefully taken apart and put back together again. At 17 I rebuilt the carb on my Javelin. I always want to know what makes things tick.

Same thing in the world of code. When I taught a web design class they all wanted to learn Dreamweaver. We did that after they learned how to work with HTML. Know the core and you can figure out most things.

At CMS Information Systems, I went from web designer to Autonomy guru in a little under a year. Autonomy was just getting a foothold in the US and CMS was one of their primary service providers. In a two year period, I designed front-ends for, lead teams for the installs, and trained end users on six different systems between government contracts and private sector clients.

I'm very versatile and can learn most technologies with very little ramp up time, but I'm not a "hard-core" coder. You can put me in a red team for proposal writing, and you can have me write training manuals for end-users. I can then train the team on best practices, and deliver a seminar at eGov if you need someone who can do that.

In a nutshell, I can help you achieve your goals because I have the ability to synthesize many parts into a reasonable, coherent project.