I've been freelance for three years now, and I admit it: I haven't had a very cohesive plan. I've been reactive, saing Yes to all the things and going where the wind blows me. Since then, I've been doing a whole series of exercises designed to help me decide what I should be focusing on - based on my strengths and previous successes. I've also been telling people this process was "nearly finished" for flippin' ages now. And that when it was finished, I would present the results to anyone who was interested. Then I realised it was never really going to be finished. So some time during the week after next (the week beginning Mon 9th June 2025), I'm going to give a high level summary of what I've been up to and what conclusions I've reached so far. 2. It'll give you a chance to vote on the date / time of the session. My plan is for the session to last an hour and a half, but I'm going to book out a two-hour time slot to leave room for general chat for the last half hour. |
Don't miss my next post! Subscribe to my Technical Leadership newsletter and learn a bunch of useful stuff about effective technical leadership.
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...
All humans have problems from time to time One of the hardest parts about a leadership role is the fact your team are PEOPLE with PROBLEMS and that’s hard to ignore. You might be aware that one of your team members is privately suffering. You might hope you can just ignore it. Or maybe you desperately want to help, or feel like you should help, but either way you don’t know how. First things first: You’re (probably) not a therapist. It’s absolutely not your job to fix people’s personal...