About Me
Hey! I’m Nirav. I build software and hardware products. I’m interested in solving deep, complex technology problems across the whole stack.
I work on the extended stack
With the end goal of making polished, simple products to improve and decorate the lives of people, I don’t restrict myself to any particular technology stack or language.
That said, I do prefer certain stacks to others. For systems work, C++ has been my go-to language. I wrote a compiler and implemented the huffman1 compression algorithm in C++, and all my embedded work is in C++. Recently I also wrote the MP3 player’s main application in C++. I still think it is the coolest language, and I don’t get to use it enough.
I also love pure vanilla JavaScript, weird as it is. I wrote a game engine and a couple of games in JavaScript. Give me JavaScript with a DOM tree and I’ll invent anything. It is really that simple and powerful. Consider this handcrafted block of code for example. I use TypeScript for professional work and client projects. For production backend work, Next.js has been my go-to, but I’ll always be partial to PocketBase for personal projects. It really is the best.
I build electronic devices
I came up with a concept that I later found better articulated and popularized by Gunpei Yokoi as “Lateral Thinking with Withered Technology”. I prefer to spend time extracting the most value and quality out of a mature technology, and try to apply it in creative ways to build fun and useful things. Hardware is different from software in that every new feature adds to the unit cost as well as the NRE cost. So hardware optimization is a lot different from and interesting than software optimization. A single line of code can be the difference between the user having to change their batteries every month vs every year. A set of vents on the enclosure can be the difference between a five-year service life vs ten. A display technology choice can be the difference between charging a device every day vs running off a single CR2016 every 5 years. This is the kind of detail that excites me.
When possible, I try to design things so they can run off a single small non-rechargeable battery for years. On microcontrollers, I prefer WCH chips (CH32V005 and CH572). They are good all-rounders, are easily and widely available, and cost very little. Their sleep-mode power consumption is not particularly good though. So when I need to optimize for that (say, running on a CR2016), the STM32L series is my go-to. I also design, prototype and fabricate enclosures to go with the circuits.
I find breakout boards, development boards, breadboards and the tangle of jumpers extremely inelegant. Fine for tests, experiments and jigs to write firmware in, but definitely nothing I’d feel proud publishing or showing off. A good project must be self-contained and robust. You should be able to hand it off to a reckless friend casually without any concerns for their or the product’s safety. If they overcharge it, leave it inside their car in the sun, insert the battery wrong side up, drop it or use it in any manner a curious monkey might, it should still function gratefully.
I strive for simplicity
Simplicity is not the absence of complexity, but the mastery of it. It is important that I work on the complicated details so the end user can enjoy a simple interface. Simplicity is not always pretty, minimalist interfaces and sleek aluminium. It comes from giving people crisp, robust mental models and from not breaking unspoken promises. It comes from empathetic understanding of my audience.
Thoughts on LLMs/AI
I acknowledge the moral and societal problems with how LLMs were created and how this technology is being speedrun with wanton abandon. At the same time, I can’t deny the value it adds to engineering and development. I use LLMs for work.
I don’t use LLMs for communication. Every blog post, every message, and every email from me is deliberate and my own. I don’t use LLMs when I’m learning. This includes most personal projects. When I do use LLMs, it is to be more productive and to explore ideas. But I am still responsible for every bit of code and media posted, and it reflects on me as much as any code I’d have written myself.
Reading
The Grapes of Wrath, One Hundred Years of Solitude, Absalom, Absalom!
What else…
I studied Computer Engineering at WRC, Pokhara. There, I helped start Yarsa Tech as a founding engineer and release its first two products: Nizi Power and eSpeaker. I work part-time at SignalWire with the DevEx team to improve the documentation of its diverse, complex product base. I refine my craft by working on multi-domain personal projects and by taking on suitably interesting client projects.
Footnotes
-
“David, I guess your name has finally entered the language.” Scientific American ↑