Category

Drive

Category

On any project I lead, I encourage Devs to log bugs. Log them all day, every day. That’s the job. You find an issue, you log it. You break something, you log it. No one has an infallible memory and if you are never logging bugs, all you are doing is making yourself look like a slow developer on that one task or story you are desperately trying to complete. Show them what you are…

This is one of those knives through the heart type of thing. You have a team working towards a delivery, everyone has their piece that they are responsible for. At the meeting to discuss where things are on the deliverable, the team clearly has a lot left to do and is working through how they are going to accomplish that. You’ve just gone through all the issues when someone chimes in – “My part is…

What does that sound like to you? The sound of a keyboard furiously hitting the keys? The sound of a chainsaw revving up? The sound of knuckles cracking? The sound of laughter and excitement? The sound of silence? Whatever it is, we all have them, they are the sounds that when we hear them, we know amazing work is going to get done, be produced and wow us. Find your sounds.

Pushing out a meeting once is okay, acceptable, go for it, do it. Pushing it out twice, that should raise eyebrows and prompt questions. Why? What do you need? How can we help? Pushing it out a third time? Before you click send, look at that meeting, will it actually happen by that time? Do people need to know that it’s scheduled to feel safe about what they are doing? All you are producing at…

At some point in a remote meeting, depending on the complexity of the topic, not everyone is going to get it. That’s life, it’s going to happen. You can sit there trying to explain it for the fifth time or you can pull up the crappiest, most basic Paint program and draw it out for them. I swear, I have pulled up Visio, Figma, different drawing programs, UML diagrams, etc, etc – sometimes they work,…