There are jobs we have that we are not right for. We have all had roles that we were completely mismatched for – you might have thought it was the thing you’d been dying for, but in reality, you were catfished and now you’re doing something completely different. Even still you might have a job you were hired for with a title you aspire to be, but what you are doing is nowhere near what…
Only one person on a project ever knows where the release is truly at. Whether it’s the person that’s taking the sum of the parts or the person responsible for their own team’s part – there is always that one person on every project that has the most intimate knowledge as to what is being released. They don’t need to feel the pulse, they are the pulse, and they release pulsates at every right and…
Is it the duration that kills us? The unknown? If we knew, would we care how long it would take? If we knew how long we’d have to wait but still knew that it was an unknown would it still drive us up the wall waiting for the answer? Does it matter how many times you hit refresh or pull down on your notifications? It doesn’t. Sometimes all you can do is wait.
You don’t need the title. You never needed it before, so why are you waiting for it now? If it’s the title that matters, give it to yourself. If that’s what you need to lead your team, give yourself the best title you can think of, print it up, and put it on your desk. We’re all home now, who’s going to see it? Take it a step further and make a fancy name card…
I have spent most of this week refactoring code. Tweaking it. Optimizing it. Tracking it. Making it more performant, trying to figure out what does and doesn’t work and work, debugging through a mountain of bugs, and generally… making it work. It’s not simple work, it’s frustrating, it’s time-consuming, but it’s always eye-opening how the beauty of simplifying your work, has the potential to work that much better.