Distributed Veto Power (and the Death of Speed) A one-day feature turned into eight because too many people had the power to slow it down. Speed isn’t lost in engineering. It leaks through organizational cracks.
Why Being Better Isn't Good Enough Are you building a breakthrough business, or just a slightly better feature? Before you write a single line of code, use this two-step framework to validate your potential.
Think Outside the Product Why did Zoom beat Skype? Why is CRED a status game, not a bill payment app?
Why the "Decentralized" Internet Keeps Breaking The internet feels global and unbreakable, but it’s quietly centralized behind a handful of infrastructure giants. When one of them stumbles, the modern web forgets how to find itself.
The Cost of SQL Habits on MongoDB Infrastructure Clusters get bigger, queries get slower, and everyone blames MongoDB. But the real culprit could be schema design built on relational intuition. Here’s why SQL habits are costly, and how to retrain teams to think natively in documents.
The Silent Rewrite of Software Engineering The ground beneath software engineering is shifting, and the teams moving fastest aren’t rejecting LLMs, they’re weaponising them.
When the winds of change blow Hierarchy works well when conditions are stable and problems are known. During transitions, its limits become visible. What replaces rigid structure is not chaos, but ownership, with decision making moving toward those closest to the work.
Why Rewrites Fail and Ugly Code Survives Messiest parts of your codebase are usually the ones holding your entire business together. Rewriting them might be the fastest path to losing customers.
Building in a World Where Nothing Lasts Startups are built on impermanence. Teams shift, markets vanish, products fade. Mujo isn’t a curse, it’s the truth. Embracing impermanence in startups turns fear into momentum and chaos into clarity.
Project Overload: How Startups Burn Out Their Best People Startups think they're getting more done by putting people on multiple projects. In reality, they're paying a hidden tax: context switching, diluted focus, and slow motion burnout.
The Art of Breaking Things on Purpose Instead of hoping systems don’t fail, what if you break them on purpose? To find weak spots before the world does. Netflix, Uber, and Google turned Chaos Engineering into a discipline. Here’s why it matters, how it works, and why it’s the best way to build resilient systems.
The Illusion of Having It Modern ambition is no longer about meaning - it's about optics. Good food, luxury travel, and branded things have replaced curiosity, craft, and contribution. We didn't plan this shift. But we're all living inside it.
Why Building a Startup Is Like Compound Interest The real magic isn't in your first win. It's in staying alive long enough for small wins to snowball.
Black Mirror: Designed to Distract When product design is too optimized for conversions, it stops being helpful and starts being manipulative. From Zepto's billing screen to sneaky free trials and dark patterns, users are catching on.
How My Mind Learned to Ship I never set out to learn product. I just couldn’t ignore when something felt broken. From obsessing over icons to running full-funnel experiments at scale, this is how my mind learned to ship: not from frameworks, but from flow, instinct, and ownership.
Hiring Is Broken. Let us Not Be. Hiring is hard. But it doesn't have to be heartless. After hundreds of interviews, here are some raw, personal thoughts about how we hire, who we overlook, and what we forget.
Structured Logging Explained: Levels, Examples, and Best Practices Debugging with bad logs is like investigating a crime without CCTV. Structured logs give you the clarity and evidence you need when systems misbehave.
What is API Observability? Logs, Metrics, Traces Explained The hardest outages aren't when systems go down-they're when you have no idea what's happening inside. API observability is how you make your system explorable in real time.
What is API Reliability? Building APIs without a reliability layer is like running a city with no backup generators. The lights stay on until the first power cut.
Running Lean and Building Faster Most startups don’t fail because they couldn’t build. They fail because they built too much, too early, and in the wrong direction. This is how I learned to stay lean, move fast, and build only what real user behavior actually justifies.