Articles for category: Leadership

August 7, 2018

Greg Thomas

The Problems with Code Reviews

The #1 problem with Code Reviews isn’t whether the standard is followed, what syntax is used or when you start doing them with your team. Whatever you pick (and when) will work – it will. The problem is the follow through. We start with lofty expectations of all that we’ll accomplish, we turn on all the switches and for a time things start to go well – code starts to get reviewed – questions are answered. But over time, they lose their lustre That last minute fix that has to go through by Senior So and So has to get

Yes, You Can Be Successful with a Bad Manager

But it’s all up to you. It’s up to you how you show up. It’s up to you how you conduct yourself. It’s up to you how much effort you put in during the day. It’s up to you how much effort you put in during the night. It’s up to you how successful you want to me. Not them, the choice is yours, it always has been.

You’re Getting the Wrong Answer

Because you’re asking the wrong questions. Your team isn’t late because they all don’t use the same tools. Your team is late because no one is helping coordinate the different tools. The reason you missed that delivery deadline wasn’t because the bug count was too high. It was because the feature load was preposterous and was never going to be met. We shy from asking the wrong questions because the answers that come aren’t immediate and cannot be answered by one person. You know if you’re getting the easy answer, you’ve been to the rodeo before, the next time you

How You Can Serve Your Team Better?

If you’ve never asked them, you can start there. That’s really all there is. There is no complicated mumbo jumbo or fancy leadership style books to read or culture decks to download. Just ask them what they need and start there. The plan, the strategy, the direction? You can figure that out later, but not until you talk to your team.

Changing Priorities will get you Every Time

They will change and shift and confuse and destroy any ounce of progress you are trying to make. If you have a daily scrum every morning and every morning the priorities are different and in direct conflict with the priorities from the day before then by the end of that week you will have accomplished nothing. And neither will your team. And if you can’t stop the changing priorities, learn to intercept them, figure out why they are happening and above all, insulate your team from them, keep them on track, keep them driving and delivering. While everyone else is