---
title: "Comment by netproxy on \"Day 01: Why your first agent should be 40 lines, not a framework\" | Hashnode"
description: "The point about raise_for_status() is a good one — a bad key failing as KeyError: 'choices' three calls later is exactly the kind of debugging session that make"
url: "https://hashnode.com/posts/the-40-line-agent/6ac903a79a41abbf2103357a/comment/6ac96e58928ea6e148dbc542"
---

[Discussion](https://hashnode.com/posts/the-40-line-agent/6ac903a79a41abbf2103357a)

Comment [Day 01: Why your first agent should be 40 lines, not a framework](https://hashnode.com/posts/the-40-line-agent/6ac903a79a41abbf2103357a)

[netproxy](https://hashnode.com/@argumentmoney8117)

[Oct 9](https://hashnode.com/posts/the-40-line-agent/6ac903a79a41abbf2103357a/comment/6ac96e58928ea6e148dbc542)

The point about raise\_for\_status() is a good one — a bad key failing as KeyError: 'choices' three calls later is exactly the kind of debugging session that makes people distrust their own code. Starting raw makes the failure modes visible. Looking forward to the rest of the series.
