2 ms·
I experienced exactly the same, when I started bringing pen and paper to bus driving to/from work and code on paper. It is very different experience from codin
by ajuc 17y ago
I experienced exactly the same, when I started bringing pen and paper to bus driving to/from work and code on paper.
It is very different experience from coding with computer, and it results in better quality code, because I can't just run to "ensure" it works, I have to think it throught.
Also I tend to write less code, when each time I forget to add check before some line I have to rewrite whole function by hand.
In home I just check documentation for apis I didn't remembered, and type code into computer. Almost always it works after a few minutes of simple variable misspelings etc corrected.
Of course, this won't work so good with bloat oriented languages :)
- nfnaaron 17y agoDoes anyone use something like Warnier/Orr diagrams for on-paper procedural code, or do you just code/pseudo-code in the target language? http://varatek.com/warnierorr.html http://varatek.com/warnierorr.html http://varatek.com/warnierorr_diagrams.html http://varatek.com/warnierorr_diagrams.html
- anonjon 17y agoI don't know Warnier/Orr diagrams. I do, however, draw pictures and diagrams to help me reason through stuff. It is one of the big advantages to writing code on paper. I find tools like visio tend to get in my way (I spend too much time fussing with getting lines connected and not enough time sketching my idea (it also never quite looks right)). I actually like it so much I was considering buying a bamboo tablet so I can include diagrams in my documentation (and not kill so many trees!). Of course, then I'd have to write an emacs plugin to call up inkscape (unless anyone has a better 'sketching' type of program) and insert a hyper-link to the saved file in the docs folder.