thechangelog

Hi there. I'm an experienced full-stack developer seeking some contract work, either one-off or ongoing.

I've built Rails apps for 12+ years (and have taught Rails at college) and am equally at home on the front-end. My most recent work is as the lead developer of an event ticket sales platform that processes millions in sales annually. I was also the lead on an aviation maintenance web app. If you work with HTML email you might also have used my Premailer project from long ago.

On the front-end I've worked with React / React Native / Redux / Typescript, including reaching the holy grail of sharing all the core logic between a mobile and web app in a single code base.

Previously I worked in tourism marketing, so I also have a strong appreciation for keeping focus on ROI and clear communication.

I haven't had much time for open source recently, but I'm happy to give you a tour of some private repos so you can see my work.

------

On the server: Rails / Sorbet, Ansible, Terraform, nginx, MySQL, Postgres, Redis, PHP / WordPress

Client-side: Javascript / ES6, Typescript, React, React Native, Redux, Jest, CSS/SASS, Coffeescript, SVG, websockets, offline web apps

General: PCI / e-commerce / marketing

We've been taking their lessons and applying them to a small municipal site we're building -- topic pages like their VAT example, flat document structure, really robust search. At first we were unsure how many lessons from a national government would apply to a village of a few thousand but it's turning out really well so far. It's a liberating data model in that we spend less time worrying about hierarchies ("is this for businesses or residents?") and more time curating content based on what users will need (e.g. what pages should be drawn into the residents' topic page in the springtime before an election).

We implemented the Luhn[1] algo credit card check on the checkout page. Invalid CCs would trigger a little warning but still allow the form to be submitted. Invalid CC transactions dropped ~90% immediately. Even better we were able to get rid of the 'select your card type' field since that was detected by Luhn. A little JS was a win all around.