schmudde

> How do we get public perception and public discussion of energy and climate centered around evidence-grounded models, instead of tips, soundbites, factoids, and emotional rhetoric?

> Furthermore, the point of embedding a model is that the reader can explore scenarios within the context of the document. This requires tools for authoring “dynamic documents” — documents whose contents change as the reader explores the model.

I've long-appreciated Victor's perspective in this article. But the general public understands very little about how models work and what they promise. I've seen little evidence that making them explorable in the New York Times has done much to move the public (and thus lawmakers) in the United States to move on gun violence or climate change.

Technologists can build better tools for storytellers and whistle-blowers. This mostly involves facilitating the disclosure, formatting (cleaning), and analysis of data.

What do you use for version control? Do you version your data as well?

Wow. This is the perfectly self-referential Wikipedia entry that post-post-modernist plebs want and deserve.

I grew up with Throbbing Gristle. Genesis has a complicated legacy of control and manipulation that was part of their music and art. They lived their work, which is part of what made it so compelling. Industrial music for industrial people - more prophetic than insane.

I suppose The Well is one option: https://www.well.com/. Decades of ongoing discussion.

People in tech undervalue what older communities offer. If the discussion group hasn't become a wasteland after a few years, there is something there.

It's possible but requires some foresight and strategy. Images are the first problem - they're stored in blobs. Small changes in graphics can create meaningless commits.

Data is the second problem - you usually can't run a notebook without it. If the notebook transforms data over time, it can be a real issue.

Here's a pretty complete run down of the first problem, the .ipynb itself: https://nextjournal.com/schmudde/how-to-version-control-jupy...

An integrated solution that versions data, the notebook, and the computational environment (collaborators will make changes over time) is the ideal collaborative platform.

In my experience, remote work takes quite a bit of organization which often defaults to hierarchy. Leaner organizations with less management struggle with this. It partially depends on where you want to put your money as an organization.

Absolutely. Point #4 offers a more sane alternative.

ClojureCL has already been mentioned, but I found the author's interview on the Defn podcast particularly enlightening: https://soundcloud.com/defn-771544745/defn-24-v3

Yeah, I was a CompuServe guy, but it was pretty innovative and looked great at the time.

"HTML is the kind of thing that can only be loved by a computer scientist. Yes, it expresses the underlying structure of a document, but documents are more than just structured text databases; they have visual impact. HTML totally eliminates any visual creativity that a document’s designer might have. — Roy Smith, 1993"

Seems like an odd request in 1993. Sure, Prodigy had visual impact, but it was pretty hard to read. HTML's starkness seems in part due to the fact that styling options were limited by the technology and the ones that existed were easily abused.

Writing long sentences as headers (<h1>) or all-caps (caps-lock) were styling options at the time... and often misunderstood and abused.

/ü

What do you mean by 'fix'? Who set it? I understand the US privatized its reserve, but I don't understand how the market seems so out-of-step with reality. What about other markets? EU, SE Asia - are they seeing the same low prices?