Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Write Code Every Day

ejohn.org

Post reply on HN
Print view View original

81–90 of 221 posts

Re: Write Code Every Day

#81

Post by munificent »

Arjuna wrote: post #48
munificent wrote: post #32

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…

Congratulations! This is a thing of great beauty. I would like to write an iOS-centric game development book; this is truly inspiring. Just curious... what are your self-publishing plans (if you don't mind discussing them)? What software do you use for writing?

> what are your self-publishing plans (if you don't mind discussing them)?

The book will remain freely available in web form in its entirety. When I put up the last chapter, that will include a nice redesign that should hopefully make it pleasant to read across most devices.

Soon after, I'm going to start working on an eBook and print version. I'm not sure how I'll do the eBook yet, but I'll do some investigation. The book is written in markdown, so it should be fairly straightforward to eBook-ify it.

For the print version, I'll be laying it out by hand with lots of love in InDesign. I was a designer before I turned to programming, and I've always wanted to typeset a full book. I didn't think I'd have to write it first to get the opportunity!

Sometime soon, I'll also contract out for a proofreading pass over the book. Each chapter has gone through a few revisions already, as well as numerous bug reports from eagle-eyed readers, but there's always mistakes. I'll pay out of pocket for it.

I'm purchasing my own ISBN. I'll put the eBook and print-on-demand version up on Amazon. I'm not sure if I'll sell it through other channels yet. I still have to look into it.

The best thing I did was start a mailing list when I was about halfway through the book (using MailChimp, who are swell). It's got over 2k subscribers now, so when the eBook and print versions are ready, I have an audience I can tell.

> What software do you use for writing?

Sublime Text. The first thing I did when I started the book was set up a very simple workflow. I have a Python script[2] that takes the markdown, transcludes the code snippets (which are in separate source files so they can be compiled and tests), and converts it to HTML.

I write in Sublime and then run the script to see the resulting output. I find seeing the prose in two different forms (markdown and styled HTML) helps me during the editing process. It's serves as a proxy for a fresh pair of eyes.

[2]: https://github.com/munificent/game-programming-patterns/blob...

Re: Write Code Every Day

#82

Post by ruffmuff »

munificent wrote: post #32

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…

How do I donate something to your cause to say thank you for the work you've already done (and for putting it online for free)? Paypal/Bitcoin would be easiest, but anything will do. :)

Re: Write Code Every Day

#83

Post by gdubs »

d55 wrote: post #63
gdubs wrote: post #2

This "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…

But what if you don't have some skill to work on? /:

Then you could make finding what you want to do with yourself a daily practice. Could be meditating, or a period of isolation -- walk in the woods, time in quite reflection...

Re: Write Code Every Day

#84

Post by munificent »

theycallmemorty wrote: post #79
munificent wrote: post #32

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…

> I've redesigned the site twice I chuckled to myself at this bit because it's the type of productive-but-utlimately-unnecessary task I'd find myself doing if I were trying to write a book. Not trying to be a downer, that's an impressive streak and I hope your book does well!

Yes, I have to work hard to limit my non-writing tinkering, so I timebox the design stuff pretty harshly.

I started the book four years ago, so the first design was unreadable on mobile devices (fixed position navigation will do that!). After a number of complaints, and the creation of Google Web Fonts, a mobile-friendly better design was a necessity.

I just finished another redesign that will launch when the last chapter is done. It's even more mobile friendly and has a front page that reflects the completed status of the book. It also just looks a hell of a lot better. :)

Re: Write Code Every Day

#86

Post by munificent »

ruffmuff wrote: post #82
munificent wrote: post #32

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…

How do I donate something to your cause to say thank you for the work you've already done (and for putting it online for free)? Paypal/Bitcoin would be easiest, but anything will do. :)

A thank you alone is enough!

If you want to back that up with cash, the best way will be to buy a copy of the print version when it's out. Part of the magic of self-publishing is that I get a very large cut of the sales of that, so it's a good way to say thanks. (And you get a physical book out it!)

Re: Write Code Every Day

#87

Post by munificent »

mhartl wrote: post #37
munificent wrote: post #32

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.

I worry about that a lot. But I think that brittleness may be what makes me work so hard to not break it.

Re: Write Code Every Day

#88

Post by munificent »

d55 wrote: post #62
munificent wrote: post #32

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 first pattern book without a mention of Christopher Alexander (:

Oh god, how did I omit that? A Pattern Language is seriously one of my all time favorite books.

Filed a bug: https://github.com/munificent/game-programming-patterns/issu...

Re: Write Code Every Day

#89

Post by munificent »

liyanage wrote: post #43
ds206 wrote: post #36

Earlier quoted context omitted.

I've read a few of your chapters and I think you're doing a great job. Keep it up!

Yes I read one of your chapters as well, very well done and I'll be buying the book when it comes out.

Thank you and thank you!

Re: Write Code Every Day

#90

Post by aiaf »

prezjordan wrote: post #77

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?
Post reply on HN