As I progress through my career I am finding the standard resume increasingly limited. This is a concept I came up with as an improvement over the standard resume. This is a step through of various stages in business, and explains what I have done at each step. I can dive into the various aspects of the business and still keep in mind all of the other facets.

1. Document a high level concept in a manner that can be expressed as problems and solutions.
   • I have a good ability to see business problems as technical solutions.
   • I can quickly eliminate vague and subjective statements to terms that are commonly recognized in Information Systems.
2. Create technical requirements through analysis design, and gathering new details beyond the scope of the high level concept.
3. Create a prototype and visual design docs to illustrate the technical approach based on steps 1 and 2.
   • I believe in creating something tangible to write more detailed requirements from. I have a wide ranging of scripting skills such as PHP, ASP, JavaScript, VBScript that I employ to assemble prototypes that are a good tool for developing ideas and requirements.
   • A prototype can also double as a proof of concept in many cases. It’s a good step to take before making very critical decisions.
4. Setup a requirements repository for tracking the detailed requirements and storing the overall Systems Architecture Documents.
5. Write, request and coordinate gathering more specific requirements to enter into the repository using the design docs and prototypes as a reference.
   • Requirements are always useful regardless of the size of the project, they help the Software Development Life Cycle make a complete revolution like it’s supposed to by having something that is tracked from concept through production and beyond.
6. Build out an initial datacenter. Planning, purchasing, and installing the right equipment necessary for the job and under the budget.
   • I have years of enterprise level experience in selecting the right equipment for the budget and need.
   • I take into account many of the factors that are usually necessary afterthoughts such as cable management, KVM switches, and power runs.
   • I always consider the long range business plans and try to make the short term purchases fit into them.
   • I have also been very successful in choosing hardware that saves in overall maintenance costs.
7. Design and implement a database schema.
   • MSSQL 2000, MSSQL 2005, MySQL 4-5
   • I have years of experience at all of the stages of a database systems lifespan.
   • In addition to traditional approaches to database development and management, I always consider the larger application design in context to the database, I do not treat it as and island system.
8. Design and develop an application.
   • DHTML, AJAX, Flex, Actionscript, PHP, ASP, Javascript, VBScript, .net
   • I specialize in web application development with a database back end.
   • I am very good at customizing, manipulating, and integrating with .net applications of all sorts.
9. Setup a bug repository for the application.
10. Coordinate QA for the application.
11. Create a scalability model and performance analysis of the application to determine how viable it will be for the projected load.
    • I use scripting techniques to simulate load, and instrumenting techniques to monitor the results, then I break them down into a formula so they can be projected.
    • Having these formulas are important so that you know how much it will cost in infrastructure to support X number of clients. This will tell you if you need to add performance fixes into your next release, or if your current release can be deployed into production.
12. Deploy the application into production.
    • I use scripting and deployment applications to install, and verify a deployment.
    • Automated deployments are reproduce able and reduce human error. It also allows for multiple iterations on multiple environments to be executed quickly.
    • Automated verification check to ensure that what was meant be installed was installed. If you find a bug in production after the release, you don’t want it to be because certain files are still on the previous version that were supposed to be upgraded.
13. Log and monitor various points of production to get early detection and predictive analysis of issues.
    • The more data that is collected, the more likely you will find critical issues and fix them before they are critical customer issues.
    • Business decisions need to be made with data that can support theories. If you don’t do any logging then you can’t support your theories with anything that can be quantified.
    • Logging does not have to be detrimental to performance. It can be asynchronous, and efficient. I have a great track record of creating effective and performance conscious logging systems.
14. Create monitoring and alerting mechanisms.
    • MOM, SNMP, custom monitoring with scripts, transaction monitoring
    • Email, text message, dashboard alerts.
15. Create maintenance and archive automation.
    • As an application matures it requires maintenance. I use scripting techniques to automate the maintenance, and then submit a more integrated and permanent solution into the next release of the software.
16. Create a management dashboard and a reporting dashboard for a consolidated point of management for the system.
    • Even the engineers on a system can benefit from a central place that coordinates the various tools and reports.
    • Managers need quick consolidated metrics to make business decisions.
    • I have built a management and reporting intranet at several companies using web development techniques so that it could be accessed by any platform at any time.
17. Perform regular security audits on environments and applications.
    • Security is an often forgotten subject until there is an issue with it and then it’s too late
    • I schedule re-occuring audits so that they are not forgotten. I am realistic about what’s worth protecting and where the points of diminishing return are.
18. Track production defects, and requested features and rate them for release deployment.
    • All software will have bugs. As a product matures, it’s how well you handle the bugs that will determine the quality of your product.
19. Coordinate and participate in the successive iterations of releases within a schedule with versioning
20. Make exceptions to the rules, creative solutions, and improvements to processes.
    • Nothing starts out perfect and there is no perfect solution for all issues.

I am happy to assist at any point in the process, fill in the blanks that have been missed, advise, and take actions. I’m not excessively rigid in process, but many of the industry best practices do serve as a good guideline.

My traditional *resume* is attached to this post as well.