Articles for category: Drive

Things Will Go Wrong

Your new project, your latest endeavor, the next idea you have. Something will break. Something will not work. Something will blow up in your face (maybe on an important Zoom call). Something will go wrong. It’s life, don’t harp on it if it happens to someone else, don’t let it get you down if it happens to you. Something always goes wrong, move on from it.

February 28, 2023

Greg Thomas

Focus on their Successes

Successes build strength and courage to try what is next. There is always success in failure… An idea you tried that didn’t quite pan out, but now you know. The code didn’t work as a product but could be a feature. The process that missed the mark, but exposed the cracks that you never saw before. There is success in everything, if you are willing to look for it.

February 24, 2023

Greg Thomas

Paying for the Software Basics

Software that is stable. Software that delivers on the features that you downloaded it for. Software that is simple and intuitive to use. Do the core features work from release to release? Those are the basics of any software solution that from release to release should always be there. Everything else is an add-on bonus, but the core, the core should never be buggy.

February 23, 2023

Greg Thomas

The Agile Goal of Multiple Teams and Multiple Processes

Multiple Teams can have multiple processes and systems for what they do. This isn’t a bad thing – build the process, methodology or system that fits the team for what they are doing. The Agile methodology for software is built around tenets to accomplish goals and not implementation details itself. If you are working with multiple teams with multiple ways of doing things and each team is performing well the question should be are you able to align the processes into one display of how everyone is doing – getting from comparing bananas and oranges to applying that are honey

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?”.