Argues that GigaOM's 2006 launch — a small team with a strong voice covering infrastructure as the real story — established the default configuration for modern Substacks, developer podcasts, and solo technical blogs. Before Malik, tech coverage was gadget reviews and earnings recaps; he created both the beat and the audience for it.
Highlights that Malik covered peering agreements, last-mile economics, dark fiber, and mobile spectrum auctions when general-interest outlets ignored them. His 2003 dark fiber piece and 2007 'In Search of Bandwidth' essay are cited as proof he saw infrastructure as the substrate of the industry, not as back-office trivia.
Submitted the minimal om.co memorial notice, which drew 857 points not for industry retrospectives but for commenters resurfacing specific Malik posts going back two decades. The top responses linked to a 2003 dark fiber piece, a 2007 hospital-bed essay, and a 2014 Bay Area fog photograph — suggesting his personal voice and specific work, not GigaOM-the-brand, are what endured.
A short notice appeared on om.co on June 24, 2026, under the title 1966–2026 — the standard memorial dash. Om Malik, founder of GigaOM, partner at True Ventures, and one of the small group of writers who effectively invented modern tech blogging, has died at 59. The Hacker News thread climbed to 857 points within hours, with comments dominated not by industry hot takes but by people recalling specific posts — a 2003 piece on the economics of dark fiber, a 2007 reflection after his heart attack, a 2014 photograph of fog over San Francisco Bay.
Malik moved to the U.S. from India in 1993, wrote for Forbes and Red Herring through the dot-com peak and bust, and in 2001 started a personal blog that became GigaOM in 2006 — one of the first venture-backed tech publications. He sold the brand in 2015, walked away from daily journalism, and spent the last decade as a True Ventures partner, a photographer, and a slow writer. The HN thread surfaced posts going back two decades; one of the highest-voted comments simply linked to his 2007 essay *In Search of Bandwidth*, written from a hospital bed days after a heart attack at 41.
No public cause of death has been confirmed at time of writing.
It is hard to overstate how unusual GigaOM was when it launched. In 2006, technology coverage at general-interest outlets meant gadget reviews and earnings recaps. Trade press covered procurement. Malik treated infrastructure — peering agreements, last-mile economics, mobile spectrum auctions, the unsexy plumbing — as the actual story, and wrote about it for an audience that included both Verizon executives and college sophomores hacking on Rails. That audience didn't exist yet. He helped create it.
The template he established — a small team, a strong voice, a beat defined by the writer's obsession rather than the assignment desk — is now the default configuration of every Substack, every developer-focused podcast, every solo technical blog with a Stripe link. Stratechery, Platformer, Casey Newton, Ben Thompson, the entire genre of "one analyst with a newsletter is worth more than the trade publication that fired them" — that lineage runs through GigaOM. So does the modern conference business: the GigaOM Structure events in the late 2000s were where you went if you wanted to understand cloud before the word had stabilized.
There's a particular sentence pattern Malik used that the community kept quoting overnight: he would describe a piece of infrastructure, then a piece of human behavior, then refuse to connect them, leaving the reader to do the work. His best posts treated the reader as a peer who could finish the thought — which is, not coincidentally, exactly the contract a senior engineer wants from a technical post and almost never gets. The current generation of tech writing — long, breathless, every implication spelled out twice — is in many ways a retreat from what he was doing twenty years ago.
His health writing matters too. After his 2007 heart attack he wrote with unusual candor about what running a media startup costs a body, well before "founder burnout" was a content category. That essay still circulates; founders email it to other founders.
If you ship software for a living, you probably absorbed Malik's influence without knowing his name. The expectation that infrastructure deserves prose — that a thoughtful 1,500 words on Cloudflare's anycast topology or AWS's networking primitives is journalism, not marketing — comes substantially from the beat he built. Every time a backend engineer reads a deep-dive on Postgres internals over coffee instead of a press-release summary of a funding round, that habit was scaffolded by the publications GigaOM made possible.
There is also a practical lesson in his career arc. Malik sold at the top, walked away cleanly, and spent ten years doing slower work — photographs, occasional essays, venture investments where the partnership name appears before his. Tech media's current crisis (collapsing CPMs, AI summarization, the slow death of the link economy) is partly a consequence of nobody else taking that exit; the people who built modern tech blogging mostly stayed, optimized for scale, and watched the model erode around them. His om.co domain — short, owned, no platform between him and the reader — outlived three rounds of platform consolidation. That is the developer-relevant takeaway: own the substrate.
For anyone running a technical blog, newsletter, or developer-relations function: re-read his archives this week. Not for nostalgia. For the cadence. The pieces are short. The headlines are flat. The sentences earn their length. Almost no post on om.co would survive a modern SEO audit, and almost every one of them is still readable.
The tech-media model Malik helped invent — independent voice, infrastructure beat, paid by ads or events or a venture day job — is currently being compressed from both ends by AI summarization on top and platform consolidation underneath. The next decade's version will look different. But the question his work poses to anyone writing about software in 2026 is the same one it posed in 2006: are you covering the product, or are you covering the substrate the product runs on? He chose the substrate, and a generation of developers learned to read because of it.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.