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.
This is the third of three posts summarising some very interesting things I learned about finance on a recent IoD course. In part one I talked about funding and financial statements, in part two I talked about accountancy principles and ratios, and today I will talk about deciding which projects, and which companies, to invest in.
On Monday I published part one of three blog posts about finance, finishing with a quiz. In this post I will share the answers to the quiz, then talk about some important accountancy principles and some ways of thinking about the financial health of companies. In part three on Friday, I will talk about methods for evaluating projects and companies.
A couple of years ago I got some excellent training on finance from a finance director at the FT. At the end of last year I went on a longer, more intensive course from the IoD, aimed at non-finance directors, and I learned LOADS.
Last month I facilitated a panel at Lead Dev Live about how to build an effective tech strategy.
I recently went on an inclusive leadership course at work. It was very interesting. There were four particular lists that I wanted to make a note of to refer back to: