3 ms·
> Then as stated in the article, only work on the side project for an hour a day over 365 days. Time is on your side and it's OK if it takes a year to get to an
by chaostheory 8y ago
> Then as stated in the article, only work on the side project for an hour a day over 365 days. Time is on your side and it's OK if it takes a year to get to an MVP. Look at Stardew Valley, for example.
That's actually not true. According to the GQ interview:
"It took him four and a half years to design, program, animate, draw, compose, record, and write everything in the game, working 12-hour days, seven days a week."
Stardew Valley is the antithesis to the article. Eric Barone worked full time on the game while his girlfriend supported him.
https://www.gq.com/story/stardew-valley-eric-barone-profile https://www.gq.com/story/stardew-valley-eric-barone-profile
imo if you're programming, it'll take a lot longer to finish anything if you're only doing it in 1 hour daily increments vs a few hours in a single day a week. Flow is important. That's not counting the mental stamina that's been drained by the day job.
The other scenario that can happen is that your performance at your day job will suffer, if you continue programming after your typical 10-14 hour programmer work shift.
- movedx 8y agoYou misunderstand me. I never said it took him 12 months to complete the game. I never stated he worked on the game on the side. My point is simply that it's OK for something simple to take a long time; it's OK to work on something over a long period of time, on the side or otherwise. If you want to make something and it takes five years: OK. If you want to make something and it takes five months: OK. The point is: do it, and do it by managing time better and staying focused.