About

No surprises

Do one thing. Do it best.
I'm a web engineer, and I love the code. Software gives you something few things do: an answer right away. It works, or it doesn't. This page is about the person behind the apps and the standards I hold my work to.

Why I do this

I love writing code, and I love how fast it tells you the truth. You run it and it works, or it doesn't. No politics, no waiting. That instant answer is why I became a developer, and it's why I'd rather spend my days on the code than on anything around it.
Mabel's Dad is where I put that: small apps, each with one job, made by one person in Maine.

The rule I was handed

Years ago I had a boss who became a mentor. He gave me his number one principle for software, and I've carried it ever since.
No surprises.
For engineers, it means code that someone else can read, review, work on, and run without an ugly shock. For the people using what I build, it means an app does what it looks like it does, and nothing else.

Why Lost Wallet is already on version 2

Lost Wallet was the first app, and its first version did more than it needed to. It had a vault, sign-in emails, and an API, and with them came network traffic: what people typed, travelling to a server and back.
1

The vault

A server that held what people saved. Anything a server holds is something to defend, forever.
2

Sign-in emails

A way for the server to know who you were, and a message sent to your inbox. More traffic, and more places for things to go wrong.
3

An API

The doorway between the app and the server. Every doorway is one someone can try to open.
Version 2 has none of it. No vault, no emails, no API, no network traffic. Nothing a person types leaves their device, so there is nothing to leak, nothing to breach, and nothing to explain. Taking it all out made the app smaller, simpler, and safer, and it showed me my north star: best in class security. I can't say it enough.

Design principles

I wanted the design to be as simple as possible. Three rules keep it that way.

One thing, done best

Each app has a single job: a playbook for a lost wallet, a will, a health care directive. A feature that doesn't serve that job doesn't go in.

As simple as it can be

A screen shouldn't need explaining. I'd rather take a button away than add a tip to explain it.

Nothing that startles

A screen never asks for what it doesn't need and never does what you didn't ask for. No account to make and no ads.

Keystones of development

What I hold the code to, for whoever reads it after me.

No surprises for the next engineer

Code you can read, a change small enough to review, and behavior that matches its name. Someone should be able to open the project and understand what it does.

Claims that checks hold up

When a page here says something about the code, a test reads the code to check it. If I change one and not the other, the build fails.

Secure from the first release

Best in class security out of the gate, not a chapter added later. The surest way to protect something is not to have it: no server, no database, no account.

My north stars

Where I'm headed, whatever else changes.

Best in class security

This is the one I can't say enough. Every page's security policy forbids every connection (connect-src 'none'). A page that cannot send anything cannot leak anything, whatever else goes wrong. That one line is the heart of why I call it best in class.

The simplest screens I can make

If someone has to hunt for what to do next, I still have work to do.

World class, and free

No account, no ads, no paid tier. Security at this level shouldn't be a premium feature.
On November 20, 2026, Mozilla's free public Observatory gave 6 of my sites an A+, with a score of 110.
Run the same scan yourself
Best in class is the standard I hold myself to, not a certificate. The Observatory grades headers, not code, and no independent security review has been done yet. An independent security review of the apps is planned for the first quarter of 2027.

Claude and Cursor are my dev ops

Ask any web engineer which part of the job is the most boring and dry, and the answer is dev ops: DNS, CI/CD, domains. Claude and Cursor are my dev ops. They take on the parts I'd rather not spend my days on, so I can spend them on the code.
I work with agentic coding tools every day, and I'm a believer. It hasn't changed the standard. Whoever or whatever writes a line, it has to pass the same checks and keep the same rule: no surprises.

What you get

No shock, no surprise. Just value: one job, done as well as I can do it, at a world class level of security, and free.
See the receipts: Under the hood
Start with Lost Wallet