November 27, 2022
They aren’t supposed to, that’s the idea of preparation, you do it solo. You choose the task. You choose the priority. You make the changes. You choose what’s next. You decide where you need to go. The only person that notices is and will be you.
November 26, 2022
It’s easy to do the things that don’t challenge you, don’t push you, don’t force you to rethink what you are doing, and give you that boost of what you are good at. It’s much harder to realize you’re not good at everything, that one thing you are struggling with, you are struggling with for a reason because it’s not easy. That “thing” you working on, you might be the only one working on it and everyone might be staring at you wondering why you are working on it, because it’s tricky, because it’s tough but in the end you
November 25, 2022
Event planners have it tough. They put everything they can into making something go off smoothly, perfectly, without a hitch and along the way something always goes wrong or off the rails. The secret is that they never let anyone know that something has gone wrong, they never show it on their face, they roll with it, they recover and they move on. There is a degree of experience worked in there as well as they look for cues to respond to in advance when they are about to happen. We all need to channel our internal event planner on
November 24, 2022
Oftentimes we compare the wrong things. They are better than us, but they are always three years ahead of us in development. Your code is faster than mine, but yours also does less. Your team works better together, but our projects are also different. The list goes on Infinitum, but the question remains the same – if you are comparing apples to oranges, they will always be different. We think the time is spent in the comparison, but where it should really be spent is ensuring that we are comparing the correct things.
November 22, 2022
If you have multiple backlogs, which one does your team know to pull through? How do they know which one is prioritized higher than the other? How do they know which items that cross backlogs might be different than the others? Keep your backlogs simple so that when your team starts to pull from them, they know they are pulling from the right place at the right time, working on the right thing. Essentially what a backlog is supposed to do.
