37. Is software a loser’s game?

A recent blog post by Tyler Hawkins highlighted how software is a loser’s game. The blog discusses the differences between a winner’s game and a loser’s game where the main difference is how the game is won. Professionals play winner’s games. Amateurs play loser’s games. In a winner’s game, the winner wins the game because of their skill. In a loser’s game, the winner wins not because of their skill, but because the loser had more errors. In a loser’s game, the winner simply had fewer errors than the loser. If software is a loser’s game, what can we learn from this idea? If losers lose the loser’s game because they had more unforced errors, the good news is that to win at the loser’s game we simply need to ensure we don’t make the same errors over and over again.Topics:• 03:31 – What is a loser’s game?• 04:12 – In a loser’s game you lose the game for yourself• 05:53 – In a loser’s game you lose the game for yourself• 07:21 – Often these are debatable things• 08:01 – Imagine if doctors were like software engineers• 08:58 – There are no official professional standards that everyone is held to• 10:28 – Standards bodies for software have gaps in where they have standards• 11:29 – Most of us have different standards• 13:04 – Continuously learn and change your ideas based on the context• 14:19 – Software is different from the other profession in that every app is different• 14:51 – What’s the difference between the expert and an amateur• 15:56 – These errors aren’t necessarily bad if we learn from them• 17:26 – Are certifications the answer?• 19:45 – The more we learn the more we fall into the hubris trap• 22:25 – We think we have the answers so we don’t evaluate all of our options• 23:13 – There are strategic and tactical unforced errors• 24:48 – Unforced errors in software often have cascading effects• 28:25 – Constancy, rigor, and restraint are what’s missing• 32:47 – The other end of the rigor is accountability• 34:14 – Keep receipts along the way• 37:10 – Maybe our team culture is to blame• 39:12 – Not improving team culture is an unforced error by the leadership teamHelpful Links:• Software Engineering is a Loser’s Game• Accelerate: The Science of Lean Software and DevOps• tylerhawkins.info• The Loser’s Game by Charles Ellis• Niels Bohr Quote—– Thanks for listening! We hope you enjoyed today’s episode. If you liked what you heard, be sure to like and subscribe wherever you get your podcasts! If you enjoyed today’s episode, please leave a comment and a five-star review. It helps us out a ton. If you haven’t already, sign up for our email list. We won’t spam you. Pinky swear. • Check out our website •