Most engineers plateau not because they stop coding, but because they stop reading anything longer than a changelog. The fastest correction is a reading list built from people who write about the systems they actually operate — not content marketing, not tutorials, but working notes from engineers debugging production.
This is that list: 12 categories, 100+ blogs, every link direct to the source. Independent blogs are grouped by what they teach; company engineering blogs are kept in their own section at the end, deliberately.
How to use this list
Don't subscribe to everything. Pick two categories that match what you are currently weak at, subscribe to three blogs in each via RSS, and give it a quarter. Depth beats breadth: reading every Martin Kleppmann post carefully will change your design instincts more than skimming fifty feeds.
1. Software architecture & engineering
This is where mental models for design come from — how to decompose a system, when to split a service, what a refactor is actually for. Martin Fowler's archive alone covers architecture, refactoring, microservices, data, testing and delivery, and remains the single strongest foundational resource on the web.
Architecture, refactoring, microservices, patterns, delivery
Software engineering, developer culture, practical lessons
Big Tech, engineering careers, engineering practices
Staff+ engineering, architecture, engineering organizations
Engineering management, leadership, technical organizations
Software design, formal methods, specification
Serverless architecture, AWS, distributed systems
2. Linux, networking & systems
The layer under your framework. Julia Evans is unusually good at making low-level concepts approachable — her own recommended reading points onward to Rachel by the Bay, Dan Luu and Aphyr when you want more depth.
Linux, networking, debugging, systems — with comics and zines
Linux performance, profiling, eBPF, observability
HTTP, networking, browsers, web performance
Hardware, performance, latency, systems, questioning assumptions
Linux, infrastructure, operations, production war stories
Databases, systems programming, distributed systems
3. Distributed systems
Jepsen is the essential one here: it shows what happens when real systems meet partitions, clock skew and crash-restart loops, instead of the idealized diagrams in vendor docs. Anirudhology is a newer resource worth watching for Raft, MVCC and storage-engine deep dives.
Distributed systems, databases, consistency, Kafka, CRDTs
Distributed-system correctness and failure testing
Distributed systems, AWS internals, performance
Large-scale architectures and system design case studies
Raft, MVCC, storage engines, distributed KV stores
Distributed systems, reliability, backend engineering
A free, opinionated distributed-systems course
4. Databases & storage
Eaton Phil has detailed material on implementing MVCC and transaction isolation from scratch; JusDB maintains a large practical collection across PostgreSQL, MySQL, MongoDB, indexing, migrations and HA. Use The Index, Luke! is still the best free SQL indexing course in existence.
SQL, indexes, query optimization for developers
Database internals, MVCC, storage engines, transactions
PostgreSQL, MySQL, MongoDB, HA, migrations
Databases meeting operating systems, durable execution
Database research made readable, self-driving DBs
MySQL internals, sharding, schema changes at scale
5. Performance & observability
Brendan Gregg's site is a body of Linux-performance work — flame graphs, eBPF, CPU and I/O methodology — that most teams never fully exhaust. Charity Majors is the one to follow if you want to understand how engineers actually debug production, rather than which dashboard tool to buy.
CPU profiling, flame graphs, eBPF, memory and I/O debugging
Hardware truths, latency measurement, engineering assumptions
Observability, production debugging, incident thinking
Tracing, high-cardinality telemetry, SLOs
Real-world performance engineering at scale
6. AI / LLM engineering
If you are shipping anything LLM-shaped, start with three: Simon Willison for practical tooling and what just changed this week, Lilian Weng for rigorous research explainers, and Chip Huyen for the systems and infrastructure side of production ML.
LLMs, AI tooling, practical AI engineering, daily notes
LLMs, agents, RL, AI research explained rigorously
ML systems, AI infrastructure, production ML
LLMs from scratch, ML fundamentals, implementation detail
Transformers and LLM concepts, visually
ML research and explanation, essays
Open-source ML/LLMs, fine-tuning, inference
7. Engineering thinking & senior-level growth
The senior-to-staff transition is mostly judgement, scope and communication. These writers cover the parts no framework documentation will.
Staff engineering, architecture, organizations
Critical thinking and engineering trade-offs
Big Tech engineering and careers
Observability and engineering culture
Engineering leadership
Engineering management and leadership craft
Software businesses, careers, engineering economics
8. Research / papers explained
The Morning Paper is a finished archive, but it is still the best on-ramp to reading CS research — hundreds of papers summarised by someone who read them properly. Papers We Love is the discovery layer for foundational work in distributed systems, databases, OS, PL and networking.
CS research papers summarised readably
Discovering foundational papers across CS
Formal methods and software correctness
Distributed systems paper reviews
9. Visual explainers — making hard things simple
Bartosz Ciechanowski's interactive articles are the gold standard for explaining something hard without dumbing it down. If you produce technical content yourself, study his structure as much as his subject matter.
Interactive visual explanations of hard physical and computing concepts
Comics and zines that make systems concepts click
Playable explanations of complex systems
Algorithms and geometry, interactively
10. Programming & practical development
React, JavaScript, programming concepts from first principles
Testing, React, frontend engineering
CSS, frontend, delightful visual explanations
Web development, CSS techniques
Web performance, browser platform features
Frontend and web development, design engineering
Software engineering, teams, product development
11. Newer / lesser-known blogs worth adding
These give you material your peers have not already seen twice on LinkedIn. Umur Inan covers backend and production failure modes — PostgreSQL performance, UUID primary keys, scheduled jobs firing across replicas. Backend Bytes and SysDesPro focus on reliability and system design respectively.
Backend, PostgreSQL performance, UUID keys, production failure modes
Production-grade backend engineering and reliability
Raft, MVCC, storage engines, caching deep dives
System design, scalability, databases, distributed systems
Visual system design breakdowns
12. Company engineering blogs
Keep these in a separate folder. Company blogs are excellent for real architecture case studies and scale numbers you can quote in an interview; individual blogs are better for building the mental models that let you reason about a system you have never seen.
If you only read 20
Fifty links is a bookmark graveyard. This is the shortlist that will actually move your engineering ability in a year.
Building a reading routine that survives
Use an RSS reader rather than social feeds — the algorithm will not show you a 6,000-word post about MVCC. Block 45 minutes a week. Read one post properly rather than five superficially, and keep a running note of the ideas you could reuse: a failure mode, a metric, a design trade-off with a name.
Then go build something with it. Reading about consistency models is useful; being forced to choose one under interview pressure is what makes it stick.