How we built automated support at Kickstarter
In this technical retrospective (2017), @selftext 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 ★ 16 points
TOTAL DISCUSSIONS 3 comments
I can see why you would want to spend as little time on support as possible (and actually the goal is to improve your internal workflows, which the article spends more time on) when your business model is founded upon taxing scammers 5% and ignoring users.
Sorry for the snide post, I'm just 0/3 now on kickstarter projects. All abandoned for years now, nothing delivered, no recourse, nobody cares, kickstarter aggressively ignores. It's beyond stupid and completely unsustainable.
Somehow "Sassy " seems like a weird name for something that's supposedly about "a deep, fundamental empathy with their users"
macro_name score
preorder_site 1.00
scam_projects 1.00
cc_chargeback 1.00