Try – What we are attempting to do. Catch – If what I was trying to do doesn’t work and it blows up, Wonder – Perhaps I should try this alternate path instead. It sounds nicer than Finally.
Every question has two responses. The knee-jerk, shoot from the hip, get off my back, I’m tired of this, you don’t know what you’re talking about, this is a waste of my time response. Or, the “take a step back”, read it again, don’t rush to respond, gather the information and this must mean something to you response. The latter doesn’t mean you are ignoring the potentially valid issue being raised, it simply means you…
You have 8 eight hours to fix this issue that you know nothing about with minimal logging, maybe a screenshot, and 5 customers all complaining about similar issues but not really the core of the issue. Go. No one wants to work like that and yet we let it happen again and again and those that do it are proclaimed as heroes for saving the day. Here’s the hero I want – the one that…
Every application has some level of Technical Debt. Some of it exists in our tracking systems, but most of it exists in our minds, slack channels, or forgotten conversations we have with each other, later to be forgotten when we start on something else. One of the hardest jobs of being a Software Manager is being able to enunciate where your team’s debt is and push the work that needs to be done, to get…
We all have leftover code lying around ready to be used. But like any type of leftovers, they are not perfect. They need to be reheated, perhaps rejigged into something else, maybe even dressed up a little more. No one eat’s leftovers as is, code snippet leftovers are the same, they are a start to something better.