I tinker first
Cameras, controllers, remotes, laptops, codebases, VEX robots. If I want to know why it works, I usually have to risk breaking it.
yo wsp, I'm
I'm a teen software engineer passionate about hacking the world around us. I'm currently focused on Hack Club , programming for my school's robotics team, and experimenting with side projects.
How I think
Software engineering has been my thing since I was around seven, but it never stayed only software. It turned into robotics, aviation, CAD, agricultural mechanics, PLTW, golf, and a lot of taking things apart just to understand the order inside them.
Cameras, controllers, remotes, laptops, codebases, VEX robots. If I want to know why it works, I usually have to risk breaking it.
Mechatronics fits because machines and electronics both feel like parts of the same thing. Losing either one would feel like leaving half of me behind.
I help people a lot, sometimes too much, but it feels wrong not to. Explaining something makes me understand it for real.
AI agents are a tool to learn with, not a substitute for talent. It takes real taste and skill to command one well anyways.
Public proof points
I am trying to get better at tracking everything instead of hoping I remember it later. These are the public ones: science fair results, Hack Club shipping, and old Q&A traces from when I was figuring things out in public.
1st place in Cognitive Science, Junior Division, for "Unraveling AI," a project about AI detection and how easily humans can be fooled by AI-written essays.
1st place in Cognitive Science before state, then advanced from the California fair to nationals.
Public build log with 8 projects, 100+ devlogs, 8 ships, hundreds of hours of coding time, and a Summer of Making win.
Selected work
Some are polished, some are jokes that got too real, and some are just me chasing a question until it turns into a repo. That is usually the best way I learn.




