How I built a multi-platform app
In this technical retrospective (2016), @thebaer 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 Cloud & Mobile Era (2014–2019)
COMMUNITY SCORE 6 points
TOTAL DISCUSSIONS 2 comments
That's actually really interesting. Wonder if he updates the iOS app himself now.
Side note: I feel this comes up every time go is mentioned by why call it go? It is so hard to search for, especially if someone has titled their SO question with go instead of Golang