I guess a good place to start is with my signature: "Developer, Researcher, Consultant. (In no particular order)":

I consider myself a developer because I have been developing software since the late 80's in high school and professionally since coming to the U.S.A in 1994 as a graduate student. I have never stopped, nor do I foresee that I will in the near future - I simply love to code and produce working, (mostly) useful software.

I consider myself a researcher - albeit new to the field - because I have unanswered questions about software development and I am actively pursuing answers for them. These unanswered questions revolve around the effectiveness (or lack thereof) of current development techniques. If I have piqued your interest, you can read about it in more detail here. I have always been an 'academic' in industry and a little too practical-minded for Academia. I have a few published refereed papers conferences that date back to my undergrad days until present. I have even gone back to school at UMass for a PhD in CS- but that particular effort was aborted after 2 years for, shall we say, creative differences :) In the end, I hope to continue to work on solving some of the issues that I see within the software development community, and hopefully contribute to their solution.

Finally I am a consultant by trade. I have worked full time at various companies as a full-time developer/designer/architect/instructor/project manager, and have been working as an independent consultant since going back to school in fall of 2003. I currently help companies build software in a number of ways that include but are not limited to architectural/design mentoring, agile coaching, and instruction in both OO design/analysis/development techniques and/or agile development techniques.