Selected Work

The Challenge

Loading... was a cloud-powered brute force attack prevention plugin that tracked failed login attempts across all WordPress sites using the plugin. If any IP had too many failed attempts, they were blocked from logging into any site with the plugin installed. The plugin went viral and grew over 4000% in just two months.

Their large 64-core server simply could not handle the request volume, and their internal team lacked the experience necessary to solve the scaling problems. Through mutual contacts, I was brought in to help.

My Role

I implemented a temporary scaling solution using ElasticHosts that allowed them to continue operating while we searched for a better long-term solution. The fundamental problem was that WordPress is a blogging platform, not a service architecture. Using WordPress as the backend API was causing massive performance problems.

I rebuilt the backend REST API using CodeIgniter instead of WordPress, which immediately solved the performance and scaling issues. We eventually settled on Heroku for hosting, and I converted the platform from MySQL to PostgreSQL because PostgreSQL scales significantly better for this type of workload.

Beyond the core platform, I developed several CodeIgniter models and controllers including a cron model, job control model, and components for their paid services like malware scanning and uptime monitoring. These revenue-generating services helped keep the core brute force protection free for all users.

Outcome

The platform stabilized, scaled successfully, and was acquired by Automattic in August 2014, almost exactly one year after I started. The technology I built was integrated into the Jetpack plugin where it continues to protect millions of WordPress sites.

The Challenge

Six Flags came to Loading... looking for a modern website that could better support their brand and multi-park operations. They needed integration with their legacy point-of-sale system for gate ticket sales and a better way to present content across their many locations. This was the largest project Loading... had ever undertaken.

My Role

I was given the task of leading the entire project. I selected all of the technologies that would be used on both the backend and frontend, including all of the visual UI elements you could see on the website. I personally wrote most of the HTML, CSS, jQuery, and PHP, with some help from other developers on tasks that suited their particular capabilities.

Beyond the technical work, I managed the relationship with Six Flags' project managers, who were some of the best I've ever worked with. They were as fun to work with as the parks themselves.

Impact

This was our first Scrum-based project at Loading..., a methodology I had been eager to try. The success was so clear that Loading... adopted Scrum exclusively afterward and completely moved away from Waterfall-based projects. This project was a real turning point for the company, showcasing what we were capable of when working with proper technologies, methodologies, and great clients.

The Challenge

CU initially came to Loading... looking to have us implement a design being produced by another firm. When that relationship broke down, I proposed that Loading... handle both the design and implementation. Our designers impressed the CU team with wireframes and mockups, and we were given responsibility for the entire project.

My Role

As the technical lead, I was responsible for all of the backend development and a significant portion of the frontend theming. Beyond the build itself, I was tasked with training the entire CU staff on how to maintain the website.

Prior to using Drupal, the CU team was spending between 120 and 200 hours per week maintaining their web presence. I helped them cut this by at least 90% by showing them how to use Drupal effectively and introducing new methodologies and best practices for website maintenance.

Legacy

I became the go-to technical contact for CU's IT department long after the project was finished. When the team had questions, Michelle would reach out to me even years after the project completed. I enjoyed working with them, so I was happy to provide ongoing mentoring and technical advice. That kind of lasting relationship speaks to the quality of the work and the knowledge transfer we achieved.

The Work

I supported both agencies as a senior contract developer across a wide variety of projects. The work ranged from new builds and complete redesigns to complex integrations and performance tuning for existing sites.

On the development side, I implemented and maintained Drupal sites of varying complexity, handling module configuration, custom code, and theming across many different client stacks. On the operations side, I performed Linux system administration for hosted environments, including troubleshooting, security hardening, and performance optimization.

Process Improvement

I helped standardize development and deployment processes at both shops, including Git workflows, Agile methodologies, and environment strategies. I collaborated closely with designers, project managers, and non-technical stakeholders to translate requirements into practical, maintainable solutions.

The Beginning

I worked with Loading... in two capacities: first as a contractor from 1998 to 2006, and then as an employee from 2006 to 2013. In 1998, Loading... was one of my long-term clients. I handled all of their Linux systems and network administration plus some PHP/MySQL development. At the time it was just myself, the owner Loading..., his secretary, and an intern developer. We specialized in custom PHP/MySQL CMS systems.

Transformation

When the owner asked me to direct the company's technical direction, I became Director of IT. The first thing I changed was to get rid of the custom CMS development path and adopt Drupal as our platform of choice. As a result, Loading... became a premier Drupal development shop and certainly the top shop in the Rockies at that time.

I wore many hats with this company, from architecture and development to Linux and virtualization work, to leading the transition from Waterfall to Scrum methodologies. It was a great ride.

Transition

In 2009, I had to move back to Maine due to the failing health of my parents. I worked remotely for three years, but the occasional data center trips became too much. I spent two years looking for my replacement and eventually hired Loading..., who I felt confident could continue what I had begun.