I'm either an engineer or a solution architect.
As an engineer, I'm great at cross-platform systems work -- I've worked on everything from embedded consumer devices to enterprise directories in environments ranging from high-pressure ("the fate of the company depends on you -- stay up all night and get it done!!!") to high-reliability (proposals first, then documentation and prototype, then collect feedback from stakeholders, then propose changes to do it better, and repeat).
As an architect, I walk the line between the necessary (those things which currently define the organization's core mission -- the fuel) and the ideal (those things which would make the organization more dynamic and effective -- the catalyst). A good solution is one which doesn't break the status-quo unnecessarily and which enables immediate gains in effectiveness plus future growth. My challenge as an architect is to not let my engineer side influence decisions too much -- other people have skills, too, and it's not fair to them to draw a small box around what's probably a large set of skills.
Personally, I like an environment which can be high-pressure, but which is generally structured in its needs.
The reasons I want to help non-for-profit organizations through DayOn are:
- To give back to our fair city
- To take on new challenges in new environments
- To meet my need for a high-pressure environment
- To meet like-minded individuals
Thanks for reading, and good luck!
