Resume

2008 ⮕ 2020: zu Communications

Devon's Roles:

• Developer, Lead Developer
  • Found ways to improve Performance and Accessibility in all projects.
  • Focused on implementing Front End best practices.
  • Successfully launched several projects on various types of technology.
• Scrum Master
  • Removed obstacles from teammates.
  • encouraged process improvements.
  • helped the team stop doing what they didn't like doing (a happy Developer is a productive Developer).

Devon's Projects:

• Several Proprietary Website Builds.
• Several Proprietary Website long term Maintenance projects.
• Several Drupal 8 builds.
• Several Drupal 8 long term maintenance projects.
• Some Expression Engine, Wordpress, and Drupal 5/6/7 builds.

Devon's Initiatives:

• Learning Lunch
  • These were originally intended to bring Developers together but expanded to sharing knowledge from all employees in different formats. Some formats were short presentations on what the team is currently doing, to watching presentations from external developers online, to having Lean Coffees (branded as Lean Lunch) to open the floor to anyone who wanted to attend.
• Device Lab
  • As the world's usage of mobile devices to connect to the web increased, I needed to be able to ensure that we were testing our projects on real devices.
  • To ensure I was providing the best experience for the end user I helped to created a Device Lab.
  • In the Device Lab there were several different phones and tablets on various operating systems. At one point there was multiple versions of IE running on several versions of Windows.
  • One fun perk of the Device lab was that it was possible to control multiple devices from one device.
• CLI Standardization
  • With many different projects on many different setups, switching between working on one project to another project several times a day was taxing on the brain to know what commands to run on the CLI.
  • To remove this impediment I implemented a standardized Makefile for every project. In the Makefile there are common commands for all of the sites: Generate CSS, Deploy the site, and Clear the Cache are a few examples.
  • All of these commands ran different code on a per site basis as. For example make clear_cache could clear either Drupal's Cache, Expression Engine's Mustashe Cache, Varnish Cache, or something else depending on what the site was built with.

Technology:

• When hired, almost all of the projects were on different versions of a Proprietary software that was built internally.
  • Several of those projects I worked on.
• After a couple of years that version of the software was replaced with another Proprietary software.
  • Only a few projects were completed with this new software. I worked on all of these projects.
• Upon seeing the complications to maintaining and hiring for a Properietary software they began investing in Drupal.
  • Successfully built, launched, and maintained several Drupal 8 projects.

2005 ⮕ 2008: 2WebDesign

Devon's Role: Lead Developer

• 2005-2006
  • Only Developer at company
  • I completed all development work no matter the tech stack
  • Created 2WebDesign's proprietary CMS
• 2006-2008 Lead Developer
  • Trained other developers and encouraged a collaborative environment