ENGINEERING ★ 5 upvotes 2019

Show HN: how I built my replacement for reading lists and Pocket

Retrospective Overview & Key Insights

Distilled analysis of the business dynamics, operational challenges, and strategic takeaways:

In this technical retrospective (2019), @piotrgrudzien shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.

Core Principles for Independent Builders:
1
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
2
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
3
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:

HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.

Founder's Discussion Replies (@piotrgrudzien)

Direct clarifications and follow-up comments shared by the author during the live discussion:

OP @piotrgrudzien Original Author
2019

There are always new articles, videos, podcasts, blogs, tweets, websites, books or plaintext thoughts that I'd discover or get recommended by friends. It's impossible to consume all that content as soon as it arrives. But it's also really important that it doesn't get lost and I do get round to going through it at some point.

I would use several reading lists (or apps) which is a great solution in many ways. But they didn't feel like a problem off your chest. On the contrary, you need to remember where all your reading lists are so you get back to them at some point. I still have several of those buried somewhere on my computer.

Another big problem with reading lists is that it's so difficult to just pick the next item to read. Which list do I go for? Do I start off the top or at the bottom?

And when I've picked up that one article or video, I'm pretty sure there was a specific reason why I'd saved it or perhaps someone recommended it to me but I've forgotten now. Also, I'm pretty sure I've saved something more recent and relevant on the same topic since. At this point, all the context is gone.

That's why we built Itemsy around the exact experience I would've wanted for myself. Here is how it works:

1. Start emailing links to any content you want to save for later to my@itemsy.com (optionally, include a note or email of a person you want to share it with)

2. You get delivered your personalised newsletter that's just the right volume so you can read it as soon as you get it

To me personally, the main thing has been that I can forget all about the reading lists and actively trying to find time to go back to them. Just dump all the links onto Itemsy, they won't get lost and will be delivered to you in bite-sized chunks at a frequency of your choice.

We'd love for you to try it out. Signing up takes 10 seconds: https://itemsy.com/

HISTORICAL ERA Cloud & Mobile Era (2014–2019)
COMMUNITY SCORE ★ 5 points
TOTAL DISCUSSIONS 1 comments
TOPICS & TECH STACK: