June 5, 2023
Getting it right requires measuring twice and cutting once. It’s about making mistakes and going back to try again to be better. It’s about the bugs coming in and the updates going out. Not everyone wants to get it right because it means realizing you have work to do and that work never end. But many people do, and those are the people you want on your team.
June 5, 2023
Phasellus vel ante mi. Aliquam sit amet velit tortor. Fusce efficitur diam sit amet mauris consequat, vel vestibulum est gravida. Praesent lacinia velit nec arcu aliquam euismod at at dolor. Vivamus efficitur pellentesque nulla et vestibulum. Praesent at luctus nulla, eget convallis nunc. Mauris a dolor dictum, sagittis elit non, hendrerit felis. In non pharetra risus. Proin tincidunt felis et volutpat facilisis. Nulla dolor tortor, dapibus sit amet elit sed, aliquam rutrum lectus. Aliquam luctus tempus eros id tincidunt. Nulla ullamcorper magna in vulputate aliquet. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Sed eu orci
June 3, 2023
Every team has them. The “Ism” – the CodeIsm, the EnterpriseIsm, the SupportIsm. They are the ideas, the culture, the vernacular that makes your team, your team and separates it from everyone else. They are the rallying cry for getting things done and delivering. They are a good thing to have as long as they project the good of your team and not the “that’s the way we have always done it”, “that’s how it works”, “we don’t know what it really does” – then they go from being an “ism” to a problem.
June 2, 2023
What I admire most about video games, is their resiliency to consistency deliver updates. Maybe I’ve been lucky but when I look at the games I’ve played, and how they are updated I can’t help but think that this is where the time was spent first – on the Updates. The team figured out the problem they hoped they would have forever. Pushing out changes and ensuring they don’t impact their customers from using their product during this time. When something as critical as updating all that you do is an add-on or after thought, the propensity for it to
June 1, 2023
After one release that goes well, you’re perfect. If your second and third ones go just as well, you’ll maintain that perfection. But eventually, the more you do, the greater you open yourself up to the chance that something will go wrong, that you won’t have the perfect release. That your code might blow up. That a bug might get missed. What factors outside of your control will cause you to slip? Because presumably, you are reaching higher and higher each time, aiming to get better and better as you go. So your streak of perfection will end. The question
