Charitable donations

I have never signed the Giving What We Can pledge, despite a long running nagging feeling that I should. This is because reasons.

I’m still not going to sign it (for now), but I’m going to start making up for my charitable deficiencies as an individual by sorting out my act through my company (I currently operate through my own limited company).

I’ve been putting this off until my business bank account was a bit more liquid, but now it is so it’s time to act.

So, starting from this point, 10% of all my limited company’s revenue will go to charity. To more or less backdate this for invoices I’ve issued so far, I’m going to be donating £1000 pounds to charity immediately (or, rather, as soon as the charities I’ve chosen get back to me RE how they want me to handle corporate donations, but I’ve emailed them already).

I am still vacillating somewhat on exactly what charities to donate to, but I’ve decided to go with an initial position that I am pretty confident in and adjust later as I refine my thoughts: I’ll be donating in a 50/50 split between Give Directly and Cool Earth. Each will definitely get £500 of that initial donation, and until I come up with a better plan will get 5% each of my revenue.

I’m also considering:

  • Donating to the Against Malaria Foundation. At present if I do this the most likely scenario is a 50/30/20 split Cool Earth/Give Directly/Against Malaria Foundation (I am aware that this is the direct opposite order to what Give Well would recommend. Again, reasons. Maybe even good ones).
  • Finding some good political change organisations to donate to. Recommendations welcome.
  • Investing in renewable energy funds. Note: This requires me to do a lot of investigation of how this sort of thing works as a corporation, so I’m probably not going to do it any time soon.
  • Offering clients some sort of matching scheme for up to an additional 10%.
  • Additionally donating money to open source organisations such as the Python Software Foundation. If I do this it would not come out of the 10%.
This entry was posted in Charitable giving on by .

Hello from Windows

For the first time in about 15 years, I’m running Windows as my primary operating system.

It would not be accurate to say that I’m feeling conflicted about this. I’m feeling downright disgusted by this.

But you know what… it’s pretty OK so far. I’ve not had 100% success getting things working, but I have more working now that I typically would at this point in a Linux install, and Windows 10 is pretty nice.

What happened? Well, basically I got bored of my computer not working. I don’t actually enjoy ops at the best of times, and debugging why my computer has randomly decided sound shouldn’t work or similar is absolutely not the best of times.

The plan is that most work is going to keep happening in Linux running on a VM. I’ve ended up having to use virtualbox rather than Hyper V (I got a bunch of weird effects with they keyboard not capturing properly on hyper V and I really wanted native shared folders support), but it’s working pretty smoothly so far.

I feel kinda gross about this, but at the same time I feel like it was obviously a good idea and I probably should have done it a while ago. I’ve certainly been threatening to for some time. I’m sure I’ll have at least one screaming fit at Windows in the near future, but for now I’m feeling cautiously optimistic.

This entry was posted in Uncategorized on by .

The Borda Count as a Randomized Limit of Approval Voting

I just noticed this and it seemed worth writing down. It may be a well known result, but 30 seconds of Googling doesn’t turn up everything obvious.

It turns out, that under a certain (highly unrealistic) model of voter behaviour, if you use Approval Voting then you get the Borda Count winner.

In Approval Voting you get to cast a vote for as many candidates as you like, and then the candidate with the most total votes wins.

The question is: How many votes do you cast? Do you cast a vote for only your top candidate (in a close race you probably should)? Do you vote for everyone except the candidate you think is literally Hitler?

I’m actually not sure what the generic tactical answer to this is. For the sake of this post it doesn’t matter, because I’m going to be looking at the following model: What happens if everyone just picks the answer at random? i.e. you have \(N\) candidates, they rank the candidates in order of preference, and then they pick a number c between \(1\) and \(N – 1\) and vote for their top c candidates.

And the answer is that what happens is that you elect the Borda winner.

The Borda Count works as follows:

Everyone ranks every candidate. For each voter, a candidate is given a score: The top candidate gets N, the second candidate gets N – 1, and so on. The candidate with the highest total score wins.

The reason why approval voting results in the Borda winner is quite straightforward: The expected number of votes a voter gives a candidate is just an increasing linear function of the Borda score they would give that candidate.

If you rank a candidate in position t, then you vote for them unless you choose \(c < t\), which happens with probability \(\frac{t – 1}{N – 1}\). So the expected number of votes is \(0\) if this happens and \(1\) otherwise, i.e. \(1 – \frac{t – 1}{N – 1} = \frac{N – t – 2}{N – 1} = \frac{1}{N – 1} B – \frac{1}{N – 1}\), where \(B\) is the Borda score.

Because the the Borda winer is just determined by adding up scores, the scaling doesn’t affect who wins. So assuming that the populace is large enough, the randomization more or less averages out and you elect the Borda winner.

Now, as mentioned, this is a highly unlikely model of voter behaviour – it’s probably just about valid if you have a very small number of candidates (3 or 4), but for larger number of candidates I would expect the number of votes actually cast to be bunched up around either \(0\) or \(N\) with fairly sharp drop-offs moving away from that. I don’t actually know if that’s how it works in practice, but whatever happens in practice it’s very unlikely to actually be uniformly at random.

So I present this mostly as a curiousity rather than as making any point about the actual merits of either system, but I thought it was interesting.

This entry was posted in voting on by .

Randomizing Lean Coffee

I went to a Lean Coffee event last night. I really enjoyed it.

But naturally I’m constitutionally incapable of participating in a democratic process without thinking about whether it could be improved by randomization, and I think this one can.

Lean Coffee as we practised it had slightly more structure than described in the link:

  1. First we voted as described (though actually we had three dot votes for some reason), and then we went discussed the topics in order of decreasing vote.
  2. A discussion lasted 8 minutes. A vote was then conducted as to whether people wanted to continue – everyone could vote yes/no/maybe, and you continued for another 4 minutes if there were more yes votes than no votes (maybes are ignored). In theory at the end of that 4 we would vote again, but we actually never voted to continue.

There are two voting mechanisms here, and one is much better than the other: The continuation vote is a good system because you’ve got a simple yes/no question and thus majority rule is a straightforward choice (arguably you can improve it with randomization, but it’s a hard sell).

The voting on topics thing on the other hand didn’t work very well for me. There was a lot of obvious tactical voting caused by both the system and the public nature of the voting. e.g. people were very reluctant to cast their last vote for something that didn’t already have votes.

So I’d like to propose the following alteration to the system:

  1. People write cards and just put them into a central pile. Once everyone has finished, the pile is shuffled.
  2. You now go through the pile in the shuffled order. You draw a card, the person who wrote it has a short opportunity to explain what it means (normally this happens before the voting phase), and then everyone votes using the majority rule of yes/no/maybe whether they would like to discuss it. Break ties by treating them as no votes.
  3. If the conclusion is yes, you discuss it as above. If it’s no, you move on to the next card.

I think this has a number of advantages over the existing system:

  1. It removes the element of tactical voting (for the most part. You get an element of time tactical voting where you vote something down because there’s something later you want to discuss more, but that seems quite reasonable to me)
  2. What you end up discussing has a much stronger mandate because you’ve had an actual vote on the specific question of whether you want to discuss it.
  3. We got a lot of ties which had to be broken arbitrarily in the normal voting for what to talk about process. This intrinsically doesn’t have that problem.
  4. It has the usual debiasing advantages of randomization which help offset the tyranny of the majority.
  5. It’s actually a more streamlined process – you go straight from writing to discussion with no intervening steps.
This entry was posted in voting on by .

Filibuster, the game

I originally thought of this as a training exercise, but actually I think it’s probably quite a fun party game.

This is a game about interrupting other people without talking over them. It works for any number of players in theory, but will probably become unmanageable somewhere in the 5-10 range.

Setup

You will need:

  • One weird specialized piece of equipment, which is a decay timer (terminology mine). This is a randomized timer where you get to set a half-life for the timer and then it goes off at an exponentially distributed time with that half-life. (It would be easy enough to create an app for this but I’m not aware of there being one). Set the half-life to somewhere between 30 and 90 seconds (the shorter it is, the shorter the game).
  • A way of keeping score
  • A way of assigning a random player (cards, beads to put in a bag, etc).

Once you have those you are ready start.

Play

The game consists of ten rounds. Each round is played as follows:

  1. A random person is selected to start, by drawing straws or whatever mechanism you’ve picked. As soon as they start speaking, the decay timer is started.
  2. Anyone else may interrupt at any time.
  3. When the timer goes off, the round is over and scores are calculated.

Scoring happens based on who is speaking at the exact instant the time goes off.

  1. If nobody is speaking, nobody gets any points.
  2. If only one person is speaking, they get one point.
  3. If multiple people are speaking then whomever of them started speaking first gets one point, and everyone else loses two points. If there is a joint tie for who started speaking first they each lose two points.

In the case of ambiguity in 3, err on the side of everyone losing.

Once the round is over and scoring has been calculated, start with the next round. Once ten rounds have been completed, the game is over. Whomever has the highest total score wins (ties are joint wins).

Notes on concept and purpose

The idea is that it’s a game about waiting for the person currently speaking to pause and then interrupt mercilessly. You can try to do this by interrupting them mid sentence, but it’s a high risk strategy unless you’re sure you can browbeat them into silence by talking over them very rapidly because every second you’re speaking while they are costs you two speaking solo.

I originally thought of this in terms of exercises for practising conversational flow, but it somehow evolved into a game. As a result of my primary motivations, I would be terrible at this game.

The purpose of the exponentially distributed timer is that it means that your expected score is the amount of time you spend speaking solo minus twice the amount of time you spend speaking over someone else, which I think is a nice metric. I was originally thinking in terms of having a voting system for penalizing jerks, but I like this system much more.

ETA: eiríkr rightly points out that this game may need some sort of neutral adjudicator to decide whether something is an interruption or not. I think it might be obvious most of the time, and with the bias in favour of scorched earth in cases of ambiguity it’s probably OK. This would come out in play testing I think.

This entry was posted in Games on by .