Howdy, welcome to the week!
We'd really love to hear from you if you have a topic you'd like to write a CTO Craft blog post on, or appear on one of our Bytes events to discuss - please do drop us a line if you'd like to collaborate! Also, we're always looking for leaders to interview for our Zero to CTO blog series, which focuses on the path from IC to leader. There are some great interviews already up on the blog - check them out
Hope you're having a great summer - reach out if there's anything we can help you with
Until next time
Andy @ CTO Craft
Reads of the Week
Platform as a product is becoming an increasingly popular approach to building internal platforms in engineering organisations.
This issue is the second part and final article in a series about oncall. Part 1 – published last week – covers healthy oncall practices. In this issue, we dive into: In this issue, we’ll go through more than 80 data points on how much different companies pay for oncall.
From our Sponsors
Learn how unikernels can run up to 200% faster on GCP, 300% faster on AWS while being easier than kubernetes.
About our Sponsors
Thanks as always to the amazing sponsors helping CTO Craft bring you resources like this newsletter, our events, community and more:
AWS, CircleCI, Code Climate, O’Reilly, Pentalog, Skiller Whale, The Software House, iTechArt, LinearB, Lohika, Albany Partners, 101 Ways, PGS Software, YLD, Steamhaus, Swarmia
Culture & People
Focus means not just saying “yes,” but saying “no” too. Say “yes” to these 3 things and “no” to these 3 things when managing a growing team. Coupling the words “managing a growing team” and “focus” may seem oxymoronic to you.
Whether hiring is slowing down or keeping pace, now's the time to revamp your process, from job description to offer. Peoplism's founders share unexpected tips, from swapping resumes for a screener survey, to sharing interview questions in advance.
This week I read the paper On the Unhappiness of Software Developers by Daniel Graziotin, Fabian Fagerholm, Xiaofeng Wang, and Pekka Abrahamsson. This was a large-scale survey study with over 2,000 developers that looked to understand happiness among developers and what the top causes of unhappiness are.
“Our codebase is easy to understand. You won’t need more than a couple of hours. You’ll be productive right away! Guaranteed!” It’s Dave, your colleague developer, explaining to a new employee how one of the codebase of your company shines like a diamond.
In this article, Scott Himmer will go over some areas where you might find the design and engineering conflicts manifesting, what some of the contributing factors are, and strategies to work through the challenges.
Leadership & Self-management
In this article, I will cover five cognitive distortions that impact communication:
- Heaven’s reward fallacy
- Curse of knowledge
- Fundamental attribution error
- Fallacy of change
One of my favourite social engineering experiments is a computer simulation showing how ghettos form. A simple model of housing markets in which digital sellers are programmed to have a preference for certain types of buyer.
Tramale Turner is the CTO of TaxBit. We met at the LeadDev LeadingEng conference in London. When I met him I thought I bet he has some great leadership stories for us. I invited him on the spot and am grateful he said yes.
The topic of reducing friction exhausts me: Do people still need to be persuaded to help their developers go faster? Really? In this, the year 2022? But yes, in this, the year 2022, many teams require persuasion on this topic.
We are drowning in information. Most of that information is irrelevant. If only we could sort what matters from what doesn’t. The good news is that you can train your brain to evaluate the quality of information.
Agile, Engineering & Product
One day a shiny new app was completed. All the code was just right, and it was ready to go out in the world and be useful! The app looked bashful. “Um, um, on a computer! I need a computer to run on!”
The question: How can this portfolio team start to manage the project portfolio when the organization has 600 projects? Right now, the portfolio team is supposed to read the status decks for each of those 600, to understand each project's status. How to start?
So you want your developers to build secure applications during SDLC and not as an afterthought after being dinged by Security reviewers. You got this idea of highlighting security controls via reference architectures that can be easily consumed by developers early on in the SDLC life cycle.
The Scrum world has changed a lot in the last few years. Nowhere is that more true than estimating; Scrum folks have struggled with the practice since the framework's origin. Other folks also struggle with it, but this article focuses on Scrum. Many don't see the value in estimating.
If you’d like to be considered for the free CTO Craft Community, fill in your details here, and we’ll be in touch!
Please do remember to share this link if you know of anyone who’d like to receive TMW:
Have an amazing week!