Robotics / AI / Systems
Selected work across open robotics, physical AI, healthcare platforms, and retrieval systems—built by Alok Didde.
01 / Selected work
Systems are most interesting at their edges: where software meets hardware, models meet messy data, and prototypes meet actual use.
A framework for moving from an idea to working hardware without rebuilding the same infrastructure every time.
The aim is practical: composable software, firmware, and hardware interfaces that are understandable enough to change—and solid enough to build on.
An autonomous agricultural platform combining spatial reconstruction, visual pest detection, and robotic-arm control.
Gaussian Splatting informed navigation, CNNs handled pest detection, and forward/inverse kinematics drove precise manipulation.
A retrieval approach that uses Monte Carlo exploration to search a corpus rather than depending entirely on vector similarity.
In early experiments it reached roughly 80% recall on the target task, compared with under 20% for the embedding baseline. The interesting part is not the number—it is the search behaviour behind it.
PCBoo lets coding agents author circuit boards as composable TypeScript, then makes them show their working.
Deterministic builds, structured diagnostics, local inspection, and separate readiness statuses keep a plausible-looking board from quietly becoming a very expensive coaster.
Read the project storyClinical platforms, remote patient monitoring, real-time communication, claims workflows, and AI-assisted document systems.
Work across startups and scaled healthcare companies shaped how I think about reliability: the difficult part is rarely the happy path.
More things shipped
Smaller in footprint, complete enough to use.
A TypeScript memory engine combining BM25, embeddings, recency, and feedback with per-query adaptive weighting and an L1/L2/L3 memory hierarchy.
A working assistant for Indian micro-businesses: transaction capture, cash-flow forecasts, payroll, collections, and proactive alerts through a familiar interface.
02 / Working questions
Not declarations. Questions worth keeping open long enough to build something around them.
The useful kind of boring: predictable, inspectable, and reusable.
Search may need strategies, memory, and backtracking—not only a better embedding.
Documentation and interfaces matter as much as a downloadable CAD file.
A short signal