Cate Houston (@catehstn) gives 5 useful warning signs for both ICs and Managers about resignation. I especially like the pragmatic “do this” if you’re seeing each sign. There’s even a bonus 6th sign but you’ll have to read the article to find out what they all are.

This article from Antoinette Weibel (@antoinetteprof) reminds me that the choice of tools or processes to use matters as much as how you use them how. She outlines some common pitfalls to avoid when it comes to OKRs.

Nick Moore (@nickwritesit) shares some concrete examples of atypical schedules of people working in tech. This requires communication and agreement with their team and stakeholders. Consider experimenting or using these as inspiration for your own schedule.

This is a summary article of a LeadDev roundtable discussion on metrics I co-hosted with James McGill for Engineering Directors. You’ll get a sense of some of the topics and trends that emerged from a group of experienced engineering leaders from companies of all shapes and sizes.

Jason Yip (@jchyip) looks at reasons why building stable teams is difficult, but also some great options for thinking about team design. The patterns he includes are just as relevant for companies not going through rapid growth looking to build a new team.

VP Engineering at Tier, Efrén A. Lamolda (@ealamolda) explains the three types of phases a team (originally from Elastic Leadership) which means your leadership style must adapt to fit the phase.

Ken Norton (@kennethn) explores an ideal ratio between Engineers and Product Mangers and some factors that influence the ratio. A great article, very well explained. 👏

HashiCorp has an impressive engineering and product-focused culture. I personally think it’s one of the most modern companies that balance research-intensive work and strong product engineering. HashiCorp have now generously published how they work, sharing individual, manager, team, and company-wide practices. This is a website I’ll be returning to time and time again. Thanks to Armon Dadgar (@armon) and Mitchell Hashimoto (@mitchellh) for generously sharing!

Company culture is extremely important, but impossible to define. David Xiang (@davex_tech) shares some ideas on what to measure when it comes to software engineering culture?

Jacob Bo Tiedemann (@jabopiti) and Tanja Bach (@tanjabach) offer examples of what poor developer experience looks like and what you can do to change it. It also emphasises the financial cost which technical leaders need to recognise *and* communicate to influence management to invest.