How I built my first Android Game
In this technical retrospective (2015), @skazka16 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 56 points
TOTAL DISCUSSIONS 19 comments
Interesting take on creativity. Applying the scientific method to more and more disciplines seems to be a trend lately.
I agree with the reasoning, but am curious how iterative creativity can be applied on the individual scale for projects that take longer than a month and a half to complete.
I am the author of this article. You can download the game from Play store:
https://play.google.com/store/apps/details?id=com.halftspgames.romeorocket ↗
What's with all the kukuruku articles on the front page? Where did this site come from?
Any link (or bunch of links) for specific tutorial that you have followed?