Why I Built BlogDrop

July 20, 2026blogdropopensourceweb-developmentproduct

When I started learning web development, YouTube was my main source.

It was great for beginners, but after some time I wanted deeper content.

That's when I found engineering blogs.

Companies like Vercel, Cloudflare, Stripe, and GitHub publish amazing articles. Many open-source projects also share how they build things.

The problem?

Everything was scattered.

Too many tabs, too many bookmarks

I bookmarked dozens of blogs.

Some had RSS feeds.

Some didn't.

Some posted every week.

Others once a month.

After a few weeks I completely forgot to check most of them.

I knew good content existed, but finding it every day became a chore.

I tried RSS readers.

They worked, but they weren't built for developers.

I didn't want news, marketing posts, or random articles.

I only wanted high-quality engineering content.

I also wanted AI summaries so I could quickly decide whether an article was worth reading.

I couldn't find a product that solved this the way I wanted.

So I decided to build it.

BlogDrop started as a small weekend project.

My goal was simple.

Collect engineering blogs in one place.

As I kept building, more ideas came.

Every feature came from a problem I personally faced.

This project taught me much more than any tutorial.

While building it, I learned about:

More importantly, it taught me how to build a real product instead of just following tutorials.

BlogDrop is still growing.

There are many features I want to add and many things I want to improve.

I'm building it in public, learning as I go, and sharing the journey.

If BlogDrop helps even one developer discover a great article they would have otherwise missed, I'll consider it a success.

Thanks for reading. 🚀