Articles for category: Drive

That Meeting

We all have “That” meeting. The one we dread. The one we dont’ want to attend. The one we already know what is going to be said, how people will respond, and how it will end. What if YOU could change that meeting? What if YOU could make it better? What if YOU knew what could be done to make it better? As an attendee of any meeting you always have two rights. Make it better. Stop attending. Number 2 isn’t about giving up, if you’ve tried Number 1 with nothing changing, then it’s time to find a way to

May 17, 2021

Greg Thomas

The Merge

Not the company merge, but the CODE merge. Minor CODE merges aren’t a problem, but the big ones, the ones we have drifted so far apart on for too long, that we have been afraid to merge back in because “it’s not going to be run anytime soon” – those merges, those are the ones that strike fear into a developer’s heart. The first question a developer will ask is – “how long”? And if the answer isn’t “not long”, minds start racing with impacts and outcomes as to what might happen and ways to mitigate what will invariably happen.

Breaking out of the Box

Every day, you’re in a box. You’re on who knows how many calls per day that are in a box. Whether you’re on video or whether it’s your name in a black box. It’s a box. And that is what you have, at your disposal to get people wanting to hear what you have to say, in a sea of more and more boxes. Blurred backgrounds and pictures of beaches aren’t going to help you. What you have to say, how you respond to what people have to say, how you prepare and what you do after the meeting –

Be the Conduit

A conduit is a pipe, it is a delivery system for getting work done and shipping materials from Point A to Point B. That is their job, and as a leader, that is a part of your job to. Working with your team to get Code from A to B. Growing your team from C to D. Implementing Innovation from E to F. Not everyone knows the path, the direction, the pipe they need to take. That’s why they come to you, the conduit, because they know, no matter what challenges lay ahead, you always find a way to make

Where you at?

When I ask a developer where they are at in their work, I’m not looking for the rosy picture, the hopeful optimist or any other unicorn answer. I’m asking for where they think they are and what they have left to do. To be honest, I’d rather they lean to the side of being a little more realistic (or if you want to call that negative). Why do I want this? So I can provide them the insulation they need to get the job done that they need to do and that I trust them to do. Straight, simple, direct