How I Built a $600 / mo Product In One Day | kpkaiser.com
In this technical retrospective (2010), @hboon 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 Web 2.0 Genesis (2007–2013)
COMMUNITY SCORE ★ 8 points
TOTAL DISCUSSIONS 2 comments
Great read. I was surprised to see how much it was priced at. It would be really interesting to see the price set to iPhone app store levels for one month and compare adoption to income.
At the current ~40 sales per month, I would venture that the many many thousands of WP users would adopt a $1.99 version of this more readily than the current $15 price.
It appears wpplugins now take a 30% cut rather than the 10% mentioned in the article, which makes more sense. Plugin authors can also charge for a monthly support subscription. I'd be interested in knowing if that subscription dissuades many people from buying the plugins in the first place.