---
title: "Discussion on \"None Is Not an Error\" | Hashnode"
description: "Discussion on \"None Is Not an Error\". I have a small CLI tool that looks up an MLB player's season stats by name. The lookup used to fail without ever raising anything: if the MLB API had no player matching a name, search_player_id printe"
url: "https://hashnode.com/posts/none-is-not-an-error/6aa56ab8a7f8ab9fcaf90ebc"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [None Is Not an Error](https://jeffthoensen.hashnode.dev/none-is-not-an-error?utm_source=hashnode&utm_medium=feed)

I have a small CLI tool that looks up an MLB player's season stats by name. The lookup used to fail without ever raising anything: if the MLB API had no player matching a name, search\_player\_id printe

Sep 12 · 2 min read · jeffthoensen.hashnode.dev  
Read the article

-   [#python](https://hashnode.com/tag/python)
-   [#testing](https://hashnode.com/tag/testing)

## Written by

[Jeff Thoensen](https://hashnode.com/@jeffthoensen)

@jeffthoensen · Atlanta, GA

  
[View profile](https://hashnode.com/@jeffthoensen)

QA Engineer focused on users, not just test cases

I’m a QA engineer with a background in customer support, which gave me a strong sense for how bugs impact real users. I spend most of my time doing exploratory testing, working closely with developers, and building out automation with Playwright. I care about catching what actually matters, not just passing checklists.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.