October 25, 2019
Heads Down Meeting
If you are in a meeting and haven’t taken your eyes off your phone or laptop – you probably didn’t need to be there. It’s a simple barometer check to see if you are providing value or losing time to finish wh
October 25, 2019
If you are in a meeting and haven’t taken your eyes off your phone or laptop – you probably didn’t need to be there. It’s a simple barometer check to see if you are providing value or losing time to finish wh
October 22, 2019
Then don’t ask for feedback. Ask for validation instead, because the answer will always yes (or begrudgingly be yes when you emphasize that you are looking for validation). But if you can handle hearing No, your path to growth will be all the better because of it.
October 16, 2019
We can iterate, nimble, agile, push, ship daily and continuously improve as much as we want, but if the team isn’t catching up you’re doing more harm than good. This doesn’t mean you give up, this means you find the breaking points, you find what is holding people back and you zone in on them. Doing the basic math, if they are stuck on Step 1, then you know they are going to be stuck on Step 5, so going ahead to Step 5 will not do them any good. You know that feeling you have in a meeting, when
October 15, 2019
Always Lead to Win Always Play to Win. Always Code to Win. Always Bake to Win. Always Ship to Win. Always Wake up to Win. Always Debate to Win. Always Knit to Win. Always Create to Win. Always Check-In to Win. Always Compile to Win. If your whole purpose is to win, in everything you do, how will you focus on growth? What does you being first to complete your code, leaving the team behind do for the overall feature delivery? What does having checking in your work before the interfaces are completed do for builds? What does having all
October 8, 2019
No one knows everything about anything and if you work hard enough, you can figure out what they don’t know. For this reason, programming tests in Interviews are a lost cause because what they focus on is the application of memory and not methodical approach to solving something you don’t know. When someone doesn’t know the answer, I want to know what they are going to do to look it up; Google it. Podcast it. StackOverflow it. MSDN it. Slack it. Reach out a peer. Call a friend. All of these pieces are methods to solving problems that are constantly