Articles for category: Growth

3 hours ago

Greg Thomas

Footwork and Repetition

If you want to be good at soccer in the long run, you need strong footwork. Over time, we all get slower; we can try to slow it down or improve our stamina, but we all get slower. It’s just life. But footwork, footwork isn’t built on speed, it’s built on control, repetition, and most importantly, being able to handle the ball without looking at it. Repetition and being able to handle the ball without looking at it – seems like an important skill for a job when speed fails.

3 days ago

Greg Thomas

Now I understand High School

I was never a math or science major in school, and strongly disliked having to show my work. I wanted to figure out the answer in any way I could, and just give out the answer and get the full marks. Now with AI, I’m seeing code and ticket changes that go from a blank class file to a fully fleshed out solution – that might work well – but hasn’t been removed. It’s a good reminder for me as I use AI, that yes, it’s important to keep showing my work. The differentiator won’t be the answer; we all

4 days ago

Greg Thomas

The AI Cut and Paste Dilemma

When a ticket goes from no content to 1000 lines of content, here is where my mind immediately goes now. I use AI to help me troubleshoot and track down problems – no one knows it all – and that goes for you to AI! After being burned a few times, with AI usage, I have found myself now in an instant doubting mood when I see long pieces of content come my way, where I now have to remind myself – someone might have put a lot of effort into this and I should give it the time it

5 days ago

Greg Thomas

The Era of “I think this is the problem.”

We are exiting the era of someone knowing the answer and entering the era where everyone around the room can say – “I think it’s this”. During a call, everyone can bring up their AI tool du jour, copy and paste an error message in, and come back with a “I think it is this”. It’s not the answer; there is no analysis, there is no surety in what we are trying to solve. Having more information is great, but if it’s not directed to the solution at hand, it’s just more noise. Whereas we used to have people who

6 days ago

Greg Thomas

Counting Token Shock

Counting Lines of Code became… Counting Number of Unit Tests Generated became… Generating the number of class files became… Ensuring we had everything commented, which became… An unlimited number of TODOs in our code. And now we are counting Tokens of usage and surprise, surprise – we are gamifying and overusing them so that our metrics look inflated. I AM SHOCKED!!!! Yes, your team should be using AI. But if you’re measuring your team by their token consumption, it’s a lazy, easy metric. Instead, why not look at; As with development metrics of the past, the first metric identified is

© 2025 Rambli by Greg Thomas. All rights reserved.