I passionately write clean, readable, tested code that solves a wide variety of problems, including asynchronous interoperability, network unreliability, performance with large data, dynamically generated HTML/CSS pages, software interconnectivity, and legacy challenges. I am innovative, and have awards and a patent to demonstrate that. I am good at thinking outside the box. I gladly work with team members and other helpful sources (including stackoverflow.com). I wholeheartedly embrace the evolution toward clean code, and Agile & test-driven development, especially within a continuous build/integration/test environment—CI/CD. I habitually work at a frenzied pace, which allows me to create clean code at a pace that has me meeting deadlines that others may find challenging.Although management may regard executable software as our team's product, I realize that my team's actual product is the source code and other infrastructure that generates the deliverable product. This means I make my work always ready to pass on to teammates. At Adobe, we had a saying: "Do your work so that if you're run over by a beer truck tomorrow, the team can carry on."I am an affable guy. I am friendly toward everyone, and most people are friendly toward me. I am willing to help anyone, though keeping in mind deadlines I must meet. Sure, sometimes I make mistakes, but I regard them as opportunities to learn. (When I taught 'Team Programming in a Business Environment', I taught that it was better to do 9 of 10 things right [supposing the failure didn't hurt the company] than to do 3 of 3 things right, because then someone else would have to do the other 6 things.) As a team player, it is part of my job to get along with people. I've made that part of my lifestyle; it's not just a "duty." Indeed, in the past twenty years, I've not gotten angry at anyone, except once.