> That's written by an oddly highly motivated individual.
On the contrary. Sometimes I struggle with attention or get hyperfocussed on a specific problem, so I use these to keep myself in check. I fail most of the time, still, just a little bit less often.
I can't edit, so will post here: please read the note before commenting (it's short), a lot of context is missing in this quick comment.
Apologies, I should've put this phrase in more context. I agree with most of the comments, even the snarky ones, but I didn't express what I meant well enough.
Lmao. HN people don't want to grind for years to solve tough problems. They want to find some 'hack' or side-trick to bypass everything. But the reality is some problems take a long time to solve. How long do you think Bitcoin took to write? It wasn't 2 weeks.
Sorry, it wasn't my intention to make you feel harassed. Your advice probably makes a lot of sense for people who like to release many smaller products. Scope creep and extreme complexity are problems I've struggled with myself, and I often find it hard to start with the most basic deliverable rather than a vision that is much further along. I still have a lot to learn and I think these things are important problems for HN-type people.
Thanks, I appreciate that. As much as many people here didn't seem to have read the article or the note I linked, I should've phrased it differently so the context was apparent.
- 2 hours for a PoC
- 2 days for a prototype you can share
- 2 weeks for something actually useful
I put together some notes on the subject here: https://untested.sonnet.io/notes/2-2-2-project-scoping-techn...