Shipping products at eighteen, while still in school

I wrote my first line of code at eleven. I am eighteen now, still in school, working at a small IT company, and building Runway in the hours around both. People assume the interesting part is the timeline. It is not.

The thing that compounds is caring

Six years is not that long. What made the difference was never raw speed — it was refusing to ship something I would be embarrassed to explain.

That sounds like a personality trait. It is closer to a process:

• Read the code back the next morning before you call it done.
• Use your own product in the ugly path, not the demo path.
• Write the error message a stranger would need, not the one you can decode.
• When something is 90% right, the last 10% is the part people remember.

Working somewhere real changes your taste

Building side projects teaches you to make things. Working at a company with actual clients teaches you what happens after you make them: the support ticket, the misread label, the thing that only breaks on someone else's network.

You cannot learn that from a tutorial. It permanently changed how I design interfaces — I now assume the person using it is tired, in a hurry, and does not care how clever the implementation was.

Why infrastructure

Because it is the hardest place to fake it. A landing page can look impressive while doing nothing. A deployment platform either boots the VM, restores the cache, streams the log and hands you a working URL, or it does not.

There is no room to hide, and that is exactly why I like it.

The goal

Run my own company as founder and CEO. Everything I build now is practice for that standard — and honestly, I would be doing it anyway.