Hello, I'm Jeremy

Hi! My name is Jeremy Aidan Hernandez Yu!

I have lived in the Philippines all my life, and I am now studying Engineering Physics in Vancouver, Canada.

Why build a personal website?

This website is a collection of my projects, work, and credentials. I made it because I think personal websites are a really big marketing tool for yourself. LinkedIn just doesn’t give it justice. You can list what you have done, but your personality does not really show through, especially when you cannot customise the experience and design (something I do like).

What do you work on?

My background spans both algorithms, digital and physical builds. Right now, I am still trying to find my niche.

How do you learn?

I learn best by immersing myself in a community where I can ask questions. I genuinely think people should not be afraid to ask. A lot of the growth I have had in competitive programming and engineering design teams came from being a complete rookie, asking a lot of questions, and making many, many mistakes.

What are you actually good at?

I think my strength is probably more in execution and forcing myself to learn things that seem completely unrelated to each other. I am not an Olympiad gold medal purist.

How do you get into something completely new?

I think the best way to learn something that feels vastly different from what you already know is to just throw yourself at it. The jump between Olympiad algorithms and physical engineering builds is pretty massive, but I just throw myself into it, learn, ask questions, and slowly build mental models.

What are you looking for next?

Right now, I am probably looking for ways to learn how to build things at a larger scale.

A lot of my software engineering work so far has been on a relatively small scale, with only a few users. Because of that, I could get pretty far by vibecoding and relying on rough algorithmic principles without really needing to learn the deeper software engineering practices that become important when software has to support hundreds or thousands of users.

I think I have a similar gap on the engineering side. A lot of the things I have built have been for relatively small teams or projects meant for only a few people. I know how to make something work, but I have much less experience with what happens when you need to make that same thing reliable, repeatable, and scalable. How do I set up an automated build process for a hardware product? How do I design something that can actually be manufactured repeatedly?

I also want to interact with non-technical people. I want to learn how to figure out what someone actually needs through all the noise, then turn that into something useful owning it end to end.

Where is this going?

I hope this website becomes a record of the things I build, but also a place where I can put down some of my reflections, mistakes, and learnings as I explore new topics.

I am still figuring out where all of this goes. That is kind of the point.

(The one and only) Jeremy Aidan Hernandez Yu