Articles for category: Growth

2 months ago

Greg Thomas

Trends on Trends

Last week I was scrolling through social media and found this cool video of a guy on a kayak, tons of camera gear, catching a fish, and cooking it on the kayak. Each time it got more elaborate with what he was cooking. Then my feed popped up with someone else doing it, with a different take on the trend; they were on a jetski, zipping around and doing the same thing. Then I saw more posts that flipped the trend a bit more, as each person had to take their crack at the trend. But in the end, there

2 months ago

Greg Thomas

The Bermuda Triangle

I did not grow up near the sea, but I heard about the Bermuda Triangle – that’s where stuff goes and doesn’t come back – so you never go to the Bermuda Triangle. Good to know. The truth is, a few ships disappeared there that got blown way out of proportion and became sensationalized – then we gave it a cool name and the rest is history. Something might be happening in your organization that no one knows why, so they give it a name, a thought, a concept – and it becomes bigger than it is. And then you

2 months ago

Greg Thomas

Various Ideas

Take all your ideas. Write them down. Order them. Prioritize what matters to you. Put them front and center in your face. Pick one. And ship. (Don’t stop at putting them in your face, this is the last step before it becomes real, where many stop, pick and go).

2 months ago

Greg Thomas

The Big Day

Big days are the summation of small moments that have all pulled together to make something incredible. Whether it’s weeks, months, or years of moments, all of them come together to create something incredible, so on that one big day it looks like a piece of cake. Big Days look great to everyone else, but to you, they are the culmination of so much work, effort, sweat, and tears. Make sure you take a moment to enjoy it.

2 months ago

Greg Thomas

Maintaining your AI

LLMs keep learning, growing, and improving. But they are only as good as the scenarios that they are dropped into. For instance; A new code library that doesn’t log errors- great when it works, not great when it fails. Requirements that use “generic” nomenclature and not what everyone else uses, only good if you’re a senior dev. QA Test Cases that generate failure scenarios for tests which don’t apply to your stack? Add extra work. Diagrams that point to systems that don’t exist (but should), don’t give you the current state. If you’re not cleaning up and working with your

© 2025 Rambli by Greg Thomas. All rights reserved.