Full-Stack Developer & CS Lecturer

   

I am a full-stack developer, currently splitting my time between building software and teaching computer science to undergrads.

My engineering philosophy is simple: build systems that survive the real world. I care less about chasing the newest framework hype and more about writing code that doesn't break when an external API goes down. I focus on pragmatic problem-solving, clean data flow, and building fallbacks for when things inevitably fail.

Chronithm is my current focus. It's a tool built to solve a problem I actually have: tracking developer work across different platforms is a fragmented mess.

Instead of writing manual standup updates, Chronithm pulls in data from GitHub webhooks and Jira, normalizes it in MongoDB, and uses AI to summarize it into clean daily reports.

How it works under the hood:

• Dual Outputs: The API uses custom prompt routing to generate two different summaries one highly technical report for developers, and one jargon free update for clients.
• Graceful Degradation: Live AI demos fail. If the Gemini API hits a rate limit or a billing block, the server doesn't crash. It catches the error and safely falls back to returning the raw, formatted timeline logs.
• Separation of Concerns: A React frontend on Vercel, a Node/Express backend on Heroku, and a unified database structure to handle vastly different incoming webhook payloads.

Whether it's discussing systems architecture, full-stack roles, or figuring out how to survive bad API documentation my inbox is open.