I Know more than You

No I don’t. Not even close. I know things you don’t know and vice-versa. That’s the beauty of working with a team, you don’t have to be the expert at everything, you don’t have to know it all. The best advice I ever got for leading a developer that outclassed me in every area – “I won’t be able to help you with coding, but I am going to help you with all that other stuff” – and from there we worked incredibly well together. There are no Gurus, Ninjas or Rockstars – there is you and your team.

March 15, 2025

Greg Thomas

The Last Bug

The Last Bug before any release is the one where everyone is standing over you, wanting it to get done. It’s been an irritation the entire release, you’ve pushed it off more times than you can count, it’s driving you nuts. The worst part is, that you don’t even know what is causing it. But when you figure it out, when you realize what was causing it, when the fix is right in front of you. That will become the best moment where you mark a ticket as “done” that you could ever have. Don’t push it off, figure it

March 14, 2025

Greg Thomas

Make Your Own Path

The path you take is yours and yours alone. It’s not linear, it doesn’t follow what everyone else does, and it’s not based on how many years you work somewhere or go to school. It’s your path, filled with ups and downs and all around. In the moment, you’re not thrilled with your path, you might not enjoy the daily grind of it, and it might feel like all it does is hold you back. But when you look back, it’s the path that made sense, the path that worked, and the one that fit best for you. The worst

Feedback in Intervals

Feedback can come in intervals or as one big hose. The benefit of intervals is that you are able to give out the feedback in drips, watch for improvement, tweak, and give out some more. When it comes out as a firehose, the “giving” of the feedback benefits you because you get it out all at once and can move on. Feedback in intervals takes longer, goes slower, and requires you to hold back when talking to others.  It puts more on you as the leader than the individual. Anyone can do a firehose and get everything out all at

The Goal in Your Test Cases

The goal in your test cases is to validate a problem that has been solved. It starts with understanding the problem and reproducing it. If you don’t know the problem you can’t reproduce it. If you can’t reproduce it, you can’t validate the fix. One action drives another, impacts another, and makes another come to fruition. Without knowing the problem, you cannot reproduce it, without reproducing it you cannot test it. You need one to do the other, otherwise you are not validating anything.