3 ms·
I'm basically going down the opposite path, and am learning how to more effectively use my printer for a variety of tasks. You can Doxygen your code into a .pd
by dragontamer 6y ago
I'm basically going down the opposite path, and am learning how to more effectively use my printer for a variety of tasks.
You can Doxygen your code into a .pdf, and then print off a reference copy of your API. Use a 2-hole punch with standard prong fasteners: and you've got a decent binding system (far superior to staples).
Just $15 for a 2-hole punch, $5 for 100x prong fasteners. From there, double-sided print from a laser-printer is pretty efficient.
----------
A Booklet of 100 pages can hold a surprising amount of information, and practically works as a 2nd (or 3rd) monitor for your productivity.
Learning to make __books__ out of your printer, by using a basic binding system (comb binders, 2-hole punch, or 3-hole binders) is a good skill to have. It really does improve your productivity.
- strombofulous 6y agoWhy do you find print better than an electronic version of the same thing? Having never tried it, I would assume your method is worse because it lacks features like easy editing and search.
- dragontamer 6y ago> Why do you find print better than an electronic version of the same thing? Because it converts desk-space into "screen space", so to speak. > easy editing A lot of things don't really change when you're coding. For example, APIs, or "vocabulary objects" of your code. But if you really need to edit some object that's changed, pull out a pencil and write it into the margins. Or print out the new page, and stick it into your book. No need to reprint everything. 2-hole punch + prong binder is easy to disassemble and reassemble. Comb-binder is a bit harder, but its a superior binding if you care about that. 3-hole punch is pretty much designed for easy editing: very easy to add and/or remove pages. But in all honesty, 3-hole punch is a terrible reading experience so I still prefer 2-hole punch and/or comb binders (even if they're harder to edit). > search You don't use the paper version to "search". (Though crude methods exist: dog-earing common pages or putting sticky notes / literal physical bookmarks into some pages). If you need to search, search on the computer for the material. Then, open up to the page you need in the physical book. Bam, now you have a reference and can use the screen-space on your monitor for something else. ---------- A dedicated reference page (such as OpenMP Reference Cards: https://www.openmp.org/wp-content/uploads/OpenMP-4.0-C.pdf https://www.openmp.org/wp-content/uploads/OpenMP-4.0-C.pdf) is of course best. Doxygen -> Latex isn't the best at automated layout, but it does get the job done. I mention it mostly because its "low effort" to convert code into a physical paper reference copy. If you really need a reference sheet, you should manually craft a nice reference sheet in MS Word, or HTML5, and print it out. Nothing beats hand-crafted effort, but the low-effort methodologies are still worth knowing.
- PascLeRasc 6y agodeleted
- dragontamer 6y ago> cost more than reading docs online A 10-ream costs $35 (5000 sheets of paper). Laserjet toner is 8000-pages for $100. I think you're overestimating the costs. > less portable I can carry the book outside and mark it up while the sun is shining overhead. I can walk out to my deck, eat some food and read the book on my deck's table. In contrast: I don't know of any laptop screen that has a decent amount of visibility in the open sun. Maybe you can get an e-ink reader that can read the documents, but e-ink isn't quite where I want the technology yet. (Its getting close, oh so very close... but not quite good enough to replicate paper yet). How are you reading your documents book in the park? Or on your deck? Or in your lawn? > harder to search Search on your computer. Then open up to the page in your book. Page numbers exist for a reason. Its not like CTRL-F stops working because you printed a physical copy.