Upgrade to Pro — share decks privately, control downloads, hide ads and more …

⚡️ Do Repeat Yourself: How to move from Develop...

Avatar for Luke Stringer Luke Stringer
May 06, 2025
7

⚡️ Do Repeat Yourself: How to move from Development into Leadership

Lightning talk version of my talk Do Repeat Yourself.

As a developer moving into a leadership role for the first time it can be can be tough, confusing, and at times overwhelming. This was certainly the case for me. I discovered that the principles I had once followed when building software were no longer effective as a leader. However, after a few years I can confidently say that becoming a leader is one of the most fulfilling things I've done. In this talk you will learn some of the ways to adapt your developer skillset to that of a tech lead, and I will share my observations in making these adjustments myself. We'll look at how the problems you need to solve are suddenly very unfamiliar, with incentives that are often the reverse to what you've been used to. If you've had similar experiences or are considering a move into leadership yourself, this talk is for you. You will leave with a number of effective strategies for becoming a tech lead, while remaining kind to yourself and others.

Delivered at

Hey! All Day. Leeds, May 1st 2025

Avatar for Luke Stringer

Luke Stringer

May 06, 2025
Tweet

Transcript

  1. Hi, I’m Luke, @lukestringer90 I work for as a Tech

    Principal I run the LEEDS MOBILE monthly meetup Do Repeat Yourself How to move from Development into Leadership
  2. Have you ever wondered if leadership is the right move

    for you as a developer? 🙋 🙋
  3. Why Consider Leadership? Good Reasons ✅ Want new challenges ✅

    Solve problems at a broader level ✅ In fl uence team culture ✅ Bored of just writing code
  4. Why Consider Leadership? No-So-Good Reasons ❓Promotion is the only way

    to advance ❓More money ❓“You're a good dev, so you must be a good leader”
  5. Mindset Shift Developer Leader Clear Outcomes Ambigious Outcomes Short Feedback

    Loop Long Feedback Loop • Code compiles • Tests pass • PRs approved • Apps released
  6. Mindset Shift Developer Leader Clear Outcomes Ambigious Outcomes Short Feedback

    Loop Long Feedback Loop • Code compiles • Tests pass • PRs approved • Apps released • Mentoring • Hiring • Business change • Tech adoption
  7. Staying Technical (enough) You may fear losing your technical skills.

    You won’t, but you’ll use them differently.
  8. Staying Technical (enough) You don’t (maybe shouldn’t) need to be

    hands-on. However, you can stay hands-warm.
  9. Staying Technical (enough) Do Developer Things 🧑💻 Review code, fi

    x bugs 👩💻 Discuss architecture 🧑💻 Watch WWDC, Google I/O 👩💻 Attend meetups, conferences
  10. Staying Technical (enough) Retain an Expertise 🔨 Git and version

    control 🔨 Debugging techniques 🔨 Regular expressions
  11. Staying Technical (enough) Technical ignorance is now your superpower. Normalise

    the asking of “stupid” questions to create a shared understanding.
  12. Communication Why are my changes not embedded? Why am I

    misunderstood? Why do people forget what I’ve said?
  13. Communication The DRY principle tells us
 Don’t Repeat Yourself in

    code. However, in leadership 
 Do Repeat Yourself is much better!
  14. Communication You are the “glue” between your team and the

    rest of the business. Make what you say tangible to the audience, but be consistent.
  15. Being Effective Find the Right Approach for you 📝 Note-taking

    📝 Todo lists 📝 Mind maps, digital brains 📝 Email and Calendar apps
  16. Being Effective Be kind to yourself. Remember… for your team

    to be effective, 
 YOU must also be effective.
  17. Do Repeat Yourself How to move from Development into Leadership

    Hi, I’m Luke, @lukestringer90 I work for as a Tech Principal I run the LEEDS MOBILE monthly meetup