How I built my first side project: Tubee, in 2017
In this technical retrospective (2025), @tomy0000000 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 Post-ZIRP & AI (2023–2026)
COMMUNITY SCORE ★ 6 points
TOTAL DISCUSSIONS 1 comments
In 2017, long before AI tools like ChatGPT, I built Tubee—a platform that tracks YouTube channels, delivers real-time updates, and organizes playlists. No AI, no shortcuts—just code, APIs, and figuring everything out from scratch.
I wrote about the journey, the tech stack, the trade-offs, and lessons learned. I’d love feedback on both the project itself and the way I wrote about it—what resonates, what could be clearer.