I'm not a fan of the word consulting because of it's negative connations. I work as a system architect, project lead or, developer. Regardless of the type of contract my goal is to make sure the customer is happy with my work and the project is a sucess. Sounds hokey but it's true. Visit my LinkedIn site.
You can view my resume by following the link. By way of an introduction I have spent the bulk of my career in the banking and point of sale industries. These are industries where accurracy, security, and efficiency are critical. I have developed ACH/NACHA processing for back office work, document and image archive systems, image quality assurance systems, data acquisition and distrubution services as well as the UI's for dashboarding and managing these types of systems. Companies in tthe banking and POS (point of sale) industries are constantly merging and I've done a lot of system integration, bringing together disparate systems. I've worked for Ingenico, when it was CheckMate, MetaVante (formerly Brokat), Bank of America, and most recently my primary contract was 4Access Communications, a POS startup where I architected and lead the development team for all their server side systems and customer UIs.
Some of my other experiences have been working with the Georgia Department of Corrections in developing and maintaining their systems for tracking inmates in the state prisons and contracting for Southern Electric, the nuclear power division of the Southern Company.
A good book on the subject of designing new systems from scratch and how to avoid some of the pitfalls associated with such an undertaking. I recommend a book by Phil Simon named Why New Systems Fail: theory and practice collide. I don't agree with everything Mr. Simon has to say but, as someone whose been in the trenches, I have experienced a lot of the same scenarios he has. This is a good book for system architects and their clients alike.