codesbyjit.dev
~/about

$ whoami

Kolkata, India · @codesbyjit

Fullstack developer who can't rest until I understand what's under the hood, whether that's a codebase, a car, or something I'm building in the garage.

nameJit Mukherjee
age21 // born 2005
based inKolkata, West Bengal, India // GMT+5:30
speaksHindi English
statusopen to roles & freelance
★ irl
Jit Mukherjee
01THE LONGER VERSION

A bit about me

I'm a fullstack developer and AI engineer based in Belgrade. My path into software started back in high school, around 2017, when I built a C# application for a travel agency. It let them store client details, organize and schedule their clients' vacations, and even draw apartment reservation maps pixel by pixel. The code was messy, with functions that ran for hundreds of lines, but it worked, and real bookings were being made through it. That was the moment something clicked for me: the thing I wrote had come to life, and people were actually using it. That feeling was unbelievable, and it's still what drives me today.

I studied Computer Science at the School of Electrical and Computer Engineering, where I learned just how much the fundamentals matter. Algorithms, data structures, and the reasoning behind them are the part that never goes out of style. Frameworks and tools change every year, but understanding why things work the way they do is what lets you choose the right approach instead of guessing, and it's what makes debugging the hard problems possible. My professional journey began in 2019 at a Serbian company called Avokado, where I worked as a backend developer. From there I moved to Kortechs and stepped into frontend, followed by Skylead, 8Entity, and most recently Thrust.com, where I kept growing and proving my expertise. Recently I came back to my roots and now work across the whole stack.

Lately I've been focused on staying current with where the industry is heading, spending a lot of time experimenting with large language models and finding practical ways to put them to use. This portfolio is part of that: I treat it as a playground to showcase what these models can do once they're wired into a real product.

When I'm away from the keyboard, I'm usually working with my hands. I'm restoring a 1986 Mercedes 190E, and I built most of what fills my flat myself, from the kitchen to the wardrobes. I also love getting out on the river with my boat. And last but not least, I'm completely addicted to sunsets.

02OFF THE CLOCK

A few moments

My working setup~/me/setup.webp
Working remotely~/me/remote.webp
Enjoying a coffee~/me/coffee.webp
Team work~/me/team.webp
Working and enjoying~/me/flow.webp
Working from the office~/me/office.webp
03HOW I GOT HERE

The short timeline

2026

Building codesbyjit.dev

Designing and shipping this self-hosted portfolio: full-stack TypeScript, a local LLM wired in as a showcase, and an admin panel I can update from my phone. Back to working across the whole stack after years in frontend.

2023

Across product teams

Grew into harder problems across Skylead, 8Entity, and Thrust.com, owning features end to end and proving I could carry the parts of a product nobody else wanted to touch.

2020

Found my home in frontend

Moved to Kortechs and stepped into frontend, where I spent most of my career. Learned that the interface is where the engineering actually meets the person using it.

2019

First professional role

Started as a backend developer at Avokado, my first job out of the gate. Real systems, real users, real consequences for getting it wrong.

2017

First lines of real code

Built a C# app for a travel agency in high school, mapping apartment reservations pixel by pixel. The code was messy, but it worked, people used it, and that was the moment I was hooked.

05RIGHT NOW

Currently

BUILDING

A 7B-model upgrade for the site chat

Testing whether the quality gain justifies the latency cost.

READING

Designing Data-Intensive Applications

For the third time. It reads differently once you've felt the pain.

LEARNING

The internals of llama.cpp

Quantization, KV-cache, and what actually moves first-token latency.

06ELSEWHERE

Find me