Hi, I'm William.

A short overview of who I am, how I learn, and how I approach building things.

At a glance

Why there’s no education, experience, or résumé here

I’m still early in my learning and don’t have formal industry experience yet. Rather than listing coursework or roles that don’t reflect my actual skills, I’ve chosen to focus this site on concrete projects and experiments.

The work here represents how I think, how I approach problems, and how I learn from things that don’t work the first time.

How I tend to learn

Hands-on first

I understand things best by setting them up myself, even if I don’t fully understand them yet.

Breaks are useful

When something fails, that’s usually where the real learning happens. I treat breakage as a signal, not a setback.

Mechanics over gloss

I care more about how something works internally than how polished or impressive it looks.

What keeps my attention

What I tend to avoid

How to read the projects here

They’re exploratory

Most projects start with a question, not a finished design. Some exist purely to test an idea.

They’re scoped tightly

Each project focuses on one or two concepts instead of trying to solve everything at once.

They reflect where I was

Each project is a snapshot of my understanding at the time, not a claim of mastery.

A small personal note

I tend to learn slowly but thoroughly. I’m more comfortable being confused for a while than moving on without understanding what actually happened.

If something here feels deliberately limited or incomplete, that’s usually intentional.