-
The Teams webhook that became the most important endpoint
We built a Lambda that posts CloudWatch alarm summaries to a Teams channel. Took half a day. It became the first thing the on-call engineer checks in the morning. Sometimes the highest-ROI engineering is a webhook and a well-formatted message.
-
At what scale does serverless stop being the right answer?
I keep telling teams that serverless is good for bursty, unpredictable workloads. But where is the real inflection point? At 10,000 RPS? At sustained constant load? I have heard very different answers from very credible people and I still do not have mine.
-
How do you actually measure ‘code quality’?
Code coverage? Cyclomatic complexity? Pull request review time? I have used all of these. None of them capture the thing I actually care about: can a new engineer understand and safely modify this code in six months? I am still looking for a metric that gets close.
-
Is event-driven architecture making distributed systems harder to reason about?
EventBridge gives you beautiful decoupling. But ‘who published this event and why did it trigger that Lambda?’ becomes genuinely hard to answer in a post-mortem. I wonder if we are solving coupling by creating complexity of a different kind.
-
What does ‘senior’ actually mean in engineering?
I have seen senior engineers who write brilliant code but cannot bring a junior along. And I have seen others who write mediocre code but ship teams that consistently deliver. Which one is more valuable? I think I know the answer, but it makes me uncomfortable.
-
Will AI write the boilerplate, or will it write the architecture?
Right now AI is great at plumbing — CRUD endpoints, test scaffolding, repetitive config. But the hard decisions — what to build, how services should talk, what to NOT build — still feel very human. I wonder how long that distinction holds.
-
Demon or Revolutionary?
A thought keeps returning to my mind— a quiet conflict that refuses to settle. If today you were to place a revolver in my hand, perhaps it would awaken a demon within me. But if that same revolver had been given to me before 1947, it might not have awakened a demon, but instead given…
-
Linux Filesystem Hierarchy
Windows divides data into multiple drives (C:, D:, etc.), Linux follows a structured, single-rooter system. Root directory (/) It contains all essential system directories, configuration files, and user data. Everything in Linux is a file, whether it’s a text document, a directory, a hardware device, or a running process. This directory stores essential system executables…
-
The Pen Was Always in Our Hands
Maybe destiny was never written. Maybe we are writing it. For generations people have said that everything in life is already written. In India we grow up hearing the phrase: “jo likha hai, wo hoga” — what is written will happen. The idea is comforting.It suggests that somewhere, beyond our understanding, life follows a script…
-
In JavaScript, Variables Don’t Have Types — Values Do
While studying JavaScript deeply, I came across an idea explained by Kyle Simpson in You Don’t Know JS: Variables don’t have types. Values have types. At first, this statement feels counter-intuitive, especially if you come from languages like Java, C++, or TypeScript. But understanding this concept is crucial for truly grasping how JavaScript works. Let’s…
Got any book recommendations?