Hacker News Reader

PG, agree/disagree? i ask because this is an interesting contrast to what you've said about writing a crappy v1.0, then iterating on and improving it. but the two concepts aren't mutually exclusive, because maybe "crappy v1.0" can simply mean a well-engineered subset of your eventual goal.

View on HN

I guess that depends on how you define "crappy". If by "crappy" you mean "spartan" then sure. If by "crappy" you mean the code is bad, then you're only racking up technical debt, not making progress. ALWAYS start with the simplest solution that does the job.

Yet most people start with the most complex solution they can come up with, even though they don't know what they're solving yet.

Reply on news.ycombinator.com