Last year, I read the excellent and very interesting Seven Concurrency Models in Seven Weeks (though in somewhat more than seven weeks). This is a very long post with my notes from reading it.
At the FT we have a role called Principal Engineer. Many companies do; however, the shape of the role at the FT is different than it is at many other companies, so in this post I explain what the role is like on my team, Customer Products.
I delivered a talk at the inaugural London LeadingEng conference on how to set a tech strategy, specifically after the launch.
On Tuesday, I delivered a talk at QCon London: No Next Next: Fighting Entropy in Your Microservices Architecture.
If you want participation in a meeting with people who don’t spend a lot of time together, one thing that can help is getting everyone to say something at the start; here is a low-pressure way to do that.
Yesterday, I delivered a talk at LeadDev Together: The good, the bad and the tech strategy.
I recently couldn’t work out why Clojure was not working concurrently in a Vagrant box. I didn’t solve the problem, but I learned many things, and here are some of them.
Two years ago, I wrote about how as a technical leadership team we can figure out what to work on. We made some changes to the way we worked and found them really beneficial. However, last year we realised there were flaws in how we were working, which made it hard for us to prioritise the bigger, more impactful pieces of tech work.
Threat modelling is a way to identify the potential security flaws in your system, and prioritise mitigations. On Monday I attended a session comparing some card games you can use to help you, at SPA conference. This is a brief write-up.
We wanted good WiFi coverage in our house and we did not have it, so we set up a Ubiquiti network. This is how we did it.