Engineering Blogs: A Plain-Text Directory of Who Publishes What
GitHub describes it as A curated list of engineering blogs. The repository metadata lists Ruby as its primary language. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- This curated list organizes hundreds of engineering blogs by company, individual, and technology, but its value depends on how current its links remain. For engineers who want a single alphabetical starting point, it works; for those who need active maintenance, it may disappoint.
- Who is it for?
- Adopt this list if you want a single, alphabetically sorted index of engineering blogs from companies like Airbnb, AWS, and Cloudflare, plus individual contributors, and you are comfortable checking links yourself. Do not adopt it if you need guaranteed freshness or automated updates, because the last push was on 2024-08-21 and the repository has no releases.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Probably not. The repository last received commits 27 months ago, on August 21, 2024.
- What is it written in?
- Mainly Ruby, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- kilimchoi/engineering-blogs38,978 ★ · +484
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| kilimchoi/engineering-blogs | 38.5k | 39k |
484 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What This List Actually Solves
The repository addresses a simple problem: finding engineering blogs without searching the web each time. It collects links to company blogs, individual writers, and product or technology blogs in one place. The target user is an engineer who wants to follow technical writing from known organizations and practitioners. The README shows three main categories: Companies, Individuals/Group Contributors, and Products/Technologies. Each category is split by first letter, with entries like 'Airbnb https://medium.com/airbnb-engineering' and 'AWS https://aws.amazon.com/blogs/aws/'. There is no description of what each blog covers, no tags for topics, and no indication of posting frequency. It is a directory, not a discovery engine. For someone who already knows which companies they want to follow, the list saves time. For someone exploring new sources, the lack of context means clicking through many links to find relevant content.
The Structure: Alphabetical Tables and Markdown Links
The main content of the repository is the README file; it also holds engineering_blogs.opml and generate_opml.rb. The top of the file has three navigation tables, one per category, with letter links that jump to anchor points like '#a-companies' or '#i-individuals'. Each category then lists entries as bullet points in the format 'Name URL'. The Companies section comes first, with entries from 8th Light to Jane Street and beyond. The Individuals and Products sections follow the same pattern. This structure is plain Markdown, so it renders on GitHub and in any text editor. There is no database, no JSON file, no API. The data is in the README, with an engineering_blogs.opml export alongside it. That makes it easy to read and edit, but it also means the list is only as good as the last manual update. The alphabetical order is strict by company name, not by topic, so if you want blogs about databases, you cannot filter for that. You have to know the company name first.
How You Get It Running: Clone or Read
There is no installation step. The repository is a GitHub project, so you access it by visiting the page or cloning it. A typical command is 'git clone https://github.com/kilimchoi/engineering-blogs.git'. After cloning, you open the README.md file in any editor or browser. The README itself is the product. Reading the list needs no config keys, dependencies or build process. The primary language listed is Ruby, and the repository includes generate_opml.rb, a Gemfile and a .ruby-version file. If you want to use the list programmatically, the repository also includes engineering_blogs.opml. For a quick look, the GitHub web interface is sufficient. The navigation tables work on the rendered page, letting you jump to the letter you want.
The Maintenance Problem: A Static List in a Moving Web
The repository metadata shows no recent push and no releases. That is a red flag for a directory of links. Engineering blogs change URLs, move to different platforms, or shut down. The README includes entries like 'Facebook https://code.facebook.com/posts/' and 'GitHub Old https://github.com/blog/category/engineering', which suggest the list has not been fully updated for current domains. Facebook's engineering content moved to engineering.fb.com, and GitHub's blog has changed structure, but the list still carries the old paths. This is not a criticism of the original curator, who likely built the list over time, but it is a practical limitation. If you rely on this list for fresh content, you will encounter dead links or redirected pages. The repository has a contributing.md file. The list is a snapshot, not a living resource.
A Real Alternative: RSS Aggregators and Awesome Lists
If you want a more dynamic way to follow engineering blogs, an RSS reader with a curated OPML file is a direct alternative. Services like Feedly or self-hosted readers allow you to subscribe to individual blog feeds, and you can organize them by category. The difference in approach is that an RSS reader fetches new posts automatically, while the README only gives you the URL. The repository also ships engineering_blogs.opml, a format RSS readers commonly import. Another alternative is the 'awesome' list ecosystem, which this project explicitly references with the awesome badge. Other awesome lists, such as those for specific languages or topics, often include blog sections with more context, like a one-line description of each blog. The engineering-blogs list has no descriptions, so an awesome list with annotations can save you time in deciding which blogs to open. However, those lists also face the same maintenance challenges. The key difference is that an RSS reader gives you ongoing updates, whereas this repository gives you a static set of links.
What the List Covers and What It Omits
The Companies section covers a broad range of companies, from large tech firms like AWS and Facebook to smaller ones like Haptik and Hashnode. The README also has Individuals/Group Contributors and Products/Technologies sections. There is no geographic filter, no language filter, and no topic filter. The list also omits any indication of post quality or frequency. A blog with one post per year is listed the same as a blog with daily posts.
The Trade-Off: Simplicity Versus Usability
The repository's strength is its simplicity. A single main README, no setup needed to read it. That makes it easy to fork, edit, and share. The trade-off is that simplicity comes at the cost of usability. Without metadata like topics, last updated dates, or RSS feed URLs, the list is just a phone book. You still need to visit each link to see if the blog is active and relevant. For an engineer who wants to quickly find the blog of a specific company, the alphabetical order is convenient. For someone who wants to discover new blogs based on their interests, the list is nearly useless. The lack of any automated checking means broken links persist indefinitely. The project's primary language is Ruby, and the repository includes generate_opml.rb alongside the Markdown content.
Licence and Contribution: What You Can Do With It
The license field is unknown. That means you have no explicit permission to reuse the list in your own project, beyond what GitHub's terms allow for viewing and forking. If you want to create a derivative list, you should contact the repository owner or check the repository for a license file, which the top-level file list does not include. The repository has a contributing.md file, and the 'awesome' badge in the README points to the awesome list conventions. In practice, you can fork the repository and submit a pull request, but the lack of recent activity suggests the maintainer may not review contributions promptly. For personal use, you can clone the repo and edit the README locally. For redistribution, you need to clarify the license first. This is a legal boundary, not a technical one.
Editorial conclusion
Adopt this list if you want a single, alphabetically sorted index of engineering blogs from companies like Airbnb, AWS, and Cloudflare, plus individual contributors, and you are comfortable checking links yourself. Do not adopt it if you need guaranteed freshness or automated updates, because the last push was on 2024-08-21 and the repository has no releases. Before relying on it, verify that the URLs you care about still resolve, since many entries point to Medium or company domains that change frequently. The project is a static snapshot, not a service, so treat it as a starting point for your own curated bookmark set.
Frequently asked questions
What are the best engineering blogs?
engineering-blogs does not rank anything. It groups entries into Companies, Individuals/Group Contributors, and Products/Technologies, with an A to Z jump table for each section, and each entry is a name followed by a URL. It points at publications rather than judging individual posts, so it can tell you where engineering writing exists but not which one to read first.
What are some good blogs about engineering?
The list points at company and product engineering publications including Airbnb, Cloudflare, Databricks, Discord, Docker, DoorDash, Dropbox, GitHub, Envoy, and Instagram. Entries are alphabetical by name, with no subject index and no per-entry dates, so breadth is what the file offers rather than any guidance on quality or recency.
What files make up the engineering-blogs repository?
Beyond README.md the repository contains generate_opml.rb, an engineering_blogs.opml feed export, a Gemfile, a Gemfile.lock, a .ruby-version file, and contributing.md. The default branch is master, and the repository publishes no GitHub releases. There is no LICENSE file among the top-level entries.
When was engineering-blogs last updated?
The last push to the default branch master is dated 2024-08-21, and the repository has no GitHub releases. No individual entry carries an added date or a last-verified date, so the currency of any particular address cannot be established from the repository itself.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/kilimchoi-engineering-blogs)Star history chart for your README
[](https://hysenlabs.com/projects/kilimchoi-engineering-blogs)Was this useful?