webmasterraj

Where you write down thoughts/what you did/next steps. I use text files, but it's a little hard to look back on afterwards in a cohesive way. I'm wondering if people use other ways?

I don't get a chance to work on my side project every day. So I've noticed an annoying 'reload' time when I come back to it after a few days, that it takes to figure out where I was and how to get started again. To help, I've found myself keeping a simple log in a text file with notes to myself. It's not great, and I'm sure there's a better way. (By log I mean something different than commit messages. It's more like a personal journal, with notes on what I did, where I left off and what I have to do next.)

Does you do something to optimize how quickly you get back into a project that you only get to work on occasionally? E.g. I have a friend who chats with Slackbot in a private room, though I'm not sure it's much better than a text file.

Sometimes, when I'm trying to get motivated to work on my own side project, I'll read blog posts by other people who finished a project and are recapping what they did. You know, the "here's my side project and how I did it" posts. As an example, I read this one recently from a guy who got vim to work with a mechanical typewriter: http://qqrs.github.io/blog/2013/05/03/vim-on-a-mechanical-typewriter/

This is one of those times I could use that motivation. Anyone seen good posts recapping side projects recently?

Tech stocks are crashing. Bill Gurley says we're at an inflection point, and investors are going to start looking at profitability instead of growth. Most of the unicorns in the $1B+ club have gotten their valuations by rapid growth, though not necessarily the profitable kind.

If things take a turn for the worse, and funding becomes hard to come by, which unicorns will have the hardest time getting to profitability?