Yeah, that's not what the person you were replying to is talking about. I was explaining the jargon.

Complexity and LoC has nothing to do with "only coding for the happy path". Both complex and simple software can be written this way.

A great example is the moltbook hilarity. They slapped together something that looked good and did function -- in the happy case only. They put together an "authorization" flow but exposed their entire database because they didn't know how to secure Supabase. They had no rate limiting on account creation -- so one dude created 1M in an hour.

Even putting aside adversarial usage, you have to code for, like, normal stuff going wrong or your app will lose data, crash, leak information, fall over, etc, etc.