<ul><li>Evaluated the existing team and code base</li><li>Eliminated &gt; 100KLOC and shrunk the technical staff while increasing velocity</li><li>Trained and helped level up the remaining engineering team</li><li>Built real-estate listing and data scraping technology, enabling national expansion</li><li>Recruited the next phase of technical leadership</li></ul>

Director of Engineering

I built my last startup with Elixir and I am the voice behind Alchemist Camp.

I worked primarily in JavaScript from 2013-2015 and on and off for long before that. I was part of a team of three that built the front-end of Groupon's merchant Deal Builder app (Node/Backbone) and also worked on much of Verbling's current app (Node/React/Mongo).

OSS contributions: Minor contribution to Underscore.js and fixed a parsing bug in the CoffeeScript Redux compiler.

I've used ruby extensively for Unix tools and scripting, data munging, and also built a MacRuby game and a few Ruby on Rails apps.

Unix has never been my focus, but over the years I've found each time I dig in deeper, the knowledge is a gift that keeps giving.

I was part of a team of three that built the front-end of Groupon's merchant Deal Builder app (Node/Backbone) and also worked on much of Verbling's current app (Node/React/Mongo). In both cases, I was spending a bit more time on the front end but I'm comfortable working with Node.

I've been using React since mid 2014. I used it at my own startup and then as one of two engineers at Verbling (YC S11), replacing Backbone.js in a ~1MM LOC app. Currently working on React front-ends.

Also some experience building a Github Electron app with React/Node.

git has been my source control tool of choice

I'm pretty familiar with jQuery. I used to use it all the time and still use it for smaller projects.

All my work on the Groupon merchant Deal Builder app was Backbone on the front-end. We also used Backbone at Verbling, before migrating to React. I'm fine with Backbone on a legacy system, but I wouldn't start any new projects with it now.

All my work on the Groupon merchant Deal Builder app was in CoffeeScript, and during the course of that work I actually found and fixed a parsing bug in the CoffeeScript Redux compiler.

I've built an interpretter for a DSL (for use in a game) and I've fixed a bug in the CoffeeScript Redux compiler (using PegJS)

It's my go-to DB. Most of my interaction with it has been through a wrapper.

PHP has never been my go to stack, but I've maintained a WP blog and made a few small projects with Laravel.

Python has never been my primary stack, but I've worked with it on and off for many years. I've used it primarily for stats-related work and visualizations, not for web development.

I've worked with JSON on a lot of different things. It's a popular format.

It's usually been in the background of my work. I've never been focused primarily on the DB layer.

We used Mongo/Mongoose as our primary DB at Verbling. I've used Redis as an in-memory key value store on many projects. On Erlang VM, I use ETS for a more powerful version of the same.

I used it for a peer to peer chat startup.

I've been using Tailwind since it hit version 1.0

I've been using Rust on personal projects and studying it since 2019. The largest project I've built with it so far is a roguelike game.

Elixir, JS and Growth

Mark Wilbur

The largest resource of Elixir screencasts online. Fairly fleshed out content management system, virtual currency for feature requests, customer billing, Gitlab CI/CD pipeline and analytics. Running on Ubuntu with systemd.

(2018-present)

Alchemist Camp

A book for Elixir learners. Written as a static VuePress site, with a custom integration to embed it within the larger Phoenix app that powers Alchemist Camp.

Personal details

Mark W.

Technical skills

About

Work Experience

Projects

Education