Don't be mislead...

Trading is, indeed, very simple, but for psychological reasons, it is very hard.

You wouldn't get paid the big bucks if it was easy.

So there's a class of puzzles called "river crossing puzzles" which involve having to cross a river on a boat/bridge containing some set of individuals/items with restrictions on which ones can be on the boat/left on each shore, right?

and the most common subclass of these problems is the one where you have 3 items/animals to cross with.
This is alternatively called the "fox, goose, and bag of beans" or "wolf, goat, and cabbage" puzzle.

the idea is that your boat can only carry one item at a time, but if you leave the wolf/fox unattended with the goat/goose, the wolf/fox will eat the goat/goose.
and similarly, the goose/goat will eat the beans/cabbage if left alone

so you have to set up a set of actions that never leaves either side of the river in one of the lose-states.

the solution to this variant being:
1. take the goat/goose over
2. return empty
3. take the wolf/fox over
4. return with the goat/goose
5. take the cabbage/beans over
6. return empty
7. take the goat/goose over

In Academia, people aren’t always supported when they need it. I want to share what @WesternU did when my husband died right after the pandemic shutdown. It should be shared with other uni’s as a model for empathy and proactive care when someone is in crisis.
1/
#AcademicChatter

Here is a special thread introducing our series on “The Making of the Islamic World.” It offers 10 episodes about the transformation of Islamicate societies between the 7th and 17th centuries. You can find the series page here: https://t.co/7mL9eWmMmz

This is Chris Gratien posting. I created this series during Fall 2020 for my students as asynchronous material supported by readings and discussion. This is going to be a long thread, but it will be a great shortcut for those looking to make similar use of these materials.

There are two items worth pointing out: 1. This is an overview of the political, social, and cultural history of Islamicate societies. It does not deal with the origins of Islam or many theological questions. It does discuss Islam’s spread and the transformation of Islamic law.

2. This is the first part of a two-part sequence that takes the history of the Islamic world into the present. It emphasizes developments and themes that have particular relevance for later periods.

This is really a multivocal narrative of Islamic history. We feature over 20 scholars from almost as many institutions. Many of those who worked on it, myself included, study the early modern and modern era but have teaching obligations that take us further back in history.

1. Now that Stan Lee is being eulogized far and wide, it's important to remember how marginal Stan Lee and his collaborators (Jack Kirby and Steve Ditko) were in the 1950s and 1960s.

2. Marvel Comics (before that Atlas) was just a cog in the machine of a bottom pulp publisher run by Martin Goodman, the husband of one of Lee's cousins. It was the lowest of the low in the publishing world.

3. Now Mario Puzo (not yet the author of the Godfather) shared offices with Stan Lee in the 1950s and 1960s. Puzo wrote for garrish men's adventure magazines and, like Lee, dreamed of writing a novel & breaking out. But Puzo looked down on Lee.

4. Flo Steinberg, 1960s secretary at Marvel: "They were always making jokes about us. They'd come in and giggle. mario Puzo would look in and would see us all working on his way to the office and say, 'Work faster, little elves. Christmas is coming.'"

5. When JFK was killed, the whole office of Magazine Management was stunned and quiet. Except Lee. He continued working. "He was still working on the comic books," Puzo said. "Like that was the most important thing in the world."

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.