pk@dev:~$
// full-stack developer build.2026

Building things worth using.

I build full-service web applications — SaaS platforms, business tools, and internal systems — with an obsessive attention to correctness and craft. 4+ years, thirty-something products, one consistent answer to is it done?

~ / phil · zsh · 92×24 ⌥+T
>
connected main · clean utf-8 · lf · ts
01
years.shipping
since 2022
02
apps.deployed
production
03
industries.served
b2b · b2c
04
coffee.consumed
and counting
01 — CAPABILITIES

What I build.

Three flavors of the same job: take a complicated business problem, model it correctly, and ship the smallest thing that actually solves it.

./saas 01/03

SaaS Platforms

Multi-tenant applications with billing, onboarding, and feature gating. Built to scale from day one — without architecting yourself into a corner.

auth · rbac · sso
billing · subscriptions
admin · feature flags
tenancy · audit logs
./tools 02/03

Business Tools

Custom admin panels, inventory systems, and workflow automation that replace the SaaS tools companies outgrow. The ones nobody else wants to build.

inventory · orders · ops
crm · reporting · etl
document · pdf · esign
integrations · webhooks
./devops 03/03

DevOps & APIs

Internal tooling, monitoring dashboards, and API integrations that tie systems together and keep everything running while you sleep.

ci/cd · iac · containers
observability · alerting
api gateway · graphql
queues · workers · cron
02 — APPROACH

How I work.

Shipping fast is table stakes. What separates good software from great is what happens before the first commit and after the last deploy.

// principles.config
count       4
strict      true
negotiable  false
// 01

Understand the problem deeply before writing a line of code.

Most of what people call "engineering" is really translation: from a vague business worry into a model that's small, precise, and complete. I spend more time in plain English than most engineers — and it saves months downstream.

priority critical impact months saved
// 02

Ship working software, not future-proof abstractions.

A boring three-table schema that's in production beats a beautiful five-layer abstraction that isn't. I write the smallest thing that solves the problem, ship it, and refactor only after the shape of real use is visible.

priority daily impact ships faster
// 03

Own the full stack — from database schema to UI interaction.

The seams between layers are where bugs live. A single person who can chase a problem from a click through a queue into a stored procedure ships finished work, not handoffs.

priority always impact no handoffs
// 04

Maintain relentlessly. Launch is just the beginning.

Most of a system's life is after launch. I write tests that protect against the bugs you'll regret, set up the dashboards that let you sleep, and stay around long enough to know whether it worked.

priority ongoing impact you sleep
03 — RECENT WORK

Projects.

$ ls -la ~/projects · 4 entries
$ more available on request — nda-protected client work, internal tools, side experiments.
04 — LET'S TALK

Have a project
in mind?

I take on a small number of client projects at a time. If you're building something serious, let's talk.

$ start a conversation →
// current.status
booking q3 2026
response time ~24h on weekdays
preferred long-engagement work · 3+ months
rate available on request
timezone cst · flexible
// elsewhere

I don't post much. Email is the fastest way to reach me — but if you'd like to read code first, github.com/WyldHalfling ↗ is the only other public surface.