Articles for category: Initiative

February 20, 2023

Greg Thomas

When Styles Collide

Everyone has a different style of getting something done. Whether leading people, coding, testing, strategizing or writing requirements. No one does it exactly the same way – and that’s great because then we can learn from each other. When your style collides with someone else’s, the immediate reaction will be – “I do it this way and I know my way works” – because… well… it has. But the second thought you should have is – “Will it achieve the same goal as my style?  Will I get what I need out of it?  Am I losing anything from this?”.

February 17, 2023

Greg Thomas

Your Meeting Contribution

If you aren’t contributing to the meeting, you might not need to be there. If the push is to still have you there, that means you are there in a support role to speak up when it comes to needing to hear another voice. But if you’re not even doing that, it means you are there because we don’t trust that you’ll get the information you need to do your job successfully. That’s the problem with meetings.

February 15, 2023

Greg Thomas

The Clicking Moment

The clicking moment is an easy one – it’s when it all comes together and everyone goes “oh look it worked”! They don’t see the hours, days, weeks, months, and maybe even years of work that went into getting it to that point – all they see is when it clicks. That’s okay, you know what went into making that happen, the drive and initiative for it to happen. You know what it takes to make things click and that’s what matters to be able to lead yourself and others there.

February 13, 2023

Greg Thomas

Leading Devs: What value in a Meeting?

We all have meetings and they aren’t going anywhere. Status meetings, Standup Meetings, Townhall Meetings, Update Meetings, Meetings for the Meetings, Meetings that maybe could have been emails, New Announcement Meetings, Interview Meetings, etc, etc, etc, the list goes on. And when it comes to your team being involved in meetings there are only two questions you should always be asking yourself. Are they getting something out of this meeting? i.e., are they contributing OR are they coding away on something else? Do they know what the follow-up from the meeting is? If you aren’t engaged in a meeting, you’re

February 12, 2023

Greg Thomas

Leading Devs: The Daily Pulse

Developers crank out code. Not by how many lines they do, or how much they get out the door, but by how they design it, test it, debug it, architect it, smoke test it, and compare it against different frameworks, etc, etc, etc. They do all that work to crank out code. When doing all those tasks, developers go into a tunnel (or the cave).  I love working in the cave, my headphones are on (sometimes no music), and I’m just working away focused on those problems because I need to get them done. To crank out code. As a

© 2025 Rambli by Greg Thomas. All rights reserved.