/
22.08.2020 at 05:49 pm
Cuttings

Decoding Code Specimens

Dissect code like 18th century scientists do their biological specimens.

... But then it hit me. Code is not literature and we are not readers. Rather, interesting pieces of code are specimens and we are naturalists. So instead of trying to pick out a piece of code and reading it and then discussing it like a bunch of Comp Lit. grad students, I think a better model is for one of us to play the role of a 19th century naturalist returning from a trip to some exotic island to present to the local scientific society a discussion of the crazy beetles they found: "Look at the antenna on this monster! They look incredibly ungainly but the male of the species can use these to kill small frogs in whose carcass the females lay their eggs."

The point of such a presentation is to take a piece of code that the presenter has understood deeply and for them to help the audience understand the core ideas by pointing them out amidst the layers of evolutionary detritus (a.k.a. kluges) that are also part of almost all code. One reasonable approach might be to show the real code and then to show a stripped down reimplementation of just the key bits, kind of like a biologist staining a specimen to make various features easier to discern.

Peter Seibel's analogy on the good (but difficult to maintain) habit of reading code.


Filed under:
#
Words: 234 words approx.
Time to read: 0.94 mins (at 250 wpm)
Keywords:
, , , , , , , , ,

Other suggested posts

  1. 14.09.2019 at 12:00 am / Narratives Hold
  2. 14.12.2018 at 03:09 pm / Recursion, Succinctly Put
  3. 21.08.2018 at 10:59 am / Roses as Time
  4. 16.12.2017 at 12:00 am / Sketch, Draft, Craft
  5. 20.06.2015 at 12:00 am / Mike Tyson on (His) Lawyers
  6. 29.11.2013 at 12:00 am / 勉強 - Straining Studious Strength
  7. 20.04.2012 at 12:00 am / A Misty Morgue's Bat
  8. 17.03.2012 at 12:00 am / Upper and Lower Hengsha
  9. 16.08.2010 at 12:00 am / You Have Reason
© Wan Zafran. See disclaimer.