Live data from Hacker News

How I Write Code: Pen and Paper

noteflakes.com

1–10 of 110 posts

Re: How I Write Code: Pen and Paper

#5

Nothing wrong with this, but the analogy at the end about bikes is so hopelessly tortured it's comical.

It's actually a very quick, useful reminder for me that 'hey, there's this other creative medium for designing things', but wow, you weren't kidding about the analogy.

There's something there, I think, but it would have been much better without the bit about bikeshedding, or reordered.

Re: How I Write Code: Pen and Paper

#7
I do this for things that require a lot of thought, but I tend to do it with pseudo code and little scribbles on the side (tables of variable state for loop count 1..x, etc) and not worry too much about syntax, scope, and so on. Usually that gets to a point where I can put the paper down and try it with real code.

Re: How I Write Code: Pen and Paper

#8
It's something that I'm still trying to force myself to do. I do know that I'm more productive away from the computer. But it's so tempting to just tweak, compile, test, iterate... I generally use pen and paper when I'm stuck and require deeper thinking.

Also, a lot of the work of a programmer consists in understanding existing code. You need the computer for that.

Re: How I Write Code: Pen and Paper

#9
I've never really had success doing concept work of any kind with pen and paper. Especially writing, but even diagramming. If I need to step back and work with ideas abstractly, the paper medium is still going to get in the way at least as much as the digital text does. What I really have to do is keep it all conceptual in my mind; that's the only medium that's truly unopinionated and flexible.

Paper/whiteboarding is more for communication to others, in my experience

Post reply on HN