3 ms·
It's not clear to me from this article if the author has shipped a version of those projects which are "almost done", or whether they are closed sourced "produc
by bsnnkv 2y ago
It's not clear to me from this article if the author has shipped a version of those projects which are "almost done", or whether they are closed sourced "product"-type projects or edu source projects where all of the commits and progress are public.
I wrote earlier this week on HN[1] about my very recent experience trying to ship _something_ (in the "product" category) to alpha testers in <1d and to an open beta in <7d, and it's something I recommend highly for people who are stuck wanting to go from "almost done" to "done" before shipping.
There is so much valuable feedback to be gained by shipping _something_ as soon as possible, and often just the act of getting that feedback goes a long way towards breathing fresh life into a project you might be starting to feel a little burnt out on.
[1]: https://news.ycombinator.com/item?id=42307710 https://news.ycombinator.com/item?id=42307710
- mlsu 2y agoThings kinda changed for me when I realized that 'discipline' actually should refer to scope. what's fun about side projects is that the scope is unconstrained. you work on whatever you want to work on. you change scope at any time. I found it helpful to explicitly think about the scope of my side projects. to answer the question "what will I ship when this is done." The answer is, of course, that it's never done -- that's because the scope can change at any time. the solution is to keep the lofty ideal very large but greatly cut the scope of the intermediate steps. the answer isn't discipline of "finish it" -- it's the discipline to "scope it."