I made a website. You're on it.
I've been meaning to do this for a while. I keep learning things and then losing them. The fix, apparently, is to write them down somewhere. So here we are.
A bit about me
I'm a CS student. I like running, watching anime, playing Minecraft, and building things. That's most of it.
Programming started in high school. C, python, nothing serious. Then I got into college and it slowly became the main thing. I'm not sure when that happened. One day I was doing it for a grade, and then I wasn't, and I was still doing it.
This year I got into computer vision. object detection, tracking, training models on actual data. It stopped feeling like coursework. That was new.
What I built this year
My team and I finished a computer vision project earlier this year. Tracking objects in video, counting them across user-defined regions, maintaining IDs when things get crowded. We used YOLOv8 and ByteTrack.
Getting a model to run on video was the easy part. Making it useful, and fixing all the bugs, took much longer. I spent 3 hours on a Stackoverflow thread about ByteTrack integration. Left with nothing. I also asked AI. It gave me an answer that looked right. It wasn't. I tried it anyway. Still broken. Fixed it eventually by reading the source code, which I should have done first. AI is supposed to be better than me at this. Somehow I was the one who fixed it.
We finished it. That felt good. I didn't expect it to feel that good. I also learned a lot. The part I mainly built is on GitHub if you want to look.
The git situation
Before I knew git existed, I used to save my code in Apple notes. Every version that worked got its own note. Then a better version that worked got another note. I had a lot of notes.
Then I found git and thought it was the same thing, just a hard drive that lives online. You push your files up so they're safe. That's it.
I didn't think about history, or why the message mattered. So every commit was just update. Something changed, I saved it, I moved on.
I understand it better now. But I think there's also something honest about update. I don't stop to explain myself in the moment. I build, I push, I keep going. The work is the record. I know it is a bad habit. I just haven't fixed it yet.
About this site
I watched some tutorials. Got it running. Made adjustments. If something looks off, that's why.
I was deliberate about one thing. Dark. The whole site is dark, and I want it to stay that way. I spend most of my time in dark terminals and dark code editors. Light mode feels like someone turned the lights on while I was thinking. I didn't want this to feel like a portfolio optimized for a recruiter who will spend 12 seconds on it. I wanted it to feel like a place I made and a place I live.
Minimal for the same reason. Nothing that doesn't need to be there. If I'm putting words somewhere, the words should be the thing.
There is one exception. I spent a week building a perfect snake AI for the main page. Nobody asked for it. It's not useful. It just looks cool, so I put it there. I think that's a valid reason.
What I'm thinking about
AI is moving fast. It fixes some of the bugs I run into. Not all of them, but some. That's already useful.
What I keep thinking about is what comes after that. Right now it helps. Someday it might just build the whole thing. I don't know when, or what that means for me.
Should I be scared of that. Amazed. Or both. I've not decided yet.
I'm 21. I have time to find out.
If you're reading this, hi. I'm figuring it out.