Write Code Every Day
111–120 of 221 posts
Re: Write Code Every Day
#112Yeah...no.
Re: Write Code Every Day
#113I am a total convert to the "don't break the chain" idea. I started writing a book on game programming[1] about four years ago. At the time, I was working at EA, miserable, and highly motivated to have the book done so it could help pad my resume. I got a book deal (O'Reilly) then, when that fell through, another (Apress). I had a real writing schedule, and a very supportive wife, and I would work on it for hours at…
The "don't break the chain" rule is brittle: if you do break the chain, your motivation can crater. I think [Beeminder]( http://beeminder.com/ ) has a clever solution to this problem; it gives you a way to track and enforce your goals while being robust to the occasional lapse.
EDIT: for example here are my current widgets for the My Chains app on android: https://db.tt/pYRrrPZs you'll notice they're pretty quick and easy, but there are quite a few of them. This gives me a tremendous sense of achievement and progress which has been invaluable in the quest to form better habits.
Re: Write Code Every Day
#114Re: Write Code Every Day
#115Is your side project really this important to you? It's your source of identity and self-worth? I say: take three months off from even touching a text editor and practice guitar every day. I think my system leads to happier, healthier human beings.
It's the same with writers who write every day, no matter how little, to get into the rhythm and to constantly improve.
Also, doing something every day, doesn't imply neglecting other parts of your life. It just means constantly giving to something you care about.
Re: Write Code Every Day
#116This "don't break the chain" approach has worked extremely well for me, particularly during busy periods of high stress. I first learned about it in my college writing classes, where you're supposed to write something, anything, meaningless jibberish even, every single morning. Recently I read about Seinfeld using this approach to great successs. Every day he works on material, and puts a big, fat, "X" on the calenda…
1. http://www.reddit.com/r/IAmA/comments/1ujvrg/jerry_seinfeld_...
Re: Write Code Every Day
#117[1]http://www.paulgraham.com/makersschedule.html
Will need to change my attitude and get more done. Good piece.
Re: Write Code Every Day
#118Earlier quoted context omitted.
[HabitRPG]( http://habitrpg.com ) is totally awesome for this, a great motivator. You can setup "Dailies" so that when you're done writing your daily 500 words, you just check it off. Or set it up as a habit and give yourself a "+" whenever you get a new chapter done. I use it all the time for just these purposes.
This is brilliant. Thanks! Are there any other similar apps out there?
Far more minimalist. Just a calendar and mark, but I can set reminders and view my overall progress.
Re: Write Code Every Day
#119I am a total convert to the "don't break the chain" idea. I started writing a book on game programming[1] about four years ago. At the time, I was working at EA, miserable, and highly motivated to have the book done so it could help pad my resume. I got a book deal (O'Reilly) then, when that fell through, another (Apress). I had a real writing schedule, and a very supportive wife, and I would work on it for hours at…
Hey I'd just like to tell you that your site is an awesome resource and was useful to me as a student when I was talking my OO design courses. As someone with a gamedev hobby background your site made learning about patterns much easier for me. I will be sure to buy the book when it comes out. Thanks for putting in the hard work and making it available.
> As someone with a gamedev hobby background your site made learning about patterns much easier for me.
This is really reassuring to hear. One of my hopes with the book was that framing architecture in terms of games (which are graphically and conceptually very concrete) would make it easier to understand the more abstract concepts it's about.
Re: Write Code Every Day
#120I am a total convert to the "don't break the chain" idea. I started writing a book on game programming[1] about four years ago. At the time, I was working at EA, miserable, and highly motivated to have the book done so it could help pad my resume. I got a book deal (O'Reilly) then, when that fell through, another (Apress). I had a real writing schedule, and a very supportive wife, and I would work on it for hours at…