How I Built 180 Websites in 180 days and became a YC Fellowship Founder
In this technical retrospective (2016), @jenniferDewalt 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 ★ 72 points
TOTAL DISCUSSIONS 29 comments
I am deeply encouraged by your article. Surprisingly! I was thinking of doing the same thing prior to reading your article, which is, as part of my 100 day of code challenge to build a website every day and GitHub it. I guess the reason for my procrastination is being afraid of using GitHub, my lack of javascript knowledge & I barely know any design. Your input is definitely helpful! I really want to start being proficient in those areas mentioned. Also what learning resource would you recommend for javascript front & back end, web/application design, UX design and better grips on Github!
Hello, great job, I started following you first a few months back. My questions are,A: if you had to start all over again, what would you do differently. B: how did you decide on what to build each day in those 180 days. Last and this is the most important, I think learning by doing is the best way, is there a way where your experiences could be optimized for a newbie, where he/she could start from day one, build something and learn a specific part of a technology, and all the way to the end.
This is a really amazing endeavour! Great job! I really like Coded and Electro Bounce. A couple questions: Could you provide some more details about individual projects (frameworks used, any source info)? Also, how long on average did you spend on each project? Finally, what's your favorite project?
For someone who struggles with the design side of making websites, this is inspirational. I guess the takeaway here is just to practice, practice, practice.
Congrats to your achievements, Jennifer. I heard of you previously from Pieter Levels (12 startups in 12 months). You guys are my role models!