February 23, 2024
Can we put everything into this fix to get it right and get it out there? Have you tried putting everything into one fix? I remember when 100 MB was considered too big for a patch and now I’m downloading 20 GB updates. Focus your fixes on the problems they are meant to solve – no one ever complained about a fix that addressed the one issue it was meant to.
February 20, 2024
Do you ship by date? By state of quality? By bugs left on the table? By customer adoption rates? By pre-order? Do you grind late into the night on the last few weeks to get it all done? Do you lay out your sprints so you have time to work on the unknown as it arises? Do you pushback on new requirements? Everything has to be cut in stone? Often times our delivery profile is pushed upon us, however, imagine the change that could happen if you stood up and said – this is how we should ship, this is
February 18, 2024
If you can’t code 8 hours a day. Can you jump in, on small tasks, and hammer out 1 hour a day? If you can’t do 5 hours a week can you find time to do 3? Bit by bit is the origin story of many overnight successes.
February 17, 2024
The next Release is always going to be the best. Until that work gets pushed to the next release. If you commit to fixing everything now, this release will become the best release where you fix everything and next release – who knows what next release will be because you won’t be spending all your time trying to fix it.
February 10, 2024
If only Levelling Up were this easy (and fun). Instead, you have to trust the path you’re on, the process, and the direction you’re headed that it will lead to leveling up, lead to getting better, and lead to getting that much closer to your end goal.
