About
The website
This is my personal website, and it also serves as my portfolio. I made this website as a hub for the things I want to share online. Whatever I create — whether it be projects, videos, experiments, or other forms of content — will eventually find its place here. I’m still unsure whether I’ll share my art and/or comics here, but I will definitely be linking the videos I post on platforms like Odysee, Youtube, Twitch, etc. I also want to share tutorials here and on streaming platforms to help my friends and family. Some of them have become interested in the Linux and open-source world, and I’d like to help them explore it more easily. More than anything, I hope this site grows over time alongside me. I want it to become something I can genuinely look back on and feel proud of.
My background
This part feels a little like a flex, which is why I usually downplay it. Still, I think the struggles matter just as much as the achievements. Back then, I had what was considered a “decent” laptop for the time: an i5 8th Gen CPU with 4GB of DDR4 RAM. My older laptops were even worse. Looking back, I’m honestly surprised I managed to play the games I remember playing on those machines. Because of that experience, I think I naturally developed the habit of trying to preserve as many resources as possible. Even today, I still appreciate lightweight software and efficient design. I didn’t fully apply that mindset to development at first, though. Most of what I made were small JavaScript games and experiments without a deep understanding of programming fundamentals. I was mostly learning through curiosity and trial and error. During high school, I didn’t really know where I wanted life to take me. At one point, I wanted to become a YouTuber, but people around me dismissed it as unrealistic and said those dreams would disappear with maturity. They didn’t. Being a jack of all trades also added to my confusion. I explored many different skills and interests, which gave me a broad skill set, but it also meant I didn’t specialize early on. Sometimes it was discouraging watching others become better than me at the things we both cared about. Still, I don’t regret learning so many different things. Because I spent a lot of time alone, I also spent a lot of time thinking, experimenting, and improving my skills. Seeing other people in my family achieve great things motivated me to keep improving myself too. I didn’t want to be left behind. Maybe I should have focused on one path earlier, but looking back, all those different experiences helped shape the way I create today. They’re also the reason I feel like I could eventually become a one-man indie developer if I truly dedicated myself to a project. I still have fond memories of the first JavaScript game I ever made. It’s been so long that I’d probably have to relearn a lot just to recreate it, but that experience was one of the things that pushed me toward programming in the first place. Before entering university, I spent a lot of time reflecting on my life and trying to better understand both myself and the world around me. I was going through a rough period at the time, especially because I felt somewhat disconnected from old classmates and parts of my past. Reading books helped me rebuild my mindset little by little. I wanted to improve my life, so I tried rebuilding myself from the ground up. Maybe that’s also why I enjoy creating things from scratch so much. To me, making projects has never just been about productivity or skill. It’s also been a way to express myself, prove to myself that I can improve, and create things that genuinely feel personal.
My experience with AI
This website and my future projects will either avoid using AI or minimize its usage. During university, I noticed more and more people relying heavily on AI to speed up their work. I also worked on projects and games where AI-generated code was used. One issue I noticed was that some projects became difficult to maintain because the people working on them didn’t fully understand how the code actually worked. I was sometimes able to fix problems after doing additional reading and research, but as projects became more complex, more issues started appearing that were difficult to fully understand or maintain. Although AI can be useful for quickly looking things up, answering simple questions, or speeding up smaller tasks, I don’t think it should be relied upon for projects you intend to maintain long-term. There is value in learning things slowly, understanding them properly, and knowing how the systems you build actually work. That’s why I still recommend reading wiki pages and other learning resources whenever possible. It takes more time, but the understanding you gain tends to stay with you much longer. I also think over-reliance on AI can slowly make people dependent on it if they stop challenging themselves to think through problems on their own. For me personally, some of the most meaningful learning experiences came from building things myself, making mistakes, getting stuck, and figuring things out little by little. That’s how I learned during high school, and it’s probably one of the reasons why I still prefer building things from scratch today. At the end of the day, I simply enjoy creating things, experimenting with ideas, and making projects that genuinely feel like my own.