Live data from Hacker News

Write Code Every Day

ejohn.org

91–100 of 221 posts

Re: Write Code Every Day

#91

I 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…

Very good discipline in the article, and very good discipline in your plan too.

If you don't mind me asking - what's the point in writing a book about an area that you used to work in, but didn't want to going forward? (I assume you moved out of gaming if the domain was fading)

Re: Write Code Every Day

#92
post #90

I tried this a few months ago and failed miserably: https://medium.com/lessons-learned/ab219377be93 Really enjoyed your post, though. I think I might give it another shot from a different perspective.

Your link redirects to a login page?

Can't seem to reproduce that - it's just a Medium article. Could have something to do with Heartbleed if you've logged in before.

Re: Write Code Every Day

#93
This is exactly my approach on my side project, but rather than "write code every day" I say "make some progress every day". Simply because it's not a Open Source framework, but a wannabe product.

Re: Write Code Every Day

#95
post #24

On a slightly related note, I'm trying to impose a new behaviorist training on myself. I've never been one to listen to music when working, although I love music (as in member of two active bands, produced many albums love music). So now, I'm trying to do work in album-length increments. Put on the headphones, pick an album, and work on one task all the way through it. No breaks, no interruptions. It's kind of a Pomo…

If only I could find an entire album that I actually enjoy...

Re: Write Code Every Day

#96
post #37

I 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.

Another way to structure the chain is a chain of unbroken weeks, instead of days, especially for actions that stand a pretty good chance of being derailed by life. Like going to the gym. Mark a week as "checked off" if you hit the gym for at least 3 of the 7 days. That way you've got several "buffer days" to act as a cushion.

Re: Write Code Every Day

#97
post #33

Earlier quoted context omitted.

I'd agree with you if my primary desire were to improve my ability as a programmer. Unfortunately, at least at this time, it's not. My major concern is getting meaningful work done. I spend far too much time thinking and reading about technologies, techniques, and planning for the future - more time needs to be spent on actually implementing all the amazing stuff that you want to exist.

I agree. I have the habit of constantly learning, without producing. So I'll pick up side projects, suck the learning-marrow from their bones, and discard them without finishing. I have so little to show in terms of actual work product, which I am attempting to fix with a similar "don't break the chain" approach.

I have been in the same boat as you when it comes to side projects, but I'm curious about your use of the metaphor of "sucking the marrow from the bones" because that metaphor is typically used to describe completion to an extreme. For example, if "eating an animal" was your metaphor for working on a side project, I think that a more apt extension to that metaphor would be "leaving meat on the bone" rather than "sucking the marrow from the bones". However your metaphor refers to the marrow as "learning-marrow" which confuses the larger metaphor that is "eating an animal".

Have I completely misunderstood the extended metaphor you were trying to use?

Re: Write Code Every Day

#98

I 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…

[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?

Re: Write Code Every Day

#99
post #41
post #12

Earlier quoted context omitted.

+1. I've been using Joe's Goals [1] to track my daily goals since I learned about it on Life Hacker years ago. Can't recommend enough. [1] http://www.joesgoals.com/index.cfm

HabitRPG works much the same way, tracking activities to form habits. https://habitrpg.com/

I use something called Lift, but HabitRPG seems more appealing with its game theme.

Re: Write Code Every Day

#100
post #19

Earlier quoted context omitted.

no side effects from the modafinil? I take them very rarely pretty much only when it's of the utmost importance that something gets done by a deadline and even then i'll only take a half or a quarter.

I used to take 8 modafinil / day but have been able to bring my wakefulness back to what I feel is going to be normal for me without medication. I did experience one side effect -- paranoia. I became really paranoid about what my spouse was doing behind my back. I knew that there was nothing going on though, so I was able to finally make the call to get my doctor to take me off the medication. I'd imagine the situati…

8 a day damn i would be up for a month.
Post reply on HN