Hello, welcome to the week!
A massive thanks to everyone who's completed the CTO Craft Member Survey - we now have several hundred data points with which to iterate on our events, resources and community activities. Watch out for some new initiatives very shortly - you'll hear about them first here in TMW and in Slack.
You'll notice a theme in today's stack of links; we're taking a close look at the Hiring Arc, from sourcing to onboarding. If you have any thoughts or insights you'd like to share or would like to feature in upcoming TMW issues on this topic, please drop us a line!
On with the show - have a great week!
Andy @ CTO Craft
You’ve probably heard of ‘tech debt’ and how it can impact a company. However, have you ever tried to explain it to non-technical colleagues in basic terms? It’s important to your company, and it’s essential that other functions in the company understand its impact and even its existence!
CTO Craft Bytes
For quite some time, design thinking has been perceived as a magic methodology to set yourself apart from competitors by focusing on your customer’s needs. Yet, innovation labs come and go – building in-house teams to focus on the future alongside running the day-to-day business has proven to be challenging.
Reads of the Week
Learn where you stack up against other companies in this tight labor market and the latest tech hiring data and trends.
Most of our tools and processes around product/feature prioritization are heads-down analytical: RICE, opportunity trees, Kano, weighted 16-column spreadsheets, WSJF, Eisenhower, whatever.
About our Partners
A huge, huge thanks to our partners for supporting CTO Craft in 2022 - you’re all amazing!
AWS, CircleCI, Code Climate, Karat, O’Reilly, Pentalog, Indiespring, Skiller Whale, The Software House, iTechArt, LinearB, Lohika, Albany Partners, 101 Ways, PGS Software, Steamhaus, Swarmia
🥝 🥝 If you’re interested in reaching thousands of senior technology leaders and decision makers, drop a reply to this email to see our Partnership Opportunities! 🥝 🥝
Culture & People
I’m going to try to do something hard: simplifying hiring down to a dead simple algorithm based on only four data-backed, high-signal attributes.
It’s Monday. You’re back at work after a nice weekend, feeling excited as the new engineer is joining your team today! She arrives, gets her laptop and first coffee, you have a nice chat about the weekend, then the question hits you: “So, what’s my first task?”.
Running data science projects successfully is already quite challenging, and the first step is to hire some data scientists. Given the current market this is no easy task.
There are many ways to evaluate an engineering candidate’s skills. One way is to ask them to solve a problem or write some code. We have been striving for a while to make this experience better at GitHub.
Where your work meets your life. See more from Ascend here. Meetings serve different purposes, ranging from informal social gatherings to formal brainstorming sessions. They often show up on our calendars as recurring events (with no end date in sight!).
Leadership & Self-management
A couple of weeks ago, I hosted a talk with Point Nine, where I presented what I believe are the essential building blocks of great engineering leadership.
Engineering Managers (EMs) don’t intentionally set out to fail. Instead, they are often set up for failure. But even if they are set up for success, there are some common ways new Engineering Managers fail. This article will cover these and what to do instead.
At ease with experimentation, prototyping, & MVP development: Have you built something that had to be thrown away? Comfortable with ambiguity/constant change: How do you balance technical debt with the need to move quickly?
One of the most important functions of effective leadership is to master the power of perspective. Leaders require the ability to look at problems and determine their relative size and importance.
Agile, Engineering & Product
As the pendulum has swung from monoliths to micro-everythings - services, front-ends, you name it - we find ourselves with more "things" to build and maintain. And so it begs the question, who is responsible for what?
We need budget and headcount to mitigate risks. Larger risks should encourage more resources towards mitigation efforts. Legal costs are wild area of costs… along with costs to the business and regulatory risks.
Confession: I’ve been avoiding the words “agile mindset” for some time because I don’t know what it is. And, completely by coincidence, I’ve recently had a couple of encounters that have caused me to think again. So let me explain…
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!