Articles for category: Initiative

LeftOver Code Snippets

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.

Cyclical Loopholes

If you’re looking for loopholes to save the day and get your project done or product out the door you better be prepared to keep looking. Because once you find one loophole, chances are you are going to need another. And once you find that one, you’ll then need another. Loopholes are cyclical implementations of constantly trying to find your way out of a problem of your own creation. The further down the loophole you go, the harder it becomes to break out of the cycle as breaking out means throwing out the initial loophole that got you here in

Tackling Bad Code Performance

You can either tackle a code performance when it happens (i.e., fight the fires) or you can create a plan to tackle it. You will never get away from fighting the fire approach, a scenario, a use case, will always pop up and make you stop and think – “huh, I never thought about that”. But you can look to the other 90% of scenarios that you know of and work through the scenarios that could be better now so that hopefully when those performance fires flare up with a customer, they are not as bad as they could have

June 28, 2022

Greg Thomas

Inclement Weather Tendencies

You can go out and do things when the weather is bad. But you don’t want to do it all the time. Who wants to have a picnic day in and day out in the rain, each and every day. No one. Every now and again we’ll make an allowance for it so we can “brave the weather” and not “wimp out” – but doing this day in and day out is enough to have you wanting to stop doing the activity altogether. The same is true with our work, what activities are we doing that we can account for

Planning by Fires

“We’ve been delivering based on our fires over the past two months.” That’s what you hear when you are focused on customer issues, in triaging the immediate and getting the fixes out the door before asap, where the customers are beating down the door to get your code to work. And you’ve probably been successful at this, but you can only do it for so long, there are only so many times you can plan by the fire until they become little hacks, little pieces of debt that will turn into the next fire. This is why, after the fire,