Skip to content

About

The only technical person
in the room.

For nine years I was the entire technology department of a Martha's Vineyard solar company: designer, developer, sysadmin, marketer, and first-line support. When it needed building, I built it.

That ended in December 2025 when the company closed. Since then, Mayhew Technology has shifted from client services to building products... an AI voice platform, a commercial SaaS starter kit, developer tools... alongside selected client work, including a production data platform delivered to an investment firm with a full engineering handoff.

Right now I'm looking for steady remote work with a team. After a decade as the only technical person in the room, I want to build inside a system bigger than me: code review, senior peers, problems at a scale one person can't reach. The LLC stays for legal continuity; my focus is the team I join.

Part-time, contract, and full-time remote roles are all open, along with project work through the LLC. Being the whole department for nine years means the range is wider than one title usually covers: web, automation, data, servers, and the unglamorous maintenance that keeps all of it running.

Remote / Worldwide
Open To Remote Work
English

Outcomes Delivered

~200
PV systems designed
in Aurora Solar for a Martha's Vineyard installer
#1
Local search rankings
built and held for the company's core solar searches
337x
Processing speedup
TraceForge raster-to-SVG pipeline, 45 min to 8 sec
73%
GPU cost reduction
PhotoKeep image-restoration platform
11,808
Automated tests
across 1,213 files in the voice/audio SaaS, excluding git worktrees. Measured 2026-08-24
227
API endpoints
FastAPI routes in that same platform, alongside 82 Alembic migrations. Measured 2026-08-24

My Approach

Compound Architecture

Every technical decision is evaluated for its 3-year trajectory. I build systems that become more valuable over time, not technical debt that compounds against you.

Risk Mitigation

I've seen the failure patterns. Part of the job is spotting architectural landmines before they detonate... and saying so plainly, even when it's not what anyone wants to hear.

Velocity Engineering

Speed comes from simplicity. I architect systems that let your team ship faster by removing complexity, not adding frameworks.

Technical Toolkit

Frontend

  • React
  • Next.js
  • TypeScript
  • Tailwind CSS
  • Framer Motion

Backend

  • Node.js
  • Python
  • Go
  • PostgreSQL
  • Redis

Infrastructure

  • AWS
  • Cloudflare
  • Docker
  • Kubernetes
  • Terraform

Data

  • PostgreSQL
  • MongoDB
  • GraphQL
  • Prisma
  • Drizzle

Journey

2025

Self-Employed, Mayhew Technology LLC(Current)

Sole developer on a production data platform for a private investment firm, delivered with a written engineering handoff. Web apps for local small businesses, data-extraction tools for freelance clients, and my own products.

2016

Senior PV Systems Designer & Technology Specialist, Harvest Sun Solar

Nine years as the one-person tech department for a Martha's Vineyard solar installer (through December 2025, when the company closed). Designed ~200 residential PV systems, handled permitting through historic and conservation boards, built the lead-capture software and the WordPress site, ran the marketing and the IT.

Age 14

Self-taught beginnings

Started coding and building for the web at 14. Still how I learn: pick a real problem, build the thing, maintain it long enough to learn what it teaches.

Beyond the Terminal

When I'm not building, you'll find me exploring the intersection of technology and craft. I believe the best technical work comes from understanding how things are made... whether that's coffee, furniture, or distributed systems. That shapes how I approach every project: with curiosity, precision, and respect for the craft.

Positions I hold

Microservices before product-market fit

Most pre-Series-A teams asking for microservices actually need a well-partitioned monolith with clean module boundaries. I will say no and explain why.

AI-first architecture without measurement

Shipping LLM features without evals, cost ceilings, and latency budgets isn't innovation... it's a production incident waiting for a post-mortem.

Rewrites as a shortcut

Nine out of ten "we need a rewrite" conversations end with a strangler migration or targeted refactor. The tenth gets an honest plan... not a blank page.

Hiring to fix architecture problems

If your system needs five more engineers to be reliable, you don't have a hiring problem. You have a design problem.

Elsewhere

Need a hand, or need a teammate?

I'm available for part-time, contract, or full-time remote work... and for project engagements through the LLC. Either way, the first conversation is the same: tell me what needs building.

INITIATE_CONTACT()