4 ms·
"I would do one week of code, then spend the following week tweeting / blog posting about what I shipped — then repeat" This right here is a very important org
by luthfur 6y ago
"I would do one week of code, then spend the following week tweeting / blog posting about what I shipped — then repeat"
This right here is a very important organizing principle for indie devs. It's more effective than say doing both coding and promotion in parallel by dividing the the day into two.
- geniium 6y agoThis is very interesting IMHO !
- odonnellryan 6y agoThis works for larger companies and larger teams, too.
- cercatrova 6y agoIn contrast, splitting the day helps to pivot more easily. I've had situations where I thought I wanted to work on a certain feature but when I talked about it, people didn't want that feature. So if I spent a week implementing it, it would have been a waste of my time.
- coffee 6y agoReverse your process. Talk about it to people first, then work on a feature they need (in aggregate).
- eloff 6y agoI think I would prefer to code for the first half of the day, and market for the last half as my concentration wanes.
- arunaugustine 6y agoI have tried that in my work at my startup and failed. Alternating days did not work either. Jon's recommendation about alternating weeks is what I am going to try next.
- eloff 6y agoInteresting, what went wrong when you tried that? I'm expecting to be in your shoes soon, and I currently have to balance a part time job with writing the software for my startup. I'd love to learn from your experience.