Back to browse
GitHub Repository

Collection of engineering blogs from top tech companies as well as individuals. Integrated github actions to always keep it updated.

11 starsPython

Self-updating engineering blogs repo with GitHub Actions

by break_prod·Feb 12, 2026·6 points·0 comments

AI Analysis

MidShip It

Link validation bot for a 517-blog list. Solves a real problem, but the execution is straightforward automation.

Strengths
  • GitHub Actions automation prevents link rot in curated lists
  • Weekly validation catches moved or broken URLs automatically
  • Community-friendly: accepts submissions via PRs
Weaknesses
  • Core tech is standard CI/CD pipeline; no novel approach
  • Competes with existing blog aggregators (Hacker News, manual curation)
  • No differentiation beyond 'runs on schedule' — RSS readers already auto-refresh
Target Audience

Engineers looking for quality technical blogs; blog curators; open-source maintainers

Similar To

kilimchoi/engineering-blogs · TechReads aggregator

Post Description

Hi HN,

There’s a great engineering blog aggregation repo on github kilimchoi/engineering-blogs that I’ve used for a while. It’s an excellent resource, but it hasn’t been actively maintained in a few years — and many links have moved or broken.

That made me wonder: why do most “awesome engineering blogs” lists eventually decay?

So I built an open-source repo that aggregates engineering blogs and keeps itself updated automatically using GitHub Actions.

On a schedule, it:

> Checks blog sources for new posts > Detects broken or moved URLs > Validates links > Updates the index automatically

Basically - CI/CD for engineering blog aggregation.

I’d love feedback on:

> Any high-quality blogs I should include - specially from individuals or you > Better ways to detect canonical/moved content reliably > Whether RSS-only aggregation is enough

Thank you!

Similar Projects

Infrastructure●●Solid

Spawn – Deploy and Self-Heal Any GitHub Repo

It uses an LLM not just for scaffolding but as an active repair agent: Claude generates Dockerfiles, diagnoses crashes (diagnoseCrash) and can trigger redeploys or memory scaling. The architecture ties BullMQ, Fly Machines and a 30s health loop into a real feedback loop — clever and ambitious, but it also leans heavily on Claude + Fly/Supabase so expect nontrivial setup and vendor/LLM dependency.

WizardryBold Bet
gauravguitara
103mo ago