michael_j_ward

Who is "we"?

> Dealing with every possible source of non-determinism, re-writing services to be testable/sans-IO [2], etc. takes a lot of engineering effort.

Are there public examples of what such a re-write looks like?

Also, are you working at a rust shop that's developing this way?

Final Note, TigerBeetle is another product that was written this way.

From the abstract, it sounds more like a toolkit for "Interactive / Hypermedia" papers. The paper itself is still dead.

I was hoping more for "Living" as in "active, uncertain, will grow over time".

A toolkit for expressing the research from beginning to the end - the state of the world as you understand it, highlighting the key uncertainties and experiments, and mechanisms for viewing the history.

As a motivating example for the type of "living research paper" that I'm thinking of, think of long-running software design decisions a la the implementation of `async/await` in rust.

And in the context of discussing "whole word" vs "phonetic" systems of learning the English language, it seems like outright deception.

Pointing out a few outliers in such a large system like the English Language and using them to justify reclassifying the entire thing is braindead.

It's an alphabetic writing system where the letters largely correspond to sounds, in contrast to logographic writing system where the symbol corresponds to the entire word (like Chinese or Japan).

Yes, there are special rules and outliers that you need to learn in English, but it seems absurd to not classify it as phonetic because it's not purely phonetic. This is doubly so when discussing phonetic vs whole-word learning systems, as is the topic with "Sold a Story".

If you don't mind sharing, what grade-level, decade, location were you taught this?

The key part about the pizza example is the demonstration of mathematical thinking completely disparate from what I experienced at a Catholic high-school in Chicago during the 2000s.

Despite seeing myself almost precisely described in that video and the original article, and despite having been diagnosed with ADHD as a college student...

It's hard for me to believe that there exists persons that won't / don't identify with that description, and thus the cause of my executive dysfunction isn't ADHD, but just a failure to cultivate habits of discipline.

Having suffered through learning highly configurable software tools independently enough times, I agree completely with "digesting one or few commands" at a time works better for me too.

Spitballing:

We could probably make a general solution for organically producing "learning guide" if power users 1) share their custom configurations and share the frequencies of commands they use.

Start with the general configuration, knowing nothing about the commands the tool offers. The learning guide is just a queue of "here's the most common config edit that you don't have" and "here's the most common command that you don't know about."

We are already share configs with eachother via the dotfiles pattern. We somewhat share command patterns via coding streams. Seems doable.

(In general, making it easier to learn new tech and for devs to share / refresh the learning material for a new tech seem underdeveloped.)

Is Ilograph open source?