Skip to main content

2017 Donations

Each year around Christmas I make a set of donations to causes and organisations that I want to support. I do this all at once, because I find I'm a lot more deliberate about what causes I support and the amount I want to donate than I am donating on impulse throughout the year.

I adopted this approach couple of years back after I read a tweet from Simon Lyall. Following his lead I've decided to blog my donations this year on the theory that it may encourage others in a similarly privileged position to do likewise.

I'm always rather uncomfortable discussing financial matters, so I'm going to avoid dollar amounts and just talk about groups of charities. Everyone's situation is different anyway so I don't believe dollar amounts really help the goal anyway.

Category 1: "Humanitarian Causes"

I use humanitarian loosely, my general preference is to support organisations working locally. I use GiveWell for supporting work overseas.

I split about 75% of my overall donation equally between these organisations:


Category 2: "Agenda I want to advance"

Tech has been very good to me, so I like to somehow support making that an option for more of the next generation, particularly those for whom it's not an easy / obvious option. Basically this comes down to three things:

  1. Ensuring that kids have the basics covered so they can pursue a passion
  2. Encouraging a passion for S.T.E.M
  3. Making sure there's still a tech sector for the next generation
This leads me to split another 20% across the following:
Category 3: "Tech projects I use / want to continue existing"

Finally I spread the last 5% of my donations between some projects that I use:
  • Wikipedia
  • Mozilla
  • GPG
  • Lets Encrypt
  • Tor

Comments

Popular posts from this blog

Planning, Estimating and Monitoring a Dev Project - Before Planning

Estimating and Planning and monitoring day to day development is a lot of what's involved in the job of a team leader. This is the approach I take to this, I don't claim to have created any of this, rather it's just the collection of agile methods and tools that I find useful. This is what I do for sprint planning every 2 to 3 weeks. When doing ball-park planning for a longer period I follow the same basic process but at a less granular level with corresponding drop in accuracy.

Before Planning There are a couple of questions that really need to be answered pre-planning. This is the side of planning that's often not visible to the juniors in the team. It's the bit that gets forgotten about and contributes to that wonderful "I don't know what my manager does, but when they're away it all goes bad" feeling in so many well run development teams.
The two questions you need to answer are How much time do you have?What are you trying to do? How Much Time D…

What is the first thing you do in the morning?

What is the first thing you do at work once you log into your computer? No really think about it, is it the same thing you were doing a year ago. I can almost track my career by the changes in what I do first thing in the morning.

When I was a junior developer, bright eyed and bushy tailed I checked my email first thing. It was a bit of a novelty to receive professional email and it made me feel a bit like an adult. Email seemed like the corporate information channel, so I thought as a responsible professional I should clear my email first thing and check it regularly during the day. The thing is though I didn't really get that much email as a junior.

As I started to become more senior I started to get more email. I also started to get more interruptions during the day. The morning started to be that really nice period where nobody talked to me. So I started to code first thing. Email could wait till I was being interrupted anyway. So my morning routine became code until I was int…