Artwork

Content provided by Connor McDonald. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Connor McDonald or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Testing: The importance of trying to break stuff

29:04
 
Share
 

Manage episode 335905572 series 3376484
Content provided by Connor McDonald. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Connor McDonald or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

With the modern trend of automated testing, it is often easy to fall into the trap of relying solely on automation, especially when emotionally as developers we hard-wired to a bias of success. If you write working code, you are valued by your team. Your remuneration and career progression are often linked to working code. Thus as motivated as we want to be about finding bugs in our code with thorough testing, it is easy to fall prey to writing "blue sky" applications; applications that only work well when the conditions are right.

But part of the developers job is to discover how their code works when the storm clouds hover. How does your code hold up under more extreme conditions? In this episode, I'll talk about why testing to destruction is an important part of building successful database applications.

If you like this episode, be sure you hit the Like button and share it with your colleagues. Catch me on Twitter at https://twitter.com/connor_mc_d if you have comments and questions.

  continue reading

41 episodes

Artwork
iconShare
 
Manage episode 335905572 series 3376484
Content provided by Connor McDonald. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Connor McDonald or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

With the modern trend of automated testing, it is often easy to fall into the trap of relying solely on automation, especially when emotionally as developers we hard-wired to a bias of success. If you write working code, you are valued by your team. Your remuneration and career progression are often linked to working code. Thus as motivated as we want to be about finding bugs in our code with thorough testing, it is easy to fall prey to writing "blue sky" applications; applications that only work well when the conditions are right.

But part of the developers job is to discover how their code works when the storm clouds hover. How does your code hold up under more extreme conditions? In this episode, I'll talk about why testing to destruction is an important part of building successful database applications.

If you like this episode, be sure you hit the Like button and share it with your colleagues. Catch me on Twitter at https://twitter.com/connor_mc_d if you have comments and questions.

  continue reading

41 episodes

모든 에피소드

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide