On the Nature of Programming Languages
2019-04-22T10:50:00.862Z · score: 11 (5 votes)A skin-in-the-game vote multiplier based on age
There are two opposing ways to think about it.
You can either, as you do, say that your skin-in-the-game is proportional to the amount of time you have in front of you. From that perspective it seems fair that children should have biggest say in shaping long-term policies.
Or you can say that your skin-in-the-game factor is proprotional to how much you've already invested in the status quo. If you've spent 50 years working towards a goal it seems unfair that a 16-year old know-nothing should be able, on a whim, to throw all of that away.
The Politics of Age (the Young vs. the Old)
2019-03-24T06:40:04.359Z · score: 11 (5 votes)Muqaata'a by Fahad Himsi (I.)
2019-03-10T15:10:00.962Z · score: 15 (9 votes)Programmatic Code Generation: Composability
2019-03-02T22:50:06.865Z · score: 6 (2 votes)Lydian song
2019-02-25T20:50:01.088Z · score: 7 (4 votes)Tiles: Report on Programmatic Code Generation
2019-02-22T00:10:04.593Z · score: 5 (1 votes)Graceful Shutdown
2019-02-16T11:30:00.927Z · score: 10 (5 votes)Structured Concurrency Cross-language Forum
2019-02-10T09:20:00.779Z · score: 12 (5 votes)Confessions of an Abstraction Hater
2019-01-27T05:50:01.066Z · score: 12 (11 votes)Funny that I had exactly the same thought when writing the comment above: Isn't that just OCD? But if you look at concrete examples, it doesn't feel like that. Einstein? Incapable of accepting easy solutions? Yes. OCD? Probably not. Even van Gogh, despite the host of psychological problems, probably haven't had OCD.
Announcement: A talk about structured concurrency at FOSDEM
2018-12-30T10:10:00.836Z · score: 5 (1 votes)I think it has to do with intellectual honesty. There's a lot of highly intelligent people who are willing to accept the status quo, even if they are aware that it's broken, and just move on with their life. Then there are some people who are just psychologically incapable of such "ignore it and move on" attitude. Interestingly, this applies across broad spectrum of disciplines.
Science: A former kind of person does all the steps from a scientific method textbook and move on with their research. The latter kind of person won't be able to avoid thinking about why the method is as it is, whether its rationale matches their experiment, whether there are special circumstances that make the method inadequate and so on.
Engineering: The former type of person would just take existing tools and practices, glue them together and get a viable product. The latter kind of person will agonize over corner cases, whether there's a fundamentally different way of doing the same thing, whether the design is internally consistent and so on.
Arts: The former type of person is a mannerist. They use the existing expressive repertoire of their time and use it to create viable art. The latter kind of person cannot avoid seeing the problems with the current style, trying different ways of addressing them, getting back to basics and so on. Think van Gogh, for example.
Does that matter that much? The life had to originate somewhere and it, presumably, must have faced the same coordination problems along the way.
Yes, I own the book. However, I am not a biologist, so writing about the topic is hard for me. By focusing fully on the original book I have a reliable lead. If I had to compile from multiple sources, it would be much easier for me to go astray.
Anyway, if you'd like to write about the new developments, I would love to link that from this article.
State Machines and the Strange Case of Mutating API
2018-12-24T05:50:00.599Z · score: 8 (3 votes)“Can you just straighten out the yellow one without touching any of the others? Thanks.”
https://en.wikipedia.org/wiki/Recurrent_laryngeal_nerve#Evidence_of_evolution
Some more examples here: https://mikehadlow.blogspot.com/2014/12/the-lava-layer-anti-pattern.html
Equivalence of State Machines and Coroutines
2018-12-18T04:40:00.750Z · score: 12 (4 votes)On Rigorous Error Handling
2018-11-17T09:20:00.753Z · score: 13 (6 votes)Good point. I shall edit the article to make that clear.
There's an eerie similarity between an old software project and a inner working of a living organism. You see all these pieces that were serving some purpose in the past, then they were abandoned and repurposed, the changes are layered one on top of another without removing the vestiges of the old design first and so on.
I've written a small essay on the topic once: http://250bpm.com/blog:51
Two Approaches to Structured Concurrency
2018-10-31T16:20:01.467Z · score: 18 (6 votes)Unikernels: No Longer an Academic Exercise
2018-10-23T11:40:00.926Z · score: 29 (11 votes)Fair point!
It's just like replacing goto with while/for/if back in 60's. Not a big deal technically. Big deal in the terms of abstraction. Also, don't think about about OS threads. Every time there's a state machine somewhere it's just a green thread in disguise.
Update on Structured Concurrency
2018-10-19T11:10:01.179Z · score: 38 (10 votes)Nice idea. Maybe all the tokens should start in the pool and the players should have an option to withdraw them. I guess that would make people feel more explicitly "anti-social" if they did so.
Thanks for fixing that!
I had reposting from my site turned on recently. But this article haven't made it through (maybe because it contained tables?) So I've posted it by hand. Then the reposting pipeline caught up and posted it again. I would delete one of the two but there seems to be no delete button.
Which one specifically? I can look up the references for you.
Coordination Problems in Evolution: The Rise of Eukaryotes
2018-10-15T06:18:47.576Z · score: 46 (14 votes)Coordination Problems in Evolution: Eigen's Paradox
2018-10-12T12:40:10.675Z · score: 94 (38 votes)One-person Universe
2018-10-09T20:10:00.997Z · score: 8 (8 votes)Sorry, I've replied to a wrong thread.
I am based in Zurich, won't be able to come next week :/ But you are right, this topic could get toxic if discussed among strangers.
I think the main point in that regard is that the study doesn't distinguish between punishing cooperators because they are cooperators and punishing cooperators as a proxy for punishing punishers.
I, as well as some commenters on this thread, feel that the former phenomenon may exist, but yeah, it's based on feelings and folk wisdom. It may also well be that if given identity of punishers the players would punish punishers and leave non-punishing cooperators alone.
The original study has something to say about ingroups/outgroups. It's not exactly the same thing as the one we are discussing here but still:
Punishment may be also related to in-group–out-group distinctions (37) because people might retaliate if punished by an out-group member (38). Societies also differ in the extent to which their social structures are governed by in-group–out-group distinctions. For instance, according to some cross-cultural psychologists (15, 39) in “collectivist” societies many interactions are confined to close-knit social networks, whereas in “individualistic” societies interactions are more permeable across social groups. Because in our experiment all participants were strangers to one another, people in collectivist societies might be more inclined than people in individualistic societies to perceive other participants as out-group members. Therefore, antisocial punishment might be stronger in collectivist than in individualistic societies. Our evidence is consistent with this possibility because in regressions similar to those of Table 2 antisocial punishment is highly significantly correlated with a widely used societal level measure of individualism-collectivism (15) (table S10).
You are living in Soviet Union. Your father was sent to gulag, your mother was fired from her job in academia and sent to plow the tselina. You are being harrassed by the secret police. Then you meet a stachanovite who fulfilled the government plan to 200%. That guy is clearly a cooperator, producing more stuff you could benefit from, but you suddenly feel an irresistible urge to punch him in the nose.
I don't fully understand the mechanism on the theoretical level myself, but it seems to have something to do with the assumptions about authority. If you assume that authority is naturally malevolent you are going to try to oppose it. "This is not my game. This is a game set up by the authorities. By those scientist guys. What can I possibly do to disrupt it?" Punishing cooperators seems to be an obvious way to do that.
Possibly related phenomena:
- Lizardmen syndrome.
- Boaty McBoatface syndrome.
- Some kids being disruptive in school, just for disruption's sake.
I've seen you are planning a meetup in Bratislava. Maybe it would be worth discussing the topic. Maybe people would come up with possible motivations we haven't even thought of.
If there are any readers from Middle East or Greece I would also appreciate their thoughts on the phenomenon. It may be that the mechanism differs between regions.
Not a native speaker. I wanted it to be offensive but not to the extent where you would have to kill the offender and whole his family to restore the honor. Changed to "moron".
I like the framing of the problem here: If a bureaucrat (or lawyer) acts on fully specified set of rules and exercises no personal judgement then they can be replaced by a machine. If they don't want to be replaced by a machine they should be able to prove that their personal judgement is indispensable.
That changes incentives for bureaucrats in quite a dramatic fashion.
So we have two different explanations here:
You are saying that the participants considered the experiment to be a private pro-social activity and as such, one opposed to the state. By punishing cooperators they were signalling their loyalty to the state.
I am saying that participants considered the experiment to be a state-run enterprise and the pro-social punishment to mean complicity with the (unfair) state. By punishing cooperators they were trying to disable state's coercive mechanisms.
Those are almost exactly opposite explanations. I wonder if me can think of an experiment that would distinguish between the two?
I guess it would require to somehow trick the subjects into believing that they can form a coalition against the researchers. A kind of anti-Milgram experiment.
If you mean in game theory, there's the " common knowledge" concept.
If you mean in sociology, there was a ton of research done on the "social capital" some of which you would probably consider to be about the network effects.
Interesting point about the attitude to games. However, I guess the boundary between a game and reality may be fuzzy. People trading on stock exchange may treat it as a game. People planning a war may treat it as a game.
You may be right about the norms of social norms though. If you look how the authors measured civic cooperation it looks more like "trust in the state" metric. From the paper: "social norms are norms of civic cooperation as they are expressed in people’s attitudes to tax evasion, abuse of the welfare state, or dodging fares on public transport".
Would that reasoning apply to all societies around the world, including those in the West? If it does, it's unlikely to explain the differences between the societies.
I've just noticed that Dnipropetrovsk, Muscat, Minsk and Riyadh did better than Western countries in the public goods game without punishment. It may be a statistical fluke, but may it be that those societies are optimized for getting cooperative behaviour in the absence of enforcement mechanisms?
Anti-social Punishment
2018-09-27T07:08:56.362Z · score: 177 (92 votes)Programmers are often advised to write comments in the code about the intent, what they wanted the code to do, rather than about what the code does.
When you think about it, it makes sense. The code already does what it does, no need to write about that. However, what is the code supposed to do is often unclear, especially when the code is buggy.
This is kind of similar to the yeast example above. The rule is to explain why not how.
To give another example, I am trying to learn statistical mechanics. Not to memorize it but to actually grok it. And it turns out that staring at the equations doesn't help much. I am planning to look into its history to understand what kinds of problems were fathers of thermodynamics trying to solve (something to do with steam engines, I guess) to understand why that specific kind of thinking about the topic is useful.
One thought that comes to mind is that the monarch has not only to appoint a credible successor, but also discredit any other potential successors. Check the story of the son of Peter the Great, who was effectively killed by his father to prevent potential succession conflicts in the future: https://en.wikipedia.org/wiki/Alexei_Petrovich,_Tsarevich_of_Russia
Another related topic is preferential cross-cousin marriage which is well known from anthropology. I've written about it here, albeit in a bit different context: http://250bpm.com/blog:92
Any tips on other literature on the subject?
I don't want to put words in Ostrom's mouth but my understanding is that this has to do with scaling.
The system works if it's not too big or volatile, in other words, if everyone knows each other. You can easily imagine how the resource would be depleted if random people just showed up and started extracting it.
To scale, there's a different rule (the last one) which calls for hierarchical organization. In case of the irrigation system there's a group of people using the same distributory canal. That's a closed group, no stragers allowed. However, for problems they can't solve themselves they can coordinate with groups in control of other distributory canals.
That reminded me of a paper where they evaluate bots with with memory (that comes at a cost): https://cse.msu.edu/~dolsonem/pdfs/prisoners_dilemma_memory.pdf
The interesting intersection here is that memory can be used as a cache, thus avoiding need for re-modeling.
As for the accuracy of the book: There's not much quantitative data overall. The mode that Ostrom operates in is rather to show a lot of examples, then try to make some (pretty lightweight) generalizations. The last chapter introduces a model for researching coordination problems, but once again, it's nothing quantitative, more like a set of hints about what things and relationships to look at.
All in all, the book may not be very useful to get exact numbers but it may help to generate more conceptual surface area, give more structure to the problem of coordination failures beyond the naive "tragedy of the commons" parables.
There was a relatively long chapter on that, but not much quantitative data. In many cases policing was done by the stakeholders themselves, for instance, by rotating duty for the young men from the village who could then keep the fines they've collected.
Isn't it just the distinction between how facts are used in scientific discourse (you state a fact, expect it to be confirmed or challenged) vs. how they are used in political discourse (carefully select other fact to augment it and suit your political narrative)? I guess Umberto Eco would have had something to say about that.
Thanks! Fixed.
Inadequate Equilibria vs. Governance of the Commons
2018-05-25T13:17:21.981Z · score: 155 (56 votes)Soviet-era Jokes, Common Knowledge, Irony
2018-05-12T10:52:31.293Z · score: 31 (7 votes)Here's the entire story, as recorder by Yad Vashem, nothing about food/money though:
The carpenter Jonas Paulavičius lived in Panemune, a suburb of Kaunas, just across the Niemon River, with his wife, Antanina Paulavičienė, and their children, 16-year-old Danutė and 14-year-old Kęstutis. An ardent opponent of the Nazi regime, Jonas Paulavičius had developed close ties with Lithuanian communists before the war. When a Lithuanian friend approached him one day and asked him to shelter a four-year-old Jewish boy, Paulavičius willingly agreed. After consulting his wife, Paulavičius took the child, Shimele Shames, into his home and later decided also to give shelter to his parents, Yitzhak and Lena Shames and his grandmother. Together with his son Kęstutis, Paulavičius dug a hiding place under the floor of his home, where the Shameses hid. Aware of the distress of the Jews interned in the Kaunas ghetto, Paulavičius decided to save as many as possible. He began arranging meetings with Jews in the ghetto and inviting them to hide in his home. At the same time, the Paulavičiuses expanded the room under their home, and towards the end of the German occupation, they prepared an additional hiding place. Among the 12 Jews hiding there were the four members of the Shames family, including grandmother Feinsilver; the doctors Tania and Chaim Ipp; Aharon Neimark and his wife, Mania (later Gershenman); David Rubin; Yohanan Fein; as well as Miriam Krakinowski, and Riva Katavushnik, whom Paulavičius managed to save from a labor camp just before it was liquidated. Even after the war, Paulavičius managed to obtain a large sum of money for the Neimarks, to enable them to leave Lithuania and immigrate to Israel. In 1952, Paulavičius was murdered by his antisemitic neighbor, who never forgave him helping Jews during the occupation.
I guess if cognitive dissonance would stop effecting people, they would start following different incentives, those that are currently drowned out by the dissonance, whatever they may be.