The problem: When learning a new technology, the best insights often come from how companies like Google, Meta, or Stripe actually implement it in production. But these gems are scattered across dozens of separate engineering blogs with no way to search across them.
What I built: Engineering.fyi indexes engineering blogs from ~15 companies (Google, Meta, OpenAI, Anthropic, Stripe, Uber, etc.) and makes them searchable in one place. You can filter by topic, difficulty level, and whether articles include code samples.
Technical details: - Built with Next.js, SQLite, DrizzleORM - Custom scrapers for each blog (they're all frustratingly different) - Basic tagging system using content matching (still improving this)
Current status: Core search is working. Adding new blogs weekly as I index them.
Next features (based on early feedback): - AI summaries for quick article previews - Weekly digest of trending engineering insights - Save/bookmark articles (considering whether to add accounts)
Interesting challenges: - Each blog requires custom parsing logic (no standard format) - Building an accurate tagging system is harder than expected – started with exact matching but exploring better approaches
I'd love feedback on: - Which company engineering blogs you'd find most valuable to include - Whether AI summaries would actually be useful or just noise - How you currently discover engineering articles from these companies
I'd advise to put it at the top, before the text, to let people know beforehand and not be caught off guard. Then you can have a big button saying "read full article in website" or something, to make it easy for people to see both options.
It's a cool idea, but maybe a improvement could be to select a random handful per day, and let them stay there for a while? Fewer surprises this way!
Example (had to search on kagi with site:minifeed.net):
You Can Either Steal Great Developers or Farm Them To grow software development teams, you can either steal excellent developers or you can develop them internally.
Also a nice reminder to move my website off of cloudflare asap
Cloudflare thinks your browser is part of a DDoS?
Cloudflare is attacking your browser from several places across the internet?
https://security.stackexchange.com/questions/278660/why-are-some-cloudflare-challenges-cpu-intensive
I understand it isn’t related to DDOS but used it as a joke since it is basically attacking my browser
https://kagi.com/lenses/LdYine8hZtYmrt8yTMngOUtvTM9rmkRy
Kagi Lenses can be defined in many ways, one of which is specifying URLs to search. Unfortunately you can only provide 10 URLs per lens. Here are the ones I chose:
https://stripe.com/blog/engineering, https://engineering.fb.com/, https://www.uber.com/en-US/blog/engineering/, https://netflixtechblog.com/, https://research.google/blog/, https://technology.riotgames.com/, https://incident.io/blog, https://www.anthropic.com/engineering, https://openai.com/news/, https://shopify.engineering/
Meta’s Pyrefly announcement (may 2025)
Netflix post about their overall use of python (March 2013)
Google’s announcement of the Croissant ML metadata format (March 2024)
Looks inside
>15 tech companies blogs
This is unfortunate, RSS has promise to be that standard format. I've seen high adoption, but it's not universal.
In any case, I know there are some other solid individual blog collections in the comments - good luck with feature addition.
I've found software security companies tend to have interesting blog posts.
So many show and tells neglect that
I guess this is a reason why it does not have recent blogs from some of the sites. Otherwise, it's definitely something I'd use
Hyped up tech is like milk, it stinks after a couple of days. Open protocols are like fine wine, they age beautifully.
P.S. Your site is offline. If it wasn't and you even had one interesting article, I would have added your website to my list of feeds. I picked up hundreds of interesting websites/feeds through HN alone in the last years.
I think not.
That's the industry standard.
My GP and my veterinarian and also my librarian are all doctors, but less ambiguously they are respectively MD, DVM and PhD.
A couple of thoughts from my own workflow: • I’d definitely add smaller but high-signal engineering blogs. Some of the most interesting write-ups I’ve read came from companies that aren’t FAANG-level but are operating at scale (think Segment, Plaid, Posthog, Linear). They often publish very focused “lessons learned” pieces that don’t get much SEO love. • AI summaries could be useful if they’re really accurate and highlight the “why” behind a technical decision, not just rephrase the intro paragraph. I’d probably use them to triage which posts to read in full. • For discovery, I usually rely on Twitter/X and the occasional Reddit thread. The problem is that those channels are noisy — so something that’s searchable and filterable like you’ve built is appealing.
One nit: for tagging, maybe consider a lightweight NLP approach (spaCy / transformers) that can detect concepts beyond exact matches. Even basic keyword clustering could improve relevance without needing a massive ML pipeline.
Nice work — bookmarking this for the next time I need to dig into how someone scaled their job queues without setting their hair on fire.