4 ms·
No, the author is actually writing code using pen and paper. It's not just a high-level or organisational sketch. It's not just planning. What happens at the co
by stan_rogers 5y ago
No, the author is actually writing code using pen and paper. It's not just a high-level or organisational sketch. It's not just planning. What happens at the computer afterwards can best be described as transcription and debugging.
- nkozyra 5y agoI find it pretty unlikely that this entry: > I opened my laptop, created a new Github repository, typed in the code, added some tests and wrote the README. It was probably all done in 4 or 5 hours of concentrated work. Means handwritten code verbatim went into the repo. The focus on iteration is great - it would be unusual to stop at this point. But if we say the written word is canon, my response is that's inefficient. It is indeed the planning that is most valuable when putting pen to paper.
- thevinter 5y agoThis semantic discussion seem pretty pointless as it doesn't focus on the whole idea behind the article. It really doesn't matter what definition for "writing" you use.
- kragen 5y agoNo, she probably kept editing it after she typed it in; aside from debugging, I always find things I can improve when I'm typing in code I wrote on paper first, so I do. But that doesn't mean that what she wrote on paper wasn't the code for the module. I mean, you can see some of it in her photos. It's syntactically valid C and Ruby code, semicolons and all.