Month: July 2022

July 19, 2022

Greg Thomas

The Gap Between Waterfall and Agile

Where companies struggle in their adoption of Agile is that they implement it within a small area of the company where they learn to do it really well.  They get good at it and they get into a rhythm of what they are doing. They have tweaked the idea of Agile to meet their needs and goals and they have a system that is working and moving products and code out the door. What they don’t have is a way to translate the rest of the company’s previous Waterfall mindset of – deliver on this date, what is the percent

July 18, 2022

Greg Thomas

What every bit of code you write should have

It should be testable. It should defend. It should be clear to understand. It should catch errors. If it is not the sole source of all the logging, it should provide valuable fragments that render what it logs usable. It should do what it is meant to do, not what we hope it to do

July 17, 2022

Greg Thomas

Cloud Hides the Bad Code

Yes, it does, there is bad code in the cloud, not all code, but a good amount. Because you can easily throw more “stuff” at it to make it more “elastic” and “spinning” up things makes it more performant. These tactics work in the short-term and get you out of a jam, but that’s all they are meant to be, if your code is performing badly, no amount of memory will ever make it run better. If you have a leaky roof, you don’t keep putting more and more shingles on it each time it leaks, eventually, you need to

July 16, 2022

Greg Thomas

Try… Catch… Wonder…

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.

July 15, 2022

Greg Thomas

There are always Two Responses

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 aren’t feeding the machine that continues getting everyone riled up to the point of carrying pitchforks onto ZOOM calls.

© 2025 Rambli by Greg Thomas. All rights reserved.