Uday Kiriti / About

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 piece of code, get a result. Felt unlike anything else.

I'm someone who needs to understand how things actually work. I do not want to just use them; I want to understand them. That instinct has shaped everything: how I read, how I learn.

I may not always enjoy the final product of software, but I enjoy the process.

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

Early on, I discovered a world made of silicon and binary numbers, and it clicked immediately. I typed my first programs into 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.

Philosophy

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 worked with a bunch of languages, but most of what I actually get done is in C, C++, Rust, and Go.

Projects

I’ve worked on some projects in Rust, such as a LAN chat application. I also built an AI Traffic Management System in Python, which adjusts traffic signal timing based on vehicle density. I’ve also worked on applications using JavaScript 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.

Experiments

Apart from that, one of my main goals is to improve performance, so 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 in Ruby and a weather application in Kotlin. Much of the implementation came from an experimental, hands-on approach.

Recently I’ve been building small applications in Kotlin, such as a weather application that uses publicly available APIs.

Learning

I'm currently learning about CPU architectures, how systemd works, and other operating-system concepts, especially at the systems level and some math.