Articles for category: Delivery

July 14, 2022

Greg Thomas

Coding Under Pressure

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 prevents these days from arising the other 364 days of the year. Now that’s Leadership.

July 11, 2022

Greg Thomas

Meetings to Talk

I love the thrill coming out of a good meeting – one where a problem was discussed, a plan put in place, and the next steps laid out. It is the perfect definition for a meeting if ever there was one. Then there are the meetings to “talk”, where we schedule up the talk and take time from people’s day to have the talk. That is called a conversation, it doesn’t need to be scheduled, it just needs to be discussed. But if you find yourself having many conversations on the same topic, perhaps it’s that you don’t know what

July 9, 2022

Greg Thomas

The Grunting Grind

There comes a time when the work just needs to get done. There is no easy way around it, it just needs to happen. It might not be the most glorifying work, but it’s the work that needs to be done. Pen to Paper, Hand to Keyboard, Code to Compiler. You can keep waiting, or you can start grinding.

July 7, 2022

Greg Thomas

Asynchronous Waiting

Asynchronous communication allows for Job A to continue while another Job B happens in parallel.  When Job B has completed, it will let Job A know so that Job A can continue along. The idea is that we are not blocked waiting for Job B to finish and other jobs can carry on while we “wait” for Job B to get done.  At some point Job A will have to wait for Job B to complete, but hopefully, it will not be as bad as if it were a serial operation. Athletes are great at asynchronous operations – when they

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