January 2026

We often assume that if a doctor prescribes a medication, the only thing we need to worry about is the primary condition it treats. For over two decades, I lived by this assumption. Diagnostic: High Blood Pressure. Prescription: Atenolol 100 and Triamterene-H. Later, Levothyroxine for my thyroid, and eventually Allopurinol and Atorvastatin. I was “managed.” But management isn’t always the same as health. About ten years into my journey with hypertension, I faced a new challenge: high blood glucose. It was a shock. The doctor prescribed Metformin and Gliclazide. For a while, things were under control, especially after I managed to lose a few kilograms and cut sugary foods from my diet. But then, despite my efforts, my numbers spiked again; my A1C hit a staggering 14.2. ...

You have a startup idea, and you have the skills to build it. As a senior developer, you’ve likely spent years mastering the art of turning requirements into robust, scalable systems. But when you decide to build your own company, you realize that the code is the easy part. The hard part is everything around the code: validation, prioritization, distribution, operations, and leadership. This post is a deep dive into the “Execution Gap.” It’s designed for the developer who can build anything but doesn’t know how to make it a reality in the market. We’re going to move past the clichés and look at the gritty details of startup execution, including the legal and management hurdles that often trip up technical founders. ...

In the software world, the “Ship of Theseus” paradox is a daily reality. We replace parts of a system until, eventually, none of the original code remains. But usually, the industry moves toward the “shiny new thing.” At work, we did something that might sound like heresy to some: we migrated our core legacy React applications to Angular. This wasn’t a decision made out of fanboyism. It was a strategic move driven by the need for governance, stability, and long-term maintainability in a high-stakes FinTech environment. I’ll explain the architectural “why” and the pragmatic “how” of moving against the grain. ...

As developers, we often treat our bodies like hardware that just needs caffeine to keep running. We pull late-night sessions, work in dimly lit rooms, and stare at blue-light-emitting screens for 12 hours a day. We optimize our CI/CD pipelines, our database queries, and our bundle sizes, but we often ignore the most critical piece of infrastructure in our stack: our own biology. Our brains aren’t just processors; they are biological organs governed by a 24-hour internal clock known as the circadian rhythm. This rhythm dictates everything from our core body temperature to our hormone production and, most importantly for us, our cognitive performance. ...

There is nothing more frustrating than a device that works perfectly until you try to show someone else. In the world of vintage electronics, these “intermittent faults” are the ultimate test of an engineer’s patience and methodology. Unlike a blown fuse or a charred resistor, an intermittent fault is a ghost. It might be a cold solder joint that only fails when the chassis expands from heat, or a silver-mica capacitor that only leaks under specific humidity levels. These are the problems that don’t show up on a static multimeter test. They require a dynamic, almost adversarial approach to troubleshooting. ...