|
|
January 2 · Issue #125 · View online
Level Up delivers a curated newsletter for leaders in tech. A project by https://patkua.com. Ideal for busy people such as Tech Leads, Engineering Managers, VPs of Engineering, CTOs and more.
|
|
Recap Edition: Top Organisation & Process Articles for 2021 I’m keeping this introduction short as I know many of you are taking a break. This edition has the most-read Organisations & Process articles that Level Up included in 2021. Enjoy and happy holidays! 🎉 If you think this issue might be great for someone else, give them a gift 🎁 and forward it on. Stay safe and healthy 🙏
|
|
|
DevOps Automation for Teams Need a modern DevOps automation tool to connect your CI/CD pipeline? Octopus offers reporting, compliance, access control, SSO access, and priority support required by leading DevOps teams. Try it now.
|
|
|
5 Signs It’s Time to Quit Your Job
Reading time: 8mins
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.
|
The Dark Side Of OKRs (And Why We Should Care)
Reading time: 6mins 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.
|
Async, remote, and flexible: How 7 engineers rethought their work calendars
Reading time: 12mins
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.
|
|
🌟🌟🌟 Reach thousands of engineering leaders around the world. Maybe you want to share a leadership role you’re looking to fill? Interested in becoming a sponsor? Get in touch for details. 🌟🌟🌟
|
|
Engineering metrics at every level: An engineering director’s guide
Reading time: 6mins 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.
|
Why it’s difficult to build teams in high growth organisations
Reading time: 4mins
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.
|
Tech Leaders, where is your Team?
|
Start 2022 by levelling up your technical leadership skills with self-driven courses at https://techlead.academy
|
The Ideal Ratio of Engineers to Product Managers
Reading time: 4mins
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. 👏
|
How HashiCorp Works
Reference website 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!
|
Software Engineering Culture Metrics – How Do You Measure Culture?
Reading time: 10mins 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?
|
Why you should invest in good Developer Experience today
Reading time: 5mins
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.
|
|
If you enjoyed this newsletter, please send me feedback and share it with others!
|
Did you enjoy this issue?
|
|
|
|
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
|
|
Patrick Kua, Postfach 58 04 40, 10314, Berlin, Germany
|