I find it quite fascinating how many failures in complex systems could be avoided if we simply... tried again. So how so you retry effectively, so that your systems are much more fault-tolerant and less brittle?
Read more: <a href="https://256.nurkiewicz.com/9">https://256.nurkiewicz.com/9</a>
Get new episode straight to your mailbox: <a href="https://256.nurkiewicz.com/newsletter" rel="ugc noopener noreferrer" target="_blank">https://256.nurkiewicz.com/newsletter</a>

I find it quite fascinating how many failures in complex systems could be avoided if we simply... tried again. So how so you retry effectively, so that your systems are much more fault-tolerant and less brittle? Read more: https://256.nurkiewicz.com/9 Get new episode straight to your mailbox: https://256.nurkiewicz.com/newsletter

I find it quite fascinating how many failures in complex systems could be avoided if we simply... tried again. So how so you retry effectively, so that your systems are much more fault-tolerant and less brittle?
Read more: <a href="https://256.nurkiewicz.com/9" rel="noopener noreferrer">https://256.nurkiewicz.com/9</a>
Get new episode straight to your mailbox: <a href="https://256.nurkiewicz.com/newsletter" rel="noopener noreferrer">https://256.nurkiewicz.com/newsletter</a>

#9: Retrying failures

Podcast for developers, testers, SREs... and their managers. I explain complex and convoluted technologies in a clear way, avoiding buzzwords and hype. Never longer than 4 minutes and 16 seconds. Because software development does not require hours of lectures, dev advocates' slide decks and hand waving. For those of you, who want to combat FOMO, while brushing your teeth. 256 seconds is plenty of time. If I can't explain something within this time frame, it's either too complex, or I don't understand it myself. 

By Tomasz Nurkiewicz. Java Champion, CTO, trainer, O'Reilly author, blogger

Technology

Podcast for developers, testers, SREs... and their managers. I explain complex and convoluted technologies in a clear way, avoiding buzzwords and hype. Never longer than 4 minutes and 16 seconds. Because software development does not require hours of lectures, dev advocates' slide decks and hand waving. For those of you, who want to combat FOMO, while brushing your teeth. 256 seconds is plenty of time. If I can't explain something within this time frame, it's either too complex, or I don't understand it myself. By Tomasz Nurkiewicz. Java Champion, CTO, trainer, O'Reilly author, blogger

Share #9: Retrying failures

Sign up to save your podcasts

#9: Retrying failures

#9: Retrying failures