I'm on the Open Source team at Apollo, working on a loom to weave the global data fabric.

Worked on editor tools, when that was a thing GitHub did.

For two years, I taught at Fullstack Academy—primarily at Grace Hopper, our coding immersive for women. I lectured daily on CS topics, React, and Node, act as PM on student projects, and design curriculum and tooling.

• 👩🏽‍🏫 Daily lectures: CS topics, JS, React, Express, Node, HTML/CSS, etc.
• 🤖 Frequent lectures on system design, engineering responsibility, and robots: friend and foe
• ⭐ Guide student project work, acting as PM / tech lead
• 🦈 Prep students for technical interviews
• 📚 Design curriculum & tooling to support it

Hopscotch makes a visual programming language for kids for the iPad and, now, the iPhone. This was my first foray into mobile development, and the first time in a while that I'd worked as senior dev for a small, agile team.

• 📱 Worked with CTO to rewrite the code editor as an iPhone app
• Wrote a ton of Swift and Objective-C (I 💜 Swift)
• 😬 Productionized a JS+WebGL port of the Hopscotch runtime
• 🦄 Built a WebGL text layout system to handle emoji identically(ish) to Core Graphics
• 🚞 Kept Rails on the rails for the most part

I left full time development to work as an instructor at Dev Bootcamp. Teaching, I quickly discovered, would be the most powerful and rewarding job I'd ever had.

• 🛤 Daily lectures on a Rails / JS frontend curriculum
• ⭐ Guide student project work, acting as PM / tech lead
• 🦈 Prep students for technical interviews
• 🎓 Postgraduate technical counseling
• 📚 Curriculum design

My team handled the deployment, monitoring, repair, and production tuning of numerous large services at Google. I fought fires, saved services, occasionally broke them, and carried a pager.

• 🚀 Worked with developer teams to design, document, test, and safely deploy large scale architectural changes
• 📉 Designed monitoring for complex services and developed capacity plans for services running on thousands of machines
• 🔥 Diagnosed and repaired perplexing issues arising from, for example, the interplay of new code, ancient bugs, and recursive asynchronous processing pipelines
• 📟 Carried a pager

At NOAA, I worked on tools for forecasters, and a projection art museum exhibit called Science on a Sphere, which is probably the visually coolest thing I have ever worked on for money.

• 👁 Rebuilt graphics pipeline with shaders and DMA video streaming. This 4xed our pixel throughput.
• 🐭 Shrunk our hardware footprint from four computers down to one (it grew again)
• 🐍 Built forecaster tooling in scipy
• Invoked deep bluetooth hackery to add a full Wii remote interface
• 🕸 Improved our workflow. Before: Makefile maze, environment variables passed down by oral tradition, source in CVS. After: continuous builds and testing, hermetic packages, source—alas—in Subversion.