About
I took my first real steps into computing the moment I got my hands on a keyboard. Something about the directness of it: write a command, get a result. Felt unlike anything else.
I'm someone who needs to understand how things actually work. Not just use them, understand them. That instinct has shaped everything: how I read, how I learn, what I build.
Outside the screen, I'm drawn to things that are quiet and deliberate. I think clearly when I'm away from noise. Most of my best ideas have come from doing nothing in particular.
Education
At some point early on I discovered a world made of silicon and binary numbers, and it clicked immediately. I typed my first programs in a dim console and never really stopped.
I am currently pursuing a B.Tech in Computer Science at KL University (2022–2026). The curriculum gave me the foundations: algorithms, data structures, operating systems, networks. But the real education has been in the hours outside class: reading source code, breaking things to understand them.
I developed a specific interest in systems programming and a preference for code that is correct, fast, and small. That preference has only grown stronger over time.
Work
My work lives close to the machine. C, C++, Rust, Python. These are the tools I reach for first. Performance matters, memory matters, determinism matters.
I’ve done some projects in Rust, like a LAN Chat application. I also built an AI Traffic Management System in Python, which is used to set traffic times based on vehicle density. I’ve also worked on some applications using JS frameworks like React.
Beyond that: REST APIs with Spring Boot, a React frontend for workshop management, a C++ image classifier on MNIST, a Hibernate-backed feedback system. Different layers of the stack, all useful to understand.
Recently I’ve been building some small applications in Kotlin, like a weather application using open APIs that are freely available.
Also apart from that, my main goal is to optimize performance issues, so from that point of view I implemented some microservices in my MERN stack applications, using GO for concurrency and lightweight services.
I’ve also worked on a few small projects, including a book tracker built with Ruby and a weather application developed using Kotlin. Much of the implementation was done through an experimental, hands-on approach.
I'm currently learning about some CPU architectures, how systemd works, and some OS-related stuff, especially at the systems level.
I’ve worked with a bunch of languages, but most of what I actually get done is in C, C++, Rust, and Go.