Blog

September 17, 2020

Greg Thomas

Team Impact

When joining a new team the best way to make an impact is to volunteer for something. Anything. Can I test bugs? Can I fix some bugs? Can I review your code? Can I write some docs? These are the grunt work tasks. When Grunt Work doesn’t gets done it manifests into heaping loads of technical debt. Technical debt costs your team in the longrun. So if you’re looking to make an impact – pick up some grunt work.

September 16, 2020

Greg Thomas

Thursday is the End of the Week

It’s been like this forever. By the time Thursday comes around in the week, I’m exhausted – I’ve given my all, I need to recharge. The new week starts on Friday.

September 15, 2020

Greg Thomas

Don’t Let Go of the Outtakes

I’ve ramped up my technical expertise in the past few months as I delved into the wonderful world of podcast editing for the Remotely Prepared Podcast. I enjoy doing the editing because similar to blogging and everything else, it makes me take a step back to listen to what I’m saying and find my voice in what I’m trying to do. I also get a number of ideas from that deeper thinking of things I should be writing about and drilling down into a little more. But, honestly, they are funny as anything and I mean the outtakes are funny.

September 14, 2020

Greg Thomas

The Growth Point

When we don’t know how to do something, it’s a good idea to ask for help. When we then see how hard or complicated the task is. We get this bubbled need inside of us to ask the person teaching us – “are you able to do this?” There are a ton of excuses we throw out; This is above my paygrade. This will prevent me from finishing my other tasks. It will take me longer than you. And the list will go on and on… never ending… In anything that list will go on and on and never ending…

September 13, 2020

Greg Thomas

Good Logging, Better Errors

The hidden underbelly of software development is translating what you write into something that someone understands. Someone that has no idea what you have written. And they can’t read your code. And even if they could read your code, they don’t want to because they don’t code. Enter logs and stacktraces which has given rise to one of my most favourite and longest-running memes ever. It is crystal clear, in all it’s glory. A developer cannot resolve a problem without knowing what happened – we need those logs. But what happens when the logs aren’t there? Or they are so