Blog

The Time Between The Work

Breaks aren’t simply for doing nothing, they are time for figuring out what to do between the work.  They are rolling solutions over and over again in your mind before going forward with them. Time is what solves your problem and helps with your work.  If you don’t have the time between your work to get things done all you’re doing is grinding from one thing to the next with no thought in between. Take the time between to do the best work possible.

June 16, 2024

Greg Thomas

All Problems, All the Time

Problems are the bread and butter of your success. How many can you solve? How fast can you solve them? How do they scale? How much effort do they take? What is needed to fix them? When hiring, you always want problem solvers because no matter what they know, have on them or know through their network – they’ll be the ones to figure it out and that’s what you need.

The Hard doesn’t get Easier

The hard work, the problems you can’t solve, don’t get easier, they get familiar. We get better at solving them because we are familiar with all the constraints, context, and, constructs that surround them. Change any one of those components and the problem didn’t become harder again, it became unfamiliar. Step away from working on that problem for a few months and then go back to it, the problem itself isn’t harder, you’ve simply lost your familiarity with it. Your familiarity with problems is what makes them easier, nothing else changed.

June 14, 2024

Greg Thomas

Know your Basics

I saw this picture the other day and it speaks volumes, not only for sports but for work as well. Your basics are what set you apart from everyone else. Knowing what they are is what makes you indispensable because then you can start focusing in on them, refining them, and making them stronger. But if you don’t know what your basics are, what your fundamentals are – then you’re just practicing everything, everywhere and not getting anywhere.

The House Coding Test

Imagine your team builds houses akin to how they write code. Some questions to ask; How long would it stand the test of time? What issues would appear immediately? What would work well? Would it align with what your users wanted? Would it ship completed? Would it be finished early or late? You can come up with more/less questions, the point of the exercise isn’t to take your team down a notch – the goal is to realize we all like living in strong houses that do what they are supposed to do (keep us safe, give us a place