Month: January 2022

January 31, 2022

Greg Thomas

The Great Resignation for Developers

I came across this article last week on StackOverflow – The Great Resignation as it applies to Software Developers. It’s a pretty good read – unfortunately, it’s nothing new – all of these elements of being a software developer existed before – all the Pandemic has done has made them visible (more so before). Burnout is not new, the term might have even been invented by Software Developers. The section on “Challenges for Managers and Team Leads” was missing something though – GROWTH. Everything mentioned previously in the article speaks to why developers are leaving – freelancing, more money, culture

January 30, 2022

Greg Thomas

What are we Measuring?

If you don’t know what you are measuring, what the goal is, what matters in the end. What are you building for? How are you building it? And what will it be what you need when you get there? Knowing what you’re moving towards (and your team) is the most important part of your delivery. It might get repetitive as you ask the same questions over and over as your spidey sense tingles when you sense confusion is near.  But the more you ask, the more it will spurn others to ask as well. And if other’s are asking, then

January 29, 2022

Greg Thomas

Embedded Leaders

Whether it’s a team you work side-by-side with, interact with, or talk to now and again. You won’t get a view as to just how things are truly working until you embed yourselves within all the activities you do. The standups, the team meetings, the updates, the delivery, everything. It’s only then you can get a feel for how things are working and what needs to be done to help them. If you’re not on the inside, if you’re not side-by-side with them, all you’re doing is watching. You can’t sit beside them in a remote world, but you can talk

January 28, 2022

Greg Thomas

Meeting Presets

Every meeting, whether it’s Zoom, Meet, or Teams – the same ritual occurs. Setup my layout the way I like it for meetings and presentations, do all the fiddling around. And then go. Why these presets cannot be saved, I’ll never know. Why functions I don’t need or have never used that need to be on, I’ll never know. If you’re throwing features against the wall hoping they’ll stick and no one is using them, you’re probably missing the point. The point being the user is having to clean up features from the floor just to make your product work.

January 27, 2022

Greg Thomas

Know Thy Product

I spent a number of hours on the phone, email, and chat with a company I’ve worked with for years trying to get a simple answer to a basic question.  I even had my account representative call me out of the blue and tell me they are here for me if I need any help. I did need help, but they didn’t look at my account to see there was an open case. I updated the case three days in a row (the last day primarily just to ask if anyone was there). After the final online chat that went

© 2025 Rambli by Greg Thomas. All rights reserved.