# sumodirjo/engineering-blogs: A Directory of Company Engineering Publications > sumodirjo/engineering-blogs is a curated GitHub directory linking engineers to technical blogs operated by startups and enterprises. It offers discovery rather than search, indexing, feeds, or article archival. **sumodirjo/engineering-blogs** — A curated list of engineering blogs of startup and enterprise companies - Repository: https://github.com/sumodirjo/engineering-blogs - Website: https://github.com/sumodirjo/engineering-blogs - Stars: 1,678 · Forks: 238 - Language: Unknown - License: GPL-2.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/sumodirjo-engineering-blogs ## What sumodirjo/engineering-blogs Contains sumodirjo/engineering-blogs solves a discovery problem: finding publicly accessible engineering and technology blogs maintained by companies. Its audience includes engineers looking for technical writing outside their own employer, developers who want to follow how other organizations discuss engineering, and readers interested in company-operated technical publications. The collection spans startups and enterprises, with entries associated with organizations such as 500px, 8thLight, Addepar, Affirm, Amazon, Asana, Atlassian, BBC, Booking.com, and Bloomberg. This is not a blog reader, crawler, search engine, or mirror. The repository's top-level files are `CONTRIBUTING.md`, `LICENSE`, `README.md`, and `SOURCES.md`. The visible README is a Markdown table with a blog link and a short description for each company. Examples include direct engineering sites such as `https://developers.500px.com/` and `https://tech.affirm.com/`, as well as publications hosted elsewhere, including Medium publications for Addepar, ASOS, and BBC Design & Engineering. That distinction matters when judging adoption. The project can shorten the path from “I want a company engineering blog” to a relevant URL, but it does not document full-text search, topic filters, article metadata, feeds, snapshots, or an archive of removed content. A reader still has to visit each linked site and use that site's own navigation and search facilities. ## How the README Routes Readers to External Blogs The directory's mechanism is deliberately simple. `README.md` presents company names as Markdown links, with a neighboring description identifying the linked publication. The link is the useful payload; the short label gives enough context to recognize what will open. The visible collection is arranged alphabetically, beginning with `500px`, `8thLight`, and `99Designs` before continuing through company names. The entries do not use one hosting model. Some point to company-owned engineering domains, such as Algolia's `https://blog.algolia.com/`. Others point to broader technical blogs, including Amazon's `https://developer.amazon.com/blogs`. Some point to a category page, such as Asana's `https://blog.asana.com/category/eng/`, while others point to a Medium-hosted publication. This makes the directory useful across different publishing practices, but it also means destination behavior is outside the repository's control. Based on the repository layout, contribution guidance is separated into `CONTRIBUTING.md`, while source information has its own `SOURCES.md`. The README does not state the submission process, selection criteria, or editorial checks. It also does not document whether links are checked automatically, reviewed periodically, or corrected after user reports. A broken destination would therefore not be distinguishable from an undiscovered publishing change without checking the linked site itself. ## Opening the Directory and Making a First Use The README does not document installation because this repository is a directory rather than an application. It does not list a package, downloadable archive, executable, container image, or application server. The project is available through its GitHub page at `https://github.com/sumodirjo/engineering-blogs`, where a reader can open `README.md` and follow the entries. A first practical use is to identify the kind of company or publication you want, find its row in the README, and open the linked blog. Someone looking for Algolia's technical publication can select the `Algolia` row and visit `https://blog.algolia.com/`. A reader interested in a broad developer publication can start with Amazon's link at `https://developer.amazon.com/blogs`. These are browser navigation actions, not project commands, so there is no CLI setup to demonstrate. The GitHub repository metadata reports no GitHub releases. Readers should therefore not expect versioned directory archives or release notes describing additions and removals. The relevant artifact is the repository content on its default branch, `master`. Any workflow that depends on a particular set of entries must also account for the possibility that the list changes on that branch. ## Why the Engineering Blog List Is Not a Search System The central limitation is the absence of a documented discovery interface beyond the README table. Finding a company differs from finding an article about a database, deployment practice, programming language, incident, or system design. The README shows company links and brief labels, but it does not document a full-text index, category taxonomy, date filters, language filters, or author search. Readers who know the subject but not the company must either inspect a long list or rely on an external search engine. Link durability is another boundary. Destination sites include different URL schemes, including `http`, `https`, WordPress, custom domains, GitHub Pages, and Medium. The repository does not document an uptime check, redirect policy, archive copy, or automated validator. A listed publication may change location, become unavailable, or alter its editorial focus after the entry is added. The directory cannot supply the missing article if the destination disappears, and its short table entry provides no failure notification mechanism. It is also the wrong tool for a systematic literature review. A curated link list does not establish article metadata, publication chronology, authorship policy, citation format, or content retention. Researchers who need reproducible source coverage should collect and preserve selected articles and their metadata separately. This repository can serve as a starting point for that collection, but the README does not present it as archival infrastructure. ## GitHub Bookmarks Versus Search and Feed Tools A practical alternative is a company-neutral search engine or an RSS reader configured with publication feeds. The approaches differ clearly. `sumodirjo/engineering-blogs` starts from known organizations and supplies destination URLs. A search engine starts from a query such as a technology, engineering practice, or company topic and returns matching pages across the web. An RSS reader starts from subscription sources and presents later publications in a reading workflow. Another alternative is a hand-maintained reading list in a bookmark manager or notes application. Such a list can include private annotations, tags, reading status, and selected article links. The trade-off is that those organizational features come from another tool rather than this repository. Conversely, the GitHub directory requires no documented application setup and keeps company destinations in a public Markdown table, but the README gives it no filtering or annotation layer. For an engineer looking for one known company's technical writing, this directory is direct. For someone trying to answer a technical question or monitor many publications over time, a search engine or feed reader serves a different information-retrieval model. The right choice depends on whether the company is known before the search begins. ## Maintenance, Contributions, and GPL-2.0 Implications The repository is not archived, and its last push was on 2026-10-11. That date records recent repository activity, but the available files do not explain the maintainers' review schedule or the frequency of link checks. There are no GitHub releases, so release-based upgrade notes and version migrations are not available. The default branch is `master`, which means the README itself is the operational artifact readers should inspect. The presence of `CONTRIBUTING.md` indicates that contribution guidance exists, but the README does not document how a company can submit a blog, what qualifies for inclusion, whether broken links are accepted, or whether external descriptions may be edited. Those details must be checked in `CONTRIBUTING.md` before making a contribution. The presence of `SOURCES.md` indicates a separate source record, but the README does not reveal its format or maintenance process. The repository is licensed under GPL-2.0. Maintainers who copy or modify covered repository content may have redistribution and license-preservation obligations. The linked blog articles are external publications, and this repository's GPL-2.0 license does not state the licensing terms for those articles. Anyone planning to reproduce an article should check the destination site's own terms rather than assuming the directory license covers it. ## Conclusion Adopt this directory when you want a lightweight way to discover company engineering blogs, especially for reading about work done at other organizations. Do not treat it as a searchable knowledge base or rely on it for article history and destination availability. Before building a workflow around it, inspect `CONTRIBUTING.md` for inclusion rules, check representative links, and review `SOURCES.md` for how the directory was assembled. The repository is a bookmark collection, not an engineering content platform. ## FAQ ### What is sumodirjo/engineering-blogs? It is a curated GitHub list of engineering blogs operated by startup and enterprise companies. The README stores each entry as a company link with a short description. ### How do I install sumodirjo/engineering-blogs? The README gives no installation procedure because the repository is a directory rather than an application. Open `README.md` on the GitHub page and follow the relevant blog link. ### Does sumodirjo/engineering-blogs provide search or article archives? No search, feed, full-text index, or article archive is documented. It provides links to externally operated publications, so readers must continue to each destination site. ### Can I add a company engineering blog to sumodirjo/engineering-blogs? The repository includes `CONTRIBUTING.md`, which indicates that contribution rules exist, but the README does not state the acceptance criteria. Read that file before adding an entry. ### What license applies to sumodirjo/engineering-blogs? The repository metadata identifies GPL-2.0 as the project's license. The README does not state the license for articles hosted on the linked external blogs. ## Sources - [Issues](https://github.com/sumodirjo/engineering-blogs/issues) - [License: GPL-2.0](https://github.com/sumodirjo/engineering-blogs/blob/master/LICENSE) - [Project website](https://github.com/sumodirjo/engineering-blogs) - [README](https://github.com/sumodirjo/engineering-blogs/blob/master/README.md) - [sumodirjo/engineering-blogs on GitHub](https://github.com/sumodirjo/engineering-blogs) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/sumodirjo-engineering-blogs