nearbygoogler
Joined 3 years ago
Karma
15
Submissions
5
Member since
Jan 30
Recent submissions
Comment · 2 years ago
Comment · 2 years ago
1. Print the source code in a micro-barcode in a physical appendix.
2. Make the first exercise in all books be to code a simple barcode image interpreter. And just include the walkthrough and source as typed text.
You should be able to get a few MB on a page easily. Future proof as long as there are cameras on phones.
Comment · 3 years ago
I’m with you on the dongle issues, it’s a tremendous pain to find consistently working equipment that allows charging, in-line mic, and durability.
That said, I hate BT more and have been using the same Bose QC20 wired earbuds and Belkin adapters for 4+ years. There are semi-decent options out there.
Comment · 3 years ago
And of course search and remove for any other public dev copies of the site. Good luck!
Comment · 3 years ago
Be sure to request that the old version of your website be removed from Google search. Hint: old.yourdomain still shows the person.
In another example, take the Machine Identification Codes (MIC) tracing dots that basic home printers can produce [2], (I bet the publishing industry could do much better to produce a high density grid.)
These dots have a stated diameter of 0.1 mm, and on an 8”x10” area one could get a grid of 80x25.4x25.4x(1/0.1mm)x(1/0.1mm)= ~5.1M dots.(wikipedia claims larger spacing, but that must be the protocol, printing itself allows for highly precise positioning) And that’s just for one color. Use CMYK (you could imagine a sub-project to design a 8bit color based dot scheme) and compression, and even with ECC losses I can see a few MB of encoded source per page being possible. And writing that decoder would be a great exercise!
[1]: https://www.docucopies.com/image-resolution/
[2]: https://en.m.wikipedia.org/wiki/Machine_Identification_Code