Ringo Starr

Ringo Starr

Drummer • Songwriter • Software developer. Peace & love—and clean, tested code.

Featured Projects

Yellow Subroutine

Backend

A microservice toolkit for streaming events—runs deep, handles pressure, stays shipshape.

Go • gRPC • Postgres
Repo

Octopus’s Docker

DevOps

Opinionated Docker/K8s stack with compose profiles for local-to-cloud parity.

Docker • Helm • Terraform
Repo

Ticket to Ride-Share

Product

Sample SaaS demonstrating event-sourced bookings and CQRS patterns.

Node • TypeScript • Kafka
Demo

Helter Linter

DX

Git hooks + lint/format presets to keep repos in time—no more off-beat builds.

Pre-commit • ESLint • Black
Repo

Peace & Love API

API

A playful REST/GraphQL service returning inspirational snippets & tempo-synced quotes.

Python • FastAPI • GraphQL
Repo

About Me

I’m Ringo—yes, that Ringo. When I’m not behind a Ludwig kit, I’m behind a keyboard building reliable, well-tested services. I love developer experience, steady tempos in CI/CD, and shipping software that keeps the band (product, ops, users) in perfect time.

  • Event-driven backends & API design
  • DevOps: containers, orchestration, release flow
  • DX tooling, docs, and mentoring
  • “Peace & love” code reviews—kind, clear, actionable
Download Resume

Headshot from Wikimedia Commons (DearMoon interview crop).

Contact

ringo@open.build
GitHub LinkedIn

Send a Message

Want this to email ringo@open.build? I can wire it to FormSubmit or a serverless function on request.

Ringo Starr in 2007 (Wikimedia Commons)
Photo: Wikimedia Commons user upload, 2007.

Schedule a Call with a Developer

Choose an option below to book a call via Zcal:

Hire as Contractor Interview for a Job

Developers: Update these links with your Zcal scheduling URLs. See README for setup instructions.

Contractor Agreement & E-Signature

Fill out the agreement below to hire a developer as a contractor through Open Build. The signed contract will be emailed to contracts@open.build.

All agreements are sent to contracts@open.build for confirmation and storage. See README for best practices.