Preparing to Code

I'm excited to pair program with Ward on Wednesday. Collecting some things in support of that project.

Where can we find room and Internet access?

Friday, I visited the Grand Hyatt to ask their staff for suggestions. Novo coffee on Glenarm seems to have a few tables to offer and is open all afternoon. The Inc! closest to Grand Hyatt closes pretty early. But the one on 16th St is open later and has more space too. Ward mentioned Fluid Coffee.

I have created many turtle geometry experiments and haven't discovered the right implementation yet. I imagine constructing turtle plugins with the idea of forking and comparing turtle drawings and the related code, but also forking and sharing implementations of such plugins. It begs questions about how to nudge and edit code along while nudging and editing the paragraphs interpreted by moving code.

Unit Conversion: lessons in scientific computing from a conversation with JPL scientist and coder: n-dimensional arrays and units as first class citizens.

Date Values and Date Ranges: <-- sprawling page, but I think this is the gist. Dates are actually moments in space-time. We get date problems wrong all the time by ignoring the space. Date ranges are distances in space-time. Telecommunications complicate matters by creating tunnels in space-time. Our collaborators can be in different spaces at the same time.

• expose simple step-by-step calculation

• adhere to convention established by earliest visualisations

• support multiple data discovery protocols until the best one surfaces

• evaluate off screen and asynchronously

• multiply instantiate to provide itterative calculation in the lineup

• optionally and usefully check units and apply conversion factors

• support closed-loop dynamic simulations (unimplemented)

See Pull Request