From the Editor's Desk

Q. Let's start with the one on the front of your CV. Fifteen seconds to milliseconds. What was broken?

A. The endpoint that fetched every support ticket. It returned perfectly correct data, and it took ten to fifteen seconds to do it. Nobody had filed a bug, because nobody files a bug that says “this is technically working.” They'd just stopped opening the page.

The fix was in the database, not in the C#. That's usually where it is. I've come round to a rule about this: measure before you theorise, because your instinct about which line is slow is worth roughly nothing.

Q. Your CV is unusually full of numbers for three years in. Is that deliberate?

A. Completely. Forty per cent off response times. Thirty-five per cent better scheduling. Thirty per cent faster student responses at the university. If I can't put a number on it, I'm not sure I improved it — I'm just sure I changed it.

It also keeps me honest. It's very easy to spend a fortnight on a refactor that feels enormous and moves nothing.

Q. So what's on your desk right now?

A. A management system in .NET Core that runs employees, clients, inventory, scheduling and leave for a whole organisation. Scheduling efficiency is up about a third since it went in.

I built the JWT authentication and role-based access control underneath it, and a real-time chat layer on SignalR — because the moment people can see each other's schedules, the next thing they want is to argue about them without leaving the page. Enrolment and onboarding run as separate microservices, with the notifications and document handling automated.

Q. You put rate limiting on Redis and Lambda instead of a middleware. Why the ceremony?

A. Because it wasn't really rate limiting, it was billing. Every customer sits on a subscription tier, and the tier decides what they're allowed to consume. That's a number that has to be right, has to be fast, and has to survive a deploy.

Redis holds the counters, Lambda does the work off the request path. The API stays boring, which is the highest compliment I have for an API.

Q. Rising Star Award. What actually earned it?

A. The citation says performance, initiative and project contribution. The honest version is that I kept volunteering for the parts nobody wanted — the slow endpoint, the deployment nobody could reproduce, the billing edge case.

That work is unfashionable and it is where all the leverage is. You fix the fifteen-second page and a hundred people quietly get their afternoon back.

Q. Where did the foundations come from?

A. Maharaja Sayajirao University in Baroda — B.E. in Computer Science and Engineering, 2019 to 2023, 8.28 GPA. My final semester overlapped with my first internship, which is roughly when the theory started earning its keep.

My first real build was there too: a web application that cut student response time by about 30%. Angular.js on the front, .NET Core and SQL Server behind it. Most of that project was conversations with university staff, not code — which turned out to be the actual lesson.

Q. Right. The real question. What happens after hours?

A. Games, anime and manga, in whatever order the week allows. I like the ones that trust you to work it out — a mechanic nobody explains, a plot thread planted forty chapters before it pays off.

It's the same pleasure I get from a codebase where someone left the seams visible on purpose. A good boss fight and a good system are the same object: opaque until you find the pattern, then obvious forever.

Q. Last one. What are you after?

A. Something with a hard part in it. I'm not precious about the stack — I'm precious about the problem being real. If you've got a page nobody opens any more because it takes fifteen seconds, the Classifieds are two pages back.