3 ms·
> plenty of new project folders, draft blog posts, plans written down, database schemas, etc - but no shipped results. This is the main issue for me. Starting a
by euroderf 3y ago
> plenty of new project folders, draft blog posts, plans written down, database schemas, etc - but no shipped results. This is the main issue for me. Starting a project is easy, working on it is the issue!
You've done the fun parts. Isn't that enough to hit a good ratio of satisfaction-to-time-consumed ?
- corobo 3y agoUnfortunately satisfaction-to-time-consumed doesn't pay any bills or fill the cupboards with food In the ideal world aye absolutely, in this reality the time was wasted
- euroderf 3y agoNot to quibble, but let's face it then, that GitHub (et al.) is chock full of evidence of time wasted. False starts galore.
- corobo 3y agoDepends on the creator really. It's a waste of time for me personally because I'm supposed to be grinding down some debts, paying the bills, and making sure there's food on the table. As I'm working freelance and billing hourly anything that doesn't earn cash directly or have the potential to be a new income source takes resources away from that goal. Once my finances are more stable I'll be much more free to tinker with fun projects rather than focusing on potential business/income projects. To be a bit more clear I only mean it's timewasting for me, not for humanity as a whole! I highly encourage anyone without my current constraints to code stuff for the fun of it without worrying about false starts or failed projects! :)