My work has moved from building infrastructure to leading the organizations that build and operate it. These examples cover both.

Financial infrastructure at EasyPost

The work. As a platform engineering leader, I was responsible for financial infrastructure, shared services, and developer tooling. That work included redesigning and automating financial data pipelines to reduce revenue recognition time.

What changed. A shorter revenue recognition cycle connected an engineering improvement to a business outcome. It is one example of why I treat financial operations and data quality as part of platform engineering, not as separate concerns.

Today, as CTO, I lead EasyPost’s technology organization and strategy across platform, product, and experience.

Career account: professional profile. Current role: EasyPost leadership biography.

Engine Yard’s cloud API

The work. I architected and led development of the Engine Yard API. The work extended from the backend to the interfaces developers used to operate their applications and infrastructure.

The public artifact. The official Ruby client and command-line utility, ey-core, expose operations such as application deployment and environment management. The client supports a mocked mode for testing integrations without making live API calls.

The distinction matters: an API is not just a collection of endpoints. Its usefulness depends on whether teams can integrate it, test against it, and operate it reliably.

Career account: professional profile. Software: Engine Yard Core API client.

Speaking: Sapporo RubyKaigi 2012

Release Early and Release Often: Reducing deployment friction

Sapporo, Japan · September 14, 2012 · Engine Yard

I presented Engine Yard’s approach to connecting automated testing, continuous integration, and deployment. The main cloud codebase could be released at least daily while retaining a rigorous testing and release process.

The talk is an early public example of my interest in engineering leverage: reducing the friction between completing a change and putting it into production.

Conference program and abstract · Event report (Japanese)

Selected open-source contributions

Selected changes to tools I use, alongside earlier foundational work. Dates on merged changes indicate when they landed upstream, not ongoing maintainership.

Merged

hotreload.nvim

Replaced interval polling with filesystem-event watchers and limited watching to visible buffers in this Neovim plugin.

File-watching improvements

Merged

jnv

Added configuration-file support for custom keybindings and styles, using the XDG configuration-directory conventions.

Configuration-file support

Merged

Sinatra

Changed default parameter escaping in the bundled rack-protection integration and added a regression test. Both changes were merged upstream.

Parameter-escaping fix

Regression test

Earlier foundational work

fog-aws

I helped get fog-aws started: a Ruby library for working with Amazon Web Services, usable on its own or through Fog. The project lists me as an author alongside Wesley Beary. My involvement was in its early development; I have contributed little in recent years.

Project authorship

Contribution history

I also support Neovim through recurring donations.