Being a team player means making work that benefits the team.
I don't strive to wow my colleagues with my code; I strive to empower them. That is why I favor whatever code solution enables the team to deliver its best work.
I work to create clean, well-commented, and well-tested code. I am happy to use stable and battle-tested libraries and frameworks if it means that the next person can take my work and run with it.
One of the best things about coding is the camaraderie formed between engineers. Building strong collaborative peer relationships with other coders, designers, project managers, and product owners has led to my most rewarding professional experiences.
I constructed a modular markup and BEM infrastructure for a group of sites including hylinkexp.com. This allowed me to craft one site and reuse almost the entire codebase for other sites, such as hylinkhelix.com. The sites are backed by a multi-site installation of CraftCMS and coded using a gulp-backed optimization workflow.
At Stillwater, I collaborated with my fellow lead developer to create and implement a multi-site version control strategy that allowed us to build and maintain dozens of independent websites leveraging significantly overlapping codebases. I loved seeing my fellow developers work more efficiently and leverage DRY principles to make slicker sites with increased confidence.