How I built 7books in under 4 weeks
In this technical retrospective (2010), @revorad 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 ★ 172 points
TOTAL DISCUSSIONS 76 comments
Holy wow - thank you so much everyone for your feedback and comments! I leave for 2 hours (taking a tour of Zappos in Vegas, amazing and life changing btw) and this thing goes crazy!
I've enabled billing in appengine as I'm nearly over quota:
http://imgur.com/SN0WQ.png
If anyone has any tips to optimise my outgoing bandwidth it would be very much appreciated! Hopefully I caught it in time to avoid any real outages. I'll try and keep an eye on it though.
Ok - right off to trawl through the comments and responses and reply!
Thank you all :)
Great job learning a language (and an infrastructure) with such speed!
I've been building something with a similar aim on and off for a long time now, and it's neat to see in the comments that there are at least three others already out there.
I wonder if there is something that will lead to more widespread awareness/adoption of sites like these. Or are we better off trying to pick a target market smaller than [all book readers]?
Some good food for thought as I try and finally finish my own entrant into the space.
This is really great. I love the concept and simplicity.
Here are some suggestions:
1. Use the Amazon API to autosuggest book titles and author names.
2. Normalize the lists. That is, count up which books are recommended the most and use those statistics to recommend books.
3. List similar lists on each list :) Lists that list the same books might be related. If they list two or more of the same books, they're probably related.
But even if you don't change a thing, it's still a great little project!
Jesus, 4 weeks? That's awesome. I've been learning on and off for a few years now, and have recently buckled down to finally get something done. What are some lessons you learned for building your next project? Also, it seems like you've got a good eye for design. With a bit more practice and experience, you could likely make some great looking sites. It certainly looks a lot better than sites I've seen made by more seasoned coders.
Suggestions:
1) I'm not sure whether you're using Amazon referral links. You can show the book cover next to the title linking it to the amazon using the associate tag. It will fetch you some decent money I believe if someone buys the books using the links. Have never used but read about this in Stackoverflow.
2) You can use amazon.com/books instead of amazon.com in the Stuck? message link when adding a new book.
Great work!!