The editorial frames Malik's post not as morbid reflection but as an editorial audit: deciding in advance what the lede would be if it weren't his to write. It draws an explicit parallel to Gary Klein's premortem technique and Bezos's regret minimization framework, arguing the inversion strips away everything you can't honestly defend as having mattered.
The piece emphasizes that Malik isn't a random blogger doing a Stoic exercise for clicks — he founded GigaOm in 2006 and survived a near-fatal heart attack in 2008 that he has written about with unusual clarity. That résumé transforms the framing from morbid to editorial, making the act of drafting an obituary the real story rather than its contents.
The editorial notes that postmortems on outages are standard in operational engineering, but premortems on launches still aren't — despite NASA's adoption of the technique. A postmortem tells you what went wrong; a premortem tells you what you already know is going to go wrong but can't admit yet, and that inversion is the entire point of the discipline.
By submitting the post to Hacker News where it accumulated 1,110+ points and the #1 slot within hours, minimaxir surfaced it to an engineering audience that recognized the premortem logic without needing it explained. The voting pattern itself is evidence that the technical community sees this as a discipline worth examining, not just a personal essay.
On June 24, Om Malik published a post on om.co titled simply '1966–2026'. The dashes do the work the headline doesn't: it's a span of years, his years, written in the past tense while he is alive. The piece reads as his own obituary. Hacker News voted it to #1 within hours; at time of writing it sits at 1,110+ points.
Malik is not a random blogger doing a Stoic exercise for clicks. He founded GigaOm in 2006, was one of the first people on the planet to be taken seriously as a tech journalist while operating from a blog, and survived a near-fatal heart attack in 2008 that he has written about with unusual clarity ever since. When someone with that résumé writes their own ending, the framing isn't morbid. It's editorial.
The post itself doesn't read as a farewell. It reads as an audit — a writer deciding, in advance, what the lede would be if it weren't his to write. That decision is the whole story. The actual contents of the obituary matter less than the act of having drafted one.
Engineers already have a vocabulary for this. It's called a premortem, formalized by decision researcher Gary Klein in a 2007 Harvard Business Review piece. The exercise: before a project starts, the team assumes it has failed catastrophically and works backward to explain why. NASA adopted the technique. So did large swaths of operational engineering culture, where postmortems on outages are now standard but premortems on launches still aren't.
The inversion is the entire point. A postmortem tells you what went wrong; a premortem tells you what you already know is going to go wrong but can't admit yet. The same asymmetry applies to a life. Writing your obituary while alive isn't memento mori cosplay — it's a forcing function that strips out everything you can't honestly defend as having mattered.
Jeff Bezos's 'regret minimization framework,' which he credits with the decision to start Amazon, is the same exercise in a different costume: project yourself to 80, look back, decide. The Stoics had it as a daily practice. What Malik did differently is he published his. The act of publishing changes the discipline — once your draft is public, you can't quietly rewrite history. The community reaction on HN bears this out: the top comments aren't grief, they're recognition. Engineers, founders, and writers all immediately understand what he just did, because they've all been tempted to do it and haven't.
What Malik chose to include is its own commentary on what survives in tech writing once the metrics stop counting. GigaOm. The 2008 heart attack. The conviction, in the mid-2000s, that blogs would be a real medium and not a hobby. What's absent is more telling: no viral hit list, no follower count milestones, no podcast deals, no Substack numbers. The currency of modern tech writing is conspicuously not in the ledger. A 60-year-old writer auditing his own life left out exactly the things a 30-year-old writer would optimize for.
The technique transfers cleanly, and most teams don't use it.
Write the postmortem before you ship. Pick a date six months out. Assume the project failed. In the voice of an honest peer, write the retro. The failures you can already name aren't predictions — they're commitments you haven't made yet. If you can write a credible failure narrative today, you have a decision to make today, not in Q4. This is the Klein premortem, and it costs an hour.
Write the README before the code. Same shape. If you can't describe the finished product in a way a user would understand and want, the architecture conversation is premature. Most internal tools fail this test; most successful open-source projects pass it because the README is the recruiting pitch and gets written first by necessity.
Write the obituary of the side project. Not the roadmap, the obituary. 'X was a tool for Y that ran from 2026 to 2027 before being abandoned. It was used by Z people. The author moved on because…' If that paragraph is depressing, you have your answer. If it's defensible, you have a real project. The exercise compresses a year of clarity into ten minutes.
Write your CV from 2031. Not aspirationally — write the honest version. The roles you'd have taken, the decisions you'd have made, the technical bets that would have paid off. The gap between that document and your current trajectory is the only career-planning artifact that actually changes behavior. Performance review templates do not produce this.
The genre will spread because it's good, and because the demographics of senior tech are increasingly people in their 40s and 50s who have outlived the assumption that the next thing will always show up. Watch for the 1985–2055 posts from engineers who are tired of writing roadmaps and want to write something that will hold up. Malik didn't invent this — Bezos, Klein, and Aurelius got there first — but he made the public version legible to a technical audience that respects him. That's the shift. The premortem just moved from operations runbook to personal practice, and the people who pick it up first are going to ship better work for a stupid, embarrassing reason: they wrote down what they wanted it to have meant before they started.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.