|
|
|
|
|
|
by davidajackson
2264 days ago
|
|
|
IMO I have found that not working on your project is one of two things, or both: 1. The project isn't working, and you subconsciously know it but don't want to admit it. 2. You need to, but don't want to, do the next most important task for your startup. So you do other things to procrastinate. According to the article Sam Altman calls the latter 'fake work', which sounds like a good description to me. https://tech.co/news/sam-altman-y-combinator-5-signs-youre-f... >> TLDR "Fake work does not count and will still get you a failed startup no matter how intensely you do it" So the sooner you can figure out which point it is the sooner you know how to, or how not to, move forward. Probably the most useful thing is just to imagine how much more interesting things will be once you're at the next stage. |
|
|