Qualifications

Here are some examples of the kinds of software that I consider to be well within my capabilities as a solo engineer:

• Passwordless login workflows for single sign-on and identity management for a hybrid of both internal and external services.

• A progressive web application (PWA) for Android and iOS for secure, end-to-end encrypted peer-to-peer messaging and file transfer using post-quantum cryptography.

• Completely automated and continuous deployment of an arbitrary software application and its cloud infrastructure, across multiple regions, with zero downtime and promotions across risk categories driven by the results of live integration testing.

• Designing and instrumenting control systems involving switched loads (e.g: valves, pumps, motors) and sensors (e.g: camera, temperature, humidity, gas), with automation, real-time telemetry, and web-based UI for operators and users.

• Establishing foundational processes, workflows, and automation for an engineering organization in an early-stage / growth-stage tech company, and hiring engineers to build out the team.

Technology Preferences

• Web: HTML, CSS, JavaScript, SVG, browser-native Web APIs, Preact + htm

• App: JavaScript + Node.js

• Runtime: Docker + Kubernetes

• Cloud: Terraform + AWS

• Operating System: Debian Linux (Desktop, Server), Android (Mobile)

Values

• I value honest work that seeks to improve lives in some specific way. I would rather contribute to a product that does one thing exceptionally well than to one with unconfined scope.

• I do not use generative AI in my work, nor do I condone its use by my colleagues.

• I consider myself an advocate for inclusiveness, accessibility, and dignity in the software I build.

  • Accessibility (A11y) for those with vision or hearing disabilities

  • Internationalization (I18n) for accommodating differences in cultural backgrounds and preferences

  • Localization (L10n) for accommodating different languages

  • Privacy and security, with technical measures to ensure user data is well protected, even from insiders (i.e: us)

  • Honest interfaces, free of deceptive design and dark patterns

• I have deep experience building web client applications in React and React-adjacent tools. However, as more capabilities have been integrated into the web platform, my preference for building software for the web has shifted toward "vanilla" HTML, CSS, and JavaScript, with minimal dressing from a handful of lightweight utilities.

Experience

• Tomorrow

  Principal Software Engineer

  • Web
  • Node.js
  • Python
  • Kubernetes
  • AWS

• Smartsheet

  Sr Software Engineer II

  • Web
  • Node.js
  • Python
  • Kubernetes
  • AWS
  • GitLab CI

• Outreach

  Principal Software Engineer

  • Web
  • Ruby
  • Node.js
  • AWS
  • CircleCI

• At Tomorrow, I was a builder. I designed and built circuit boards (PCBs), firmware, progressive web apps (PWAs) for both internal scientific research and for consumer-facing products, distributed systems, and more.

• At Smartsheet, I was a technical lead, a mentor, a systems architect, and a consensus builder. I drove a cross-cutting enterprise governance feature in a complex tapestry of legacy and emergent software systems from concept through delivery while leveling up the team and pushing organizational boundaries for continuous deployment and comprehensive automated quality assurance.

• At Outreach, I was a builder. In addition to delivering core features in the flagship product, I drove the development of the first core app extensions, including the Outreach Everywhere extension for Google Chrome and the Outreach add-in for Microsoft Outlook.

Open-Source Projects

When I have encountered useful projects abandoned by their maintainers, I have occasionally taken it upon myself to inherit maintenance of those projects. Here some examples:

• twuni/docker-registry.helm

  When the stable repo for Helm charts was deprecated, all Helm charts that resided there needed new homes. I adopted this one.

• phusion/node-sha3

  When I was working with blockchain/web3, this library was a common problem due to some install-time hooks and compilation steps depending on undocumented system-level dependencies. The maintainer had abandoned the project, and since this library was a *transitive* dependency of other packages I required, I reached out to the maintainer requesting to assume the maintainer role for the project. To my delight, I was granted maintainer privileges and was successfully able to resolve the issue.

Sometimes, I encounter gaps in some tool or project that are important enough to me that I build those, myself. Some examples of that include:

• nodejs/release-keys

  The Node.js release team's release signing keys were not published in an easily and reliably available manner. So I proposed a process for managing those keys, and that process was eventually adopted by the release team.

• twuni/asdf-yarn

  When I was an active yarn user, I noticed there was no asdf plugin, yet. So I created this one and successfully got it included in asdf's plugin registry.

I have published over 200 other open-source projects across GitHub and GitLab, mostly under my Twuni organization.