Can you make your code better? Can you stop it from being so unwieldy? Can you code for the one problem that is in front of you or do you need to look at all the problems around you before you can decide? Controlling your code, what you write, and not letting it spiral out of control is one of the most difficult tasks developers have to perform. Our innate desire is to solve all…
What’s the difference? Ready means it’s ready for someone to look at and see what it looks like. Done means no one needs to look at it. One involves testing, the other states that testing has been completed. If your team doesn’t know the difference, it could be your biggest problem in knowing what is complete.
Chasing stats is a good short-term victory. It means changing what you do and what you care about to get some quick wins. It means redirecting people and resources to achieve those quick points that put a win in the column. The problem is, if you keep chasing stats in the short-term, your long-term strategy starts to fall apart, it starts to fail and break simply because you don’t have one. You’ve been too busy…
I watched this clip twice tonight, only because it is so relatable. Do we know the problem we are trying to solve? Does everyone at the table understand what we are trying to do? Are we all on the same page? We can all nod our heads and go yes, but in that case, who are you helping. Understand the problem, get everyone on the same page, move forward.
Remember having day-long planning sessions where everyone got together to figure out a problem or map out your plans for the next quarter or year? If you haven’t had to do this yet (don’t worry it’s coming) but if you have one on the horizon and aren’t sure where to start, here are a few pointers. Pre-Preparation – yes pre-preparation, before the session begins, identify what you need people to do before they get there,…