Om Malik wrote his own obit at 60. Read it before you ship another feature.

What happened

On June 24, 2026, Om Malik — founder of GigaOm, partner at True Ventures, and arguably the person who proved tech blogging could be a career rather than a hobby — published a post titled simply "1966–2026" on om.co. It's his own obituary, written in the first person, dated as if he were already gone. He isn't. He turned 60 this year, survived a heart attack in 2011, and is using the bracketed dates as a deliberate provocation rather than a medical disclosure.

The piece is short by Malik's standards — under 1,500 words — and reads less like a memento mori than a closing argument. He recounts arriving in the U.S. from India with a few hundred dollars, the Forbes years, the GigaOm rise and 2015 collapse, the pivot to venture capital, and the slow recalibration after his cardiac event. The thesis isn't "I'm dying," it's "I've been writing about other people's exits for 25 years and never drafted my own." As of this morning, the HN thread sits at 787 points with the top comments split between people who knew Malik personally in the early-2000s blog era and engineers in their thirties asking, uncomfortably, why this is landing so hard.

It's landing hard because the genre is new. Tech founders write Medium posts when they sell. They write apology threads when they get fired. They write "lessons learned" essays when they pivot. Almost none of them write the document that summarizes the whole arc while they can still edit it.

Why it matters

Malik occupies a specific historical seat. He was paid to blog about technology before "creator economy" was a phrase. He covered the broadband buildout, the mobile transition, the cloud wars, and the first AI cycle — and then he did the thing almost no first-wave blogger did, which was successfully transition into capital allocation at True. He has watched, from extremely close range, what happens to founders who treat the next round, the next launch, the next IPO as the thing that will finally make the deferred life affordable.

The obituary form is doing something the standard "reflections at 60" essay can't. By collapsing his own timeline into a closed interval, Malik forces the reader to do the same arithmetic on themselves — and the answer is uncomfortable for anyone whose calendar is full of sprints labeled Q3. The HN reaction confirms it. The highest-voted comment isn't about Malik at all; it's a developer at a late-stage startup admitting they haven't taken a real vacation in four years because "the migration" is always six weeks out. The second-highest is shorter: "My dad died at 61. I read this twice."

There's also a media-history angle worth naming. The first generation of tech bloggers — Malik, Arrington, Calacanis, Scoble, Winer — are now in their late fifties and sixties. Arrington sold TechCrunch and largely vanished from public writing. Calacanis pivoted to angel investing and podcasting. Scoble became, charitably, a complicated figure. Winer kept writing and kept being right about RSS. Malik is the first of that cohort to write his own ending while still capable of revising it, and the form is going to get copied — badly, mostly, but copied. Expect a wave of Substack obituaries by Christmas. Most will be cringe. A few will be honest.

The deeper signal for a technical audience is about feedback loops. Engineers are trained on tight ones — CI runs, error budgets, p99 latencies, weekly retros. Life decisions run on loops measured in years or decades, and the gradient is invisible until it isn't. Malik is essentially publishing a synthetic long-horizon retrospective and inviting you to backfill your own. That's a debugging technique, not a self-help genre.

What this means for your stack

Three concrete reframes, none of them sentimental.

First, calendar the non-urgent. The engineers who survive twenty-year careers without burning out or burning down relationships have one thing in common: the non-work commitments — kids' recitals, parents' birthdays, the annual trip with the college friends — are on the calendar before the sprint planning, not after. Malik's piece, read literally, is a recurring-event recommendation with a 60-year recurrence interval and a hard stop.

Second, audit your indispensability theater. The reason most senior engineers don't take the sabbatical, the parental leave, or the four-week trip is the belief that the system will collapse without them. The honest test is to look at the last time you were genuinely offline for two weeks and count how many of the "only I can do this" tasks actually broke versus got reassigned and quietly handled. Malik built GigaOm into a 70-person operation and then watched it shut down in 2015 anyway. The org survives or it doesn't, and your weekend availability is rarely the deciding variable.

Third, write the doc now. Not the obituary — though if you want to, the form is open-source as of this week. The thing Malik is implicitly recommending is the version of an engineering design doc applied to a life: what are you actually optimizing for, what are the constraints, what would the post-mortem say if the project shipped tomorrow. Most of us have never written that document. We've written hundreds for systems that will be deprecated in three years.

Looking ahead

Malik will, statistically and hopefully, be around for the 2036 update. The interesting question is whether his post becomes a one-off curiosity or the start of a small genre — senior practitioners publishing their own framing while the framing is still theirs to write. The infrastructure exists: every developer reading this has a personal domain, a static site generator, and the technical capacity to publish a 1,500-word document in under an hour. The bottleneck has never been the tooling. It's been the willingness to look directly at the interval and put dates on both ends.