Good Architects find the bad in a design that you might be in love with and perfectly aligns to your comfort design. They look at what you’ve done and show you where it could fail and point out gaps you might have missed. They are the second set of eyes that raises the game of your code and ensures you are learning new things all along the way. In short, they ensure quality is delivered,…
Done, is not always the checkbox on the project plan. Sometimes, Done can be the first step in having an idea of what to do next and creating the spark for the discussion that will ensue. Done can be so much more than what we treat it as today.
This is a question to ask your team – What kind of team are we? Are we the kind of team that follows the rules? Do we listen to each other? Do we tell each other what to do or coach each other? Do we push the envelope? Do we lead by example? It could be all of this, none of this, some of it, or more, but the important part is to know what…
I stumbled across some very old books a few nights ago that related to the construction of houses. It went deeper than books today have because the materials were different, whereas today there are myriad options of ways to build a house (and that which are still evolving), but when those books were written they were not. But what they built was solid. In building the future, it’s never a bad idea to consult the…
Every leader has the big goal at the back of their mind, the unseen goal, the one that doesn’t result in releases, bug fixes, accolades, or upgrades. It’s something bigger, something on a grander scale. Make our code better. Respond quickly to customer issues. Gain better code coverage. Ensure all aspects of the suite are covered. These are the goals that push the team forward and result in great releases, bug fixes, accolades, and upgrades.