I think it's best to focus on writing less code per day.

(edit: I mean that in the sense of making your code more efficient)

"I would have written a shorter letter, but I did not have the time."

--Blaise Pascal (http://en.wikiquote.org/wiki/Blaise_Pascal)

That's my goal too, but often I find that the best way to write good short code is to write a shitty, longer version first.

"Write one to throw away" is the quote I remember reading from someone, and I find it applies well to some of the code I write (thankfully not all).

"This morning I took out a comma and this afternoon I put it back in again." - Oscar Wilde

This is very often also true of writing.

Using Jarnal[0] on OS X with a Bamboo tablet[1] is a great way to store your thoughts while thinking about a problem.

[0]: http://www.dklevine.com/general/software/tc1000/jarnal.htm

[1]: http://www.amazon.com/Wacom-Bamboo-Create-Tablet-CTH670/dp/B...

I'm sure there's a good amount of overlap applicable to any creative process.

Yeah, that's what I was thinking. It seems the principles could be applied well. Though I think, the principles are definitely directed toward an introvert's preferred style of working.

Yes, absolutely. Especially with side 1, knowledge, this just translates to using a combination of a top-down and bottom-up approach as opposed to a pure bottom-up approach.