How I built forlater.email, my first big side project
In this technical retrospective (2021), @icy shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
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.
CATEGORY Frugal Engineering →
HISTORICAL ERA Pandemic Bubble (2020–2022)
COMMUNITY SCORE 130 points
TOTAL DISCUSSIONS 25 comments
Great one. Planning to write one such for my own service that I built - https://closetab.email ↗ (delivers a weekly digest of bookmarks to my inbox, every monday morning)
Because the biggest problem with bookmarking is forgetting it forever after ;)
I think the subject line can be used for settings while still keeping things stateless, e.g arial dark or like a preset name ad.
I hated Pocket too. I already used RSS reader, so, I ended up building https://reading.ashishb.net ↗ that creates an RSS feed of articles you add. And yeah, it has a readable mode turned on by default.
Emails are the perfect tool for that, but I got tired of opening my email client to email myself and built an app instead : https://boomerang-app.io ↗ . I am using it mainly to save HN link as well :)
I've been sending text html emails for my blogletter for over a year now. The single biggest struggle point is the spam filters in gmail/outlook/others which just render my emails waste for majority of the subscribers.
Do you face the same?