The engineering-blog landscape has thinned in 2026 — many writers have moved to newsletter platforms or to LinkedIn — but the durable blogs that remain are unusually high signal. This is a curated list of blogs where the writer or company ships consistently, the content has aged well, and the archives reward exploration.
Company engineering blogs worth following
The Stripe engineering blog
Long-form posts on infrastructure decisions, payments engineering, and developer experience. The signal-to-noise is unusually high — Stripe ships a small number of posts per year, and each one is substantive. Most useful when you are building or scaling payments-adjacent infrastructure.
The Shopify engineering blog
Strong on Ruby, on monolith-versus-microservice patterns, and on engineering culture. Shopify writes more honestly about architectural decisions than most public engineering organizations.
The Netflix tech blog
The original "famous engineering blog." Still substantive in 2026, with strong content on data engineering, observability, and large-scale operations. The signal varies by post; pick deliberately rather than read sequentially.
The Cloudflare blog
Daily-cadence posts on networking, security, and infrastructure. Higher volume than most company engineering blogs, with corresponding variance in signal. The deep-dive incident write-ups are some of the best in the industry.
The Discord engineering blog
Strong on real-time systems, on scaling chat infrastructure, and on the engineering-organization side of building consumer software. Lower volume, higher signal.
The GitHub blog (engineering category)
Posts on the engineering organization behind GitHub itself. Useful as a window into how a developer-tools company operates internally.
Reading About the Problem Is Step One
Every resource on this list points at the same gap: distributed teams lose state between shifts. StandIn is the governance layer that closes it — handoffs, decisions, and authority captured from the tools your team already uses.
See the Workflow →The Honeycomb blog
Charity Majors and the Honeycomb team write some of the strongest observability and engineering-culture content in the industry. The combination of operational rigor and cultural honesty is distinctive.
The Slack engineering blog
Strong on the operational engineering of a tool that millions of teams depend on continuously. Most useful for the infrastructure-scale write-ups and for the engineering-organization posts.
The Increment magazine (Stripe-published)
Long-form engineering essays on rotating themes. The publication pace is slower than a typical blog but the depth per post is significantly higher.
Individual writer blogs
Will Larson's blog
The companion to An Elegant Puzzle and Staff Engineer. The essays on engineering management, technical leadership, and decision-making compound into a coherent worldview. Read the archives.
Charity Majors's blog
Engineering culture, observability, and the hard parts of management. Charity writes with a directness that is rare in the field, and the essays on engineering leadership have aged well.
Camille Fournier's blog
The companion to The Manager's Path. Lower update cadence than during the book's era but the archives remain essential reading.
Lara Hogan's blog
The "donut of authority" frame and related essays on management. Hogan writes structurally about human dynamics in a way that resists pop-management framing.
Julia Evans's blog (jvns.ca)
Not management-focused but durably useful for engineering managers who want to stay technically literate. Julia writes about systems and tooling in a way that compounds your model of how computers work.
Dan Luu's blog
Engineering essays with unusual rigor and unusual contrarianism. The posts about software-industry myths and about engineering-organization patterns are some of the most-cited engineering writing of the last decade.
Patrick McKenzie's writing (Bits about Money and the older Kalzumeus archive)
Not strictly engineering, but engineering managers benefit from the structural thinking. The older essays on running a software business and on the structure of work apply directly.
Newer blogs worth watching
Several newer engineering blogs have built sustained audiences in 2024–2026. Rather than name specific writers whose content can change, the structural advice is to follow the citation graphs from the established blogs above. The writers Will Larson and Charity Majors regularly cite tend to be the most credible voices forming the next layer of the canon.
What to do with blog archives
The strongest move on this list is to read the archives rather than to follow new posts. The compounding value of older essays from established writers exceeds the marginal value of new posts from the same writers. Block an hour and read Dan Luu's archive systematically; you will encounter five or six structural ideas that will improve your judgment for years.
Reading patterns that work
Use RSS, not the algorithm. Aggregate the blogs in a feed reader and process them in deliberate blocks rather than ambient scrolling. The signal-to-noise of a curated RSS feed of substantive engineering blogs is higher than any social platform's content surface.
What to skip
Vendor-content marketing blogs framed as engineering content. Blogs that repost the same listicle-format posts across years. Engineering blogs whose writers have moved on but whose company still publishes under the brand without substance.
Frequently asked questions
Which engineering blog should I read first in 2026?
Will Larson's blog. The archive is the cleanest single body of engineering-management writing in the field, and the essays compound rather than age.
Are company engineering blogs worth following?
Yes, but selectively. Three or four company blogs read consistently outperform fifteen blogs sampled. Pick the ones whose engineering practice you actually want to learn from.
How does StandIn fit into engineering-blog reading?
The blogs describe the patterns; StandIn is where the patterns become practice. The structured handoff and decision-record discipline the better engineering writers advocate is the operational layer StandIn provides.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.