I call it the Upfront – it might have other names to you, but this is possibly the least offensive one. What happens at the Upfront? The upfront is a meeting where everyone that is attending knows that brutal honesty is required. There is no room for niceties and hand holding, it’s an all out discussion that would take place in a warroom if it were happening. There is a big problem and it requires…

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.

There is an old adage that developers are lazy and will automate what they don’t want to do. I don’t know if this applies to developers per se. I mean I could walk to work, but driving a care is faster and if I have a self-driving car, I’ve pretty much automated the task for myself haven’t I? Irregardless of my profession. But Automation is a promise and always will be. A promise to fix…

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…

Three times. Three times until your estimates mean something on what you are working on. The First Time – You’re new to whatever it is you’re creating. You are learning as you create, you are going down rabbit holes and filtering out new ideas and throwing away initial designs. The Second Time – You know enough to be dangerous, but you are still learning. You have picked up some tricks, did a learning and validation…