Picture of Cory. 6 foot 2 inches, light-brown hair, blue eyes, black thick-framed glasses, black North Face windbreaker jacket, jeans. Bookshelf full of random books behind him.

Pertinent Skills


I could use some more work on ARIA roles, microdata, localStorage, but I'm generally very good at HTML.

I understand semantic markup and actually have a lightweight HTML boilerplate with a CLI that works well with a plethora of browsers by default (saves a lot of time on browser testing).


I'm insane at CSS, preprocessors, and PostCSS. This sounds like a silly skill to brag about, but bulletproof CSS architecture is a really valuable skill to have.

Example #1: Reflow is one of the most annoying things in the universe and a problem to this day. I created a mixin that fixes it.

Example #2: Redesigning a production site without breaking anything is very difficult. I did it on a monumental codebase with Teespring.

Example #3: Browser support. Everyone gets this wrong and when they try to fix one browser, they break things in another. Someone well-versed in CSS is familiar with a lot of common gotchas and can save a lot of time by avoiding them. I can literally write a dozen more ROI examples upon request.

I created one of the most popular Stylus projects, and one of the most popular PostCSS projects.

I've read and understand most CSS architectures (SMACSS, BEM, ECSS). I also know CSS Modules are the best thing ever.


I'm good at jQuery, vanilla JavaScript, AJAX, and consuming APIs.

I know ES6+; functional concepts like mapping, reducing, etc.; promise usage to avoid pyramids of doom; some design patterns; code style with ESLint & Prettier (StandardJS is currently my favorite flavor); strong typing with Flow/TypeScript; and modularizing code with imports/exports.

🚨 I won't be able to pass your "Explain how prototypal inheritance and this binding works." I've studied it and could probably explain it if you put me on the spot, but I forget it and still bump into it in weird places from time-to-time.


I've been studying React.js and Vue a lot lately.

I've only made a few simple things, but understand the core concepts (state, props, refs, ES6, functional components, Redux) well and can create builds with a variety of tools (create-react-app, Webpack, Rollup, Browserify, etc.).

I'm excited to finally master one of these.


I've built a lot of custom stuff with Node. It's one of my favorite things to do. I'm very familiar with the API and at least know what standard libs to search through for answers to particular questions.

I've used streams and spun up simple HTTP servers/CRUD APIs with Express, but I wouldn't consider myself super comfortable with them yet.


I've worked with WP for several years. I can write custom plugins with it and have lead development on WP sites with millions of monthly visitors.

Right now I'm focusing on inventing a really nice workflow using a few plugins (ACF mostly) and getting better with the REST API.


I've been working with PHP for several years. For a few years I have worked with Django and Rails so the jump to Laravel was fairly easy. I'm still getting accustomed to some of the gotchas, but will be launching full-fledged products very soon.

What attracted me to Laravel was the really well-maintained official ecosystem surrounding it.


I started my career doing design. It comes pretty naturally to me. I'm comfortable in Photoshop, Illustrator, and Sketch--pretty much any Adobe CC product comes easily to me (I've tinkered with After Effects).

I haven't spent a lot of time with these tools since responsive web-design became a hot topic. Nowadays I prefer to prototype directly in the browser.

I have a lot of knowledge of typography, general design concepts (things like the rule of thirds, contrast and flow, etc.) and I'm especially good at mixing code with design to do things like work with ratios.

What have I built?

Who uses my work?

Who have I worked with?

Who have I written for?