Very fast. Let me explain. 

I work in 2 modes: (A) At the computer and (B) Away from the computer. 

When I'm in Mode A at the computer, I'm cranking out lines of code, testing, revising, testing, revising, etc. This process must be very fast. Several hundred lines of code (or whatever) in less than an hour. A complete cycle in less than a couple of hours. My guideline is that if I'm not working that fast, then I must not be prepared to work that fast, so I don't deserve to be at the computer. I should be in mode (B). 

Mode B is generally much slower. Reviewing code, specs, or notes. Refactoring code. Laying things out with pen and paper. When I have enough work clearly laid out, I know it's time to get back to the computer and return to Mode A. 

The most important thing for me in Mode A is to see results, any results, quickly and often. It doesn't matter how correct anything is, just as long as it's progress (or sometimes, reverse progress). I like to think of programming as making incremental progress in micro jumps, evaluate where I'm at, and go for the next micro jump. 

Some of the best advice I ever got was from a prolific artist friend of mine who claimed, "I paint every day." So I started coding every day. But that wasn't enough. Now I make progress every day. 

There are many definitions of progress. Sometimes I copy a few hundred lines of code, make a few changes, spit out a new app, and then start applying micro changes. Other times I decide that I need to see today and find a way to get there. Things don't always work out as planned, but that's OK. As long as tomorrow's starting point is beyond today's, I'm satisfied. 

That's my definition of fast. Not sure that was what you were asking, but I hope that paints you an accurate picture. 

July 24, 2010

***

This is Number 53 out of 256 entries in my new ebook, "The Best of edw519, A Top Hacker News Contributor".  You can preview the Table of Contents and Chapter 1 for free and purchase the whole book for $2.56.  Check it out at http://www.scribd.com/doc/52729281/The-Best-Of-edw519

***

Over the years, I've received lots of favorable feedback about my comments on Hacker News.  Some have suggested that I blog or even write a book.  I always resisted because I thought that more writing would take time away from my software, which I've always considered more important.

I started this blog last year, but found that I really wasn't that well suited to the medium.  I never found a way to set aside regular time, so I ended up posting old Hacker News posts instead.  The feedback, understandably, has been lukewarm.

Then when I found out about the micro-priced ebook phenomenom, it hit me.  Why not take my favorite Hacker News contributions, edit them into a micro-priced ebook, and sell it on-line.  Even better, it gave me a chance to write an app to do it for me.  (You know us hackers: any excuse for a fun weekend project).

I describe the process I went through a little more in the Forward of the ebook.  I ended up with my 256 favorite entries and decided to sell it on Scribd.  You can read the Table of Contents, Forward, and Chapter 1 for free, then purchase the pdf for $2.56 if you want to read more.  (I know, very Knuth-inspired.)

I intend to print hard copies to distribute to family, friends, and customers.  Maybe even make the software available so that others can turn their Hacker News comments into their own ebooks.

Just a little experiment.  Who knows where it may lead...

Check it out at