kilimchoi/engineering-blogs

A curated list of engineering blogs

Summary

engineering-blogs is a curated, alphabetized list of engineering blogs grouped into three sections: Companies, Individuals/Group Contributors, and Products/Technologies. Each entry pairs a name with a link to the blog's home page, and the repository ships an OPML file so the whole list can be loaded into an RSS reader at once. It is licensed under Creative Commons Attribution-ShareAlike 4.0 and carries the "Awesome" badge shown in its README header.

What it is useful for

The repository acts as a directory for engineers who want to follow primary-source technical writing instead of relying on social feeds or aggregators. It spans a wide range of voices, from large company engineering teams such as Airbnb, Cloudflare, GitHub, Stripe, and Spotify, to individual practitioners like Julia Evans, Dan Luu, Martin Fowler, and Brendan Gregg. The Products/Technologies section lets readers jump straight to blogs tied to a specific stack, including Go, Rust, Kotlin, Swift, React Native, .NET, and Crystal. Because entries are simply links, the resource is language-agnostic and stays useful regardless of which platform or framework an engineer is working on.

How engineers can use it

The README can be browsed directly on GitHub, using the letter indexes at the top of each section to jump to a range of names. To subscribe in bulk, download the engineering_blogs.opml file referenced under the "RSS feeds" heading and import it into an RSS reader. Engineers can also open contributing.md before proposing a new blog or fixing a broken link, since the project states that contributions are welcome. One observation supported by the source: the list contains historical entries such as separate "GitHub" and "GitHub Old" links, as well as a "Zendesk(old)" entry, so a small number of URLs may be superseded; the README does not document a separate vetting process beyond its contribution guidelines. For the complete list, the contribution rules, and the full license text, readers should consult the repository directly.