March 2, 2022
Someone sent me this error last week. “Could not Process” They asked me if I knew what it was or what it related to. All I could think about was how unhappy that Developer must have been at that point to have written that error with no subsequent log or follow-up information to help the next person to move forward. How bad was their day that this was all they could give?
March 1, 2022
Processes are meant to be tweaked. To overhaul them, to have the suggestion that they need to be overhauled by one person on their team means one of two things; They don’t understand the process (and thereby think it needs to change) They understand the process (and thereby know it needs to change) You only overhaul once, after that, it’s tweaking on tweaks to keep improving it and making it better. If you’re overhauling your process all the time, you aren’t in the business of whatever it was you were in before, you’re in the business of building processes (which
February 27, 2022
Grunt work never has and never will go away. It will always be there, no matter your role, it will exist, in different forms to be sure. Embrace it, learn from it, figure out how to automate it, and do something with it. From grunt work comes our great ideas for what we might work on next.
February 25, 2022
When we own something, it becomes a part of us and we want to see it succeed. It can be something as simple as a bug, a task, or any other kind of ticket. Until it’s in our name though, it’s just a thing that has to be done and anyone on the team can do it. But the moment your name gets added to it, now it’s yours, now it’s something. Now it can be anything and everything you wish for it. Because now it is yours to work on.
February 24, 2022
Too many. Too many lurking around. Too many that I don’t log into but get random texts or emails from. Too many need to be cleaned up. Too many that I don’t even know still exist. Spring cleaning is coming early.
