About Raktim Ranjit: software engineer and founder of NodeDR Infotech

The questions that kept me interested were rarely confined to one tool. A working interface led me to ask where its data lived; a working API led me to ask what happened when the network disappeared; a useful feature led me to ask who was allowed to use it and how it would be maintained. Following those questions pulled me from application code into databases, Linux, networking and infrastructure.

That curiosity now has a practical outlet. I build software for people whose work is physical and time-sensitive: a retailer billing a customer, a kitchen receiving an order, a pharmacist tracking an expiring batch, a site engineer requesting material. In those settings the whole system matters more than a polished screen on its own.

I start with the workflow. Who creates a record, who changes it, and what must remain true when several things happen at once? In Rechvix, finalising an invoice touches stock, tax, accounting and numbering in one transaction. In OrderRestro, the till, table map and kitchen display need a common live picture of an order. Those requirements lead the architecture; the framework comes later.

I prefer decisions that can be explained. Rechvix uses a modular monolith because invoice finalisation needs one database transaction. OrderRestro uses WebSockets where staff need immediate updates. KinetiRx uses server-sent events for simpler one-way live sync. The point is to choose the smallest mechanism that respects the real constraint.

I also write down what a decision costs. A stock balance maintained in application code needs a restore check against its movement ledger. A self-hosted product gives its owner control and makes backups their responsibility. The case studies and articles include those trade-offs, because a system is easier to trust when its limits are visible.

I founded NODEDR INFOTECH PRIVATE LIMITED to build useful software and engineering systems around real operational problems. Its products cover retail, restaurants, pharmacy, workforce operations, accounting, form infrastructure and construction procurement. The common thread is that each product has to fit a process people already depend on.

NodeDR is the company and the home of those products. This site is my own record of the work behind them: where a data model came from, why a permission boundary exists, what went wrong during deployment and what I would improve. The NodeDR website is where to find product details and company enquiries.

I learn by running the systems I write. I use Proxmox and TrueNAS for my own services and experiments, and I package products for Docker, Windows, Debian and CasaOS. A deployment on an unfamiliar machine exposes assumptions a development laptop hides: an empty bind mount, a cookie flag wrong for the origin, or a container that still has yesterday's environment variables.

When something takes an afternoon to understand, I turn it into a short note or an architecture decision record. I read the code that enforces a principle instead of assuming the README proves it. That is how a Rechvix review uncovered thirteen tenant lookups that relied on row-level security alone; I added an organisation filter to each query and documented why.

My technical writing begins with a specific piece of work: an implementation choice, a production mistake, a test or a trade-off. I want a reader to leave with a decision they can apply, and enough context to know when it does not apply. The longer pieces are in Blog; small observations are in Notes.

I also write fiction. Proof of Absence is a psychological thriller about memory and the confidence we place in what we remember. Part Two: Borrowed Lives continues that story. Both books can be read online or downloaded. Fiction gives me a different kind of space for the same habit of close observation.

Photography slows me down. It asks me to notice light, framing and the details I would miss if I were in a hurry. The gallery brings together portraits, birds, plants and places I have visited. I choose photographs for the light, moment or detail that made me stop and look.

I am working on OrderRestro and Rechvix, writing from the decisions in both, and improving this site as a useful public archive. The dated, shorter update is on Now. For a specific project, start with Work; for a technical topic, start with Expertise.