hey, i am ufraan

curious about systems and architecture

i build backend systems. the servers, databases, and APIs that handle the actual work. currently studying computer science at LIET, i spend most of my time learning about how to make systems faster, more reliable, and easier to maintain when something inevitably breaks.

i started coding in high school and spent time with graphic design before realizing i preferred working on problems you can't see. what pulls me in: optimizing slow queries, understanding why systems collapse under load, figuring out caching strategies, and how services should communicate. i work mainly in Go.

right now, i'm learning by building; running into problems with distributed systems and database design, then figuring out why certain architectural choices actually matter. finding out where my knowledge gaps are by hitting them directly.