How I Built a Side Project
In this technical retrospective (2016), @lillukka 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 255 points
TOTAL DISCUSSIONS 94 comments
I sent a short list of questions to 1222 recipients.
Great!
The open rate of the email was 45,8%
That's excellent.
...and 27 people replied.
Oh. Oh dear.
~ 96% of respondents told that they would - or already have - recommended the tool for a friend or colleague.
96% of the people who are enthusiastic enough about the service to respond to an email would recommend the service, but the 97.8% of people didn't respond is by far the more important number. If the people who'd tried the app were a random sample of the population then 2.2% might be enough to suggest there's a valid premium business model there, but the people who tried the service weren't randomly selected - they were a self-selected group of people who are interested enough in user testing to sign up for the service. If you can't get a significant response from a group who are (alledgedly) interested in your type of product then you clearly have a big messaging problem.
For all the people saying Heroku is too expensive: a basic single server, 10M row database and SSL is around $50 a month on Heroku: https://www.heroku.com/pricing ↗
Personally, for the reduction in admin tasks (which I think people greatly underestimate), improved deploys and rollbacks, and improved uptime about $50 a month is completely worth it compared to a standard server.
I don't know why the monthly bill in the article is $250 though.
This goes along with a good site I saw mentioned in comments yesterday, https://www.goodui.org/ ↗. If your site was still up, I'd sign up. You might even go cheaper with something like a shared hosting solution, like webfaction. it's cheap, it's easy to setup stacks, you'd have plenty of space, and you don't have to manage your server.
Aside from the free nature of the app, I think what's missing was a consistent growth strategy. In your opinion 1/ how much would be a fair price for such a service 2/ which/who sales/marketing saas/specialists would have helped it attract customers 3/ what would be the next features appealing enought to convice users to try it, use it more frequently, and invite other, should this app continued to live
"To learn more about my users, I sent a short list of questions to 1222 recipients."
brilliant read, one thing I'd modify is ask some/all these questions on signup or login. Tweak enough questions and techniques to ask [0] so as not to discourage. This way you can gain more info as as people use/try/login.
[0] Must be numerous ways to gain info building it into actions of tool.