When fixing something small, don’t forget to step back and look at the bigger picture. Does this apply elsewhere? Can we make this better in other parts of our software? What is the impact of deploying this elsewhere? What if as part of this work, we start building a framework that we can keep building on? Fix the immediate problem, don’t get lost in the forest, and plan for the next iteration. You wouldn’t put…
Errors happen. Errors about Errors happen. Errors about Errors about Errors happen. An error can send you down a different path. An error can also be a false positive. The point is, sometimes the error is wrong and you need to keep looking.
When the feeder gets empty, there is nothing to eat. You can try to time the filling with the feeder with when it gets to its near empty point, maintaining that perfect balance of “full but not full enough”. Or you can always fill the feeder with new ideas, new code, new words, new suggestions, new work, etc. When the feeder is full, you don’t have to worry about it getting empty. You don’t have…
Routines get broken. Work. Vacation. School. Unexpected events. It happens, the routine breaks, and now it lies on the floor laughing at you. You have a choice, leave it there, laughing, or pick it up and make it work once more – because it did before.
A random message goes out on Teams – “Who can help me with this?” Crickets. No one can. Or everyone can. But no one knows who owns it, so no one knows whether they should work on it. So no one puts their hand up. The subject line of the follow-up meeting is “Do I own this?” If the answer is yes, great, if the answer is no, great. But now we all know.