They stare you in the face and countdown to the end of a pre-defined time. What do they really do? They stare you in the face and give you the indication that this thing you’re working on, this thing you don’t want to do that you wish would end, will be over, at some point, boiled down to minutes and seconds (no one sets a timer for an over an hour). And they get you…
It’s not what’s written down. It’s not your job description. It’s not what people think you do or what they ask you to accomplish. It’s what your team needs, that’s your role.
We all have our set of GOTO tools when we need to work a problem. Markers, Whiteboards, NotePad++, libraries, extensions, plugins, etc, etc. Starting with a new set of tools that are not your own feels wrong, out of place, and forced upon you. It feels like you are trying to crush a square peg through a round hole and it refuses to go. You keep pounding it in, but it won’t go. Give them…
Frameworks for one always work, always do exactly what you want them to. They are the most intuitive systems on the planet that can never fail no matter the bug or the error. But what happens when it becomes a Framework of Two? Or Three? What is the cost to move to more than one user consuming your framework? Could be what you have built isn’t a framework, but rather a collection, still a great…
Did you show up? Did you do the bare minimum? Were you there but not engaged? Did you give to try your best? Could you have done better? Checking the box isn’t enough, it never was, and it never will be. The next time you find yourself in that scenario, ask yourself what you could accomplish if you did more next time – not for others, but for you.