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
Deleted Comment
1. https://minifeed.net/
2. https://minifeed.net/items/n1HZYMDEKyra
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.
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.
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!
Deleted Comment
Dead Comment
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.
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)
[1] https://fly.io/blog/
Sending emails isn't cost-free, but AFAIK, Buttondown [1] has a free plan for up to 100 subscribers. It's dead simple: they provide an issue archive [2] and handle subscription for you [3].
With their 100-subscriber free plan, you could limit this feature to a close circle. Maybe later monetize the newsletter feature to cover the ESP costs.
[1] https://buttondown.com
[2] https://buttondown.com/hacker-newsletter/archive
[3] https://buttondown.com/hacker-newsletter