1 / 8

Test or Crash: Tobiloba Aramide Ogundiyan’s Take on Software Reliability

Tobiloba Aramide Ogundiyan believes that testing isnu2019t just a step in developmentu2014itu2019s a mindset that defines software quality. In his work building distributed systems, he has seen how minor issues can escalate into major outages when testing is neglected. He advocates for rigorous, continuous testing to uncover failure modes before they impact users. For Ogundiyan, systems are either battle-tested or brokenu2014itu2019s that simple.<br><br>

Tobiloba
Télécharger la présentation

Test or Crash: Tobiloba Aramide Ogundiyan’s Take on Software Reliability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TOBILOBA ARAMIDE OGUNDIYAN WHY TESTING CAN’T BE SKIPPED

  2. INTRODUCTON Tobiloba Aramide Ogundiyan is a renowned backend engineer known for his expertise in distributed systems and email authentication tools in Go, and his unwavering commitment to testing. Tobiloba Aramide Ogundiyan, lead backend engineer at Apprentice Systems, emphasizes the importance of testing in software development. He believes untested code can lead to failure and shares his experiences on his blog, Aramide.dev, emphasizing the importance of testing.

  3. TESTING AS COMMUNICATION Tests serve as a reliable form of communication, providing detailed descriptions of system behavior in specific scenarios, often more accurately than comments or README files. Unit tests define contracts between components in complex systems, integration tests ensure pressure-hold, and end-to-end tests validate user experience. Deep testing ensures clear understanding expectations and tolerance, benefiting debugging by providing clues. of system

  4. GO AND THE TEST-FIRST MINDSET Go, a language known for simplicity and explicitness, has FISCAL YEAR 2021 built-in testing tools that make testing frictionless, promoting fast tooling, clean syntax, and modular design. Writing the test case first in a workflow helps focus on defining behavior rather than implementation. This approach makes design clearer and goals measurable, accelerates iteration, and allows for quick changes in internal design. Tests catch any regressions, ensuring confidence in the design.

  5. RESILIENCE THROUGH TESTS Resilience is viewed as a commitment to testing, ensuring predictable behavior under stress. Reliable systems are trusted to behave the same way tomorrow as today, building trust through frequent testing. Distributed systems face inevitable disruptions, but resilient systems are designed by anticipating these events. Engineers replicate failure conditions during testing to design systems that recover smoothly, as untested systems are more likely to break unexpectedly in production.

  6. BEYOND THE CODEBASE The engineering approach to testing is not just about testing but also about documenting and sharing the learning process behind it. The blog features stories, reflections on mistakes, missed edge cases, and unexpected behaviors. The author writes tests for the team, not just the code, aiming to elevate testing from a mechanical duty to an act of care. This human-centered approach elevates testing from a mechanical duty to an act of care for the next developer, operator, or customer.

  7. CONCLUSION In the tech sector, prioritizing discipline and predictability can lead to a more reliable and trustworthy approach. Engineers value reliability and testing as the foundation of trust. Despite evolving tools and frameworks, the principle remains: if it matters, test it. Tested code tells the truth, while untested code only tells a story.

  8. THANK YOU www.crunchbase.com/person/tobiloba-aramide-ogundiyan

More Related