I really enjoyed this interview from Manager’s Club with Happy Wang. I also had no idea about Everbridge (fascinating domain!) and can only imagine the challenges they have as a company. Happy shares great points for new managers and good book recommendations.

Reading time: 7mins

I enjoyed this read from Dan Fike and Eric Vogl about what the technical leadership path at Carta looks like. It’s also a great example of an implementation of the Trident Model of Career Development!

I’m including this article this week as I personally don’t often come across many lists of leaders in the data space. You can create a free account to read an interview with each person or the first paragraph otherwise. They could have improved a lot like making it easier to find each person on Twitter/LinkedIn and rephrase the horrible question, “What has been your path to power?” 🤷‍♂️ Still, you might find some interesting role models and new people to follow as I did.

Kin Lane (@kinlane) presents a dense but succinct article about API specifications touching lightly on the history, why they are useful and how to get the most out of them. A really great read if you’re interesting in publishing or consuming APIs (most people in tech 😅)

Lily Hay Newman (@lilyhnewman) reports that the FIDO alliance (an industry alliance with a mission to find and promote authentication standards to help reduce the world’s over-reliance on passwords) has found the missing piece on the path to a password-free future.

This article from Aminu Abdullahi compares two tech concepts in a short and succinct way and a conclusion about where each concept best fits.

Although this article is long, First Round (@firstround) provides a practical and pretty comprehensive guide to assessing, shaping and deliberating guiding culture. Please note this is aimed at early stage companies, so YMMV.

A short but useful answer from Tom Foster (@FosterLearning) to the question above that makes you reflect on organisational design. Unfortunately, most leaders in tech forget about the principle he emphasises, “Don’t organize the work around the people, organize the people around the work.”

This is a great article from Graeme Lindsay (@graemelind) that looks like a case study of Team Topologies in the context of the WebCore platform at the BBC (not a small organisation!).