Open to new opportunities
Senior Web Developer
JavaScript · PHP & WordPress · React & Next.js
Over 15 years, I've worked on 30+ CMS projects across agency and in-house roles, including two 1,000-page migrations, cutting 5-second page loads to the 1-second range. The 2022 rebuild of seismic.com increased visitor traffic by 50% in the first year. Regularly trained groups of 1 to 10 on website operations.
Selected case studies
“Blake is the kind of developer every team hopes to have. He’s fast to learn, deeply responsible for outcomes, committed to high standards, and consistently focused on delivering business impact.”
“Blake is, without exaggeration, the most capable web developer I’ve worked with. He combines deep technical expertise with calm, focused execution, even under the most intense deadlines.”
“Blake is one of the nicest, most patient, and dependable developers I’ve ever worked with. … You will very rarely hear a simple “no” from him. He’s the kind of guy that looks for solutions and ways to get to yes.”
Public repos and tools on GitHub
Next.js with Sanity landing page built from a Figma spec as part of a Teleport front-end coding challenge. Canvas product animations, zero axe violations, 100 Lighthouse mobile run, and font subsetting reducing loads by 89%. Docker containerization and PNPM hardening to protect against supply chain attacks.
WordPress starter framework for Full Site Editing block themes, replacing the WP Foundation 6 starter framework I used before 2022. It runs on Docker, so every developer gets the same PHP, NGINX, and MariaDB setup. Fixing instances of "well it works on my machine" situations.
WordPress plugin for exit-intent and timed popups with A/B testing and Google Analytics 4 tracking, redesign from a feature I made at Seismic. The production team can add modals to request-a-demo pages without developer intervention, so a visitor who is about to leave without filling out the form sees a popup first.
How about 500 lines of hand-written CTA styles became four nested SCSS loops, what the generated test page caught, and the four problems found later in the compiled CSS.
After experimenting with several articles on writing with LLMs, I came up with what I feel is a better way to use LLMs without losing your voice.
Six checks that passed on broken code in a Next.js landing page build, including axe reporting zero violations with three accessibility defects.
