Articles for category: Drive

May 18, 2020

Greg Thomas

Long vs Short

This is a long game, not a short one. Figure out where you want to be (long) and what steps you are going to need to take there (short). Don’t worry about the long goal until you’ve finished the short steps but if you’re doing the short steps, the long goal will solve itself. Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).

It wasn’t THAT Bad

When we think our latest effort at something was truly, horribly, the worst possible outcome, it really wasn’t that bad. When we ask someone for their opinion, it’s generally better than our own. We are hardest on ourselves. It wasn’t that bad. It’s just not as good as it was in your head. But it’s better than what others are working towards. Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).

What Agile Isn’t

An excuse to not do the work you have been doing to date and to do it right. Agile is not getting into a Tesla, dropping the hammer and seeing how fast you can go when you don’t even have a license to begin with. Agile is about iterations and delivering value. If you are not delivering value in every iteration, then it doesn’t matter how fast you are going, you have missed the point. Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).

Don’t Get Lazy While Remote

Years ago, I was working on software that had to be tested against multiple audio mics and headsets. We were interested in seeing what the experience would be and whether we could recommend it to our customers. I remember doing a demo with our sales manager, we were on a call chatting away when he popped up behind me to show how his bluetooth headset was working. This worked for our little impromptu demo with each other. This wouldn’t work for one of his sales calls, to show up behind me and tap me on the shoulder to come into

May 1, 2020

Greg Thomas

The Worst Code I Ever Wrote

The worst code I ever wrote was yesterday. Because today’s code I learned the lessons from yesterday to get better today. I tweaked it. I improved it. I made it smarter and faster. Today’s code will be tomorrow’s worst code. And the cycle continues, but the learning never stops.