I have a few ideas that have worked for me in practice. 1. Work 12 hours (or more) per day and use your energy levels wisely. The reality is (IMO): you're simp

I have a few ideas that have worked for me in practice. 1. Work 12 hours (or more) per day and use your energy levels wisely. The reality is (IMO): you're simply doing a 2 man job. I'd always start of coding, since I had the most energy then. In the evening, my brain would be beaten to a pulp and then I'd go the social route. Socially you suffer a bit because of it, but coding simply becomes impossible. If I felt tired the whole day, then I'd be social the whole day. If I'd feel energetic the whole day, then I'd code. 2. Get another person on-board to do the social stuff. I knew this one person who was very social and loved it. I like being social but this guy was infatuated with it. He did all the social things, so I could focus on coding. 3. Do it based on your mood There have been days that even when I was energetic, I didn't feel like coding or I was working on a thorny coding problem. To simply get some variety in my day, I'd switch to social activities (e.g. posting in Facebook groups). Note: I'd use Toggl for this stuff to ensure that I'd spend enough time on both. --- Full disclosure: I like replying to HN questions (see my history), but in this particular case I'm also replying in part because I have a very sligthly related issue [1]. It's unrelated enough to warrant it's own topic. So, dear HN'er, if you're interested in this then you might like my question as well (I could really use the help). [1, Ask HN: Diverging products: fork codebase, create config file or other option?] https://news.ycombinator.com/item?id=23562286 https://news.ycombinator.com/item?id=23562286