My approach to development is guided by a short set of simple ground rules. It’s never been cheaper or more convenient to learn new things.
Rule 1: Do-it-yourself.
Seek total mastery, and technical ownership by rolling up my sleeves. Avoid turnkey solutions unless there are no other practical options.
Rule 2: Eliminate or minimize cost.
Look to breathe new life into old things. Make use of the great free and nearly free resources available to us in this time. Always try to use open source software, learn from it, and contribute back to it either in gratitude or technical contributions. I am the author of eight open source projects.
Rule 3: Certifications and designations do not demonstrate mastery.
Certifications and designations absolutely have their place. I have earned them in my career. However, I will not seek certification or designation as a way of demonstrating technical ability in this space. Rather, I leave in my wake completed projects, and the lessons learned in success and overcoming stumbling blocks.
Rule 4: Be a craftsman.
Be patient. Take my time and practice true quality. Resist the urge to rush through my work. I prefer the classic to the romantic view of craftsmanship which demands comfort with ambiguity and doing it right–even if it takes longer.
Rule 5: Be humble and transparent (HAT)
Share my learnings and mistakes. Openly admit when I don’t know. Don’t try to project competency or experience beyond my current level.