Don't miss my next post! Subscribe to my Technical Leadership newsletter and learn a bunch of useful stuff about effective technical leadership.
What are you doing this autumn?
|
Would you like to attend a talk about how to counter the fear of not being technical enough, or how we can stop making each other feel stupid, or how to make the most of diversity in the workplace? Or maybe you'd like to immerse yourself in one of my hands-on workshops... about refactoring skills, or about using TDD to wrangle AI coding, or facilitating mob / ensemble programming, or on how to handle the technical in technical leadership? Fancy spending time in Spain, or Berlin, or Paris, or Amsterdam, or best of all, lovely lovely MANCHESTER? Come join me! (And my workshops are REALLY good. Ask anyone. Just sayin'.) Here's the full list of events: Deliver Sessions, Zuhlke offices, Central Manchester, 11th Sept '25, TALK: "Are you technical enough?" PulpoCon ’25, Vigo (Spain), Friday Sept 19th 2025, WORKSHOP: Lift up conditional— The magical refactoring (LH) Manchester Tech Festival core conference Day 2, 25th Sept 2025, WORKSHOP: How to handle the technical part of technical leadership Lead Dev Berlin, Tue Nov 4th 2025, TALK: “Journeys in Diversity — what difference really means“ Newcrafts Paris, Nov 6–7 2025, Continuous Integration — That’s not what they meant Hands-on WORKSHOPS for Trifork academy, Amsterdam: Software Architecture gathering, Berlin, Nov 24th ’25, WORKSHOP: How can you combine AI with Test Driven Development Come join me! I always love meeting people. See you soon. |
Clare Sudbery
Don't miss my next post! Subscribe to my Technical Leadership newsletter and learn a bunch of useful stuff about effective technical leadership.
What do you do if there's stuff you don't know? Can you ask questions? What questions should you ask? How should you ask those questions? In an earlier post, I addressed the fear of having colleagues with better technical skills than you. I suggested, "Spend time pairing with [those who know more than you]." And I added, "Handled without apology, this exercise will deepen your team members’ respect for you, rather than the other way around." I promised to explain what I meant in another post....
Oh no! You’ve been given a new team to lead, and they’re working on this horrible legacy code base that everyone hates! I can't make sense of this code... Nobody enjoys working on this code. Team members are going through the motions with no interest in what they do, repeating the same terrible patterns and either counting the days to retirement or actively looking for more exciting work elsewhere. Here are three things you can do to make things better, for yourself and for your team: 1....
How will you fit through those holes? "I'm worried my current position only works at my current company. I moved up fast because soft skills come naturally for me. I prevent any office politics from affecting my devs, and they have the freedom of implementation at an execution level. But ask me to implement code for multi-threading? I am starting from 0." You are not alone When I'm running workshops with technical leadership, I see concerns like these raised repeatedly. People who started out...