Sridhar

Sahu

02Origin, 2018 to 2021

I started with

gears, not code.

A diploma first, then a B.Tech in Mechanical Engineering. Load paths, tolerances, failure modes. A system is only as strong as the joint nobody checked.

That habit did not go away when the material changed. It just started pointing at retries, timeouts and the third-party callback that arrives twice.

• Diploma, Mechanical
• B.Tech, Mechanical
• Tolerance stacks
• Failure analysis

05Full Stack Developer, Jan 2025 to present

The

HouseKraft

Spring Boot 3 over dual MySQL and MongoDB, driving CRM, quotations, orders, approvals, payments and support in one platform.

08Now, September 2026

Where my

attention is.

Low-level design

Working through it properly rather than by pattern-matching: object modelling, where the SOLID principles actually earn their cost, and the class-level calls that decide whether a system can still be changed a year later. It is the same question the mechanical work trained me to ask, which is which joint fails first, pointed at code instead of a load path.

DevContext

A self-hosted system that watches what I actually do at a machine, commits, terminal history and which application has focus, and turns it into daily briefings and weekly reports instead of leaving it in scrollback. A local daemon collects, a redaction pass strips keys and tokens before anything is written, and it all lands in SQLite on my own hardware rather than someone else's.A TypeScript monorepo: daemon, API and dashboard over one shared types package, with queue-backed workers and a provider fallback chain that keeps the whole thing running on free tiers. It is not finished and there is nothing to open yet, so it stays here rather than in the shipped chapter, and it moves down there when there is a running deployment to point at.

Exploring opportunities

Open to full-stack and backend roles, and actively talking to teams. If the work in the chapters above is the kind of thing you need built, the email is one scroll down.