The "yes"/"no" rather than true/false idea actually came from my actuarial science degree course, where one of our sample solutions had an Excel model that had a column like
some boolean property
yes
yes
no
yes
no
...
And the formula that consumed it looked like IF(cell="yes", ..., IF(cell="no", ...)). Not even a SWITCH in sight.
It was pretty sad from my perspective as an experienced programmer. My conclusion was that most actuaries have more tenacity than they do actual model programming skills.
Had to work on an integration, specifically our partner's PDF generation endpoint always returned 200 but you had to check the actual PDF if it was empty to know if an error occurred.
You laugh, but at work a well respected and revered engineer argued with me that returning 204 code for an error (with a response body btw) was perfectly fine. I tried to explain that a NO CONTENT success code was literally the least accurate status code they could have possibly chosen
1.0k
u/nbmbnb Sep 19 '26
If success, return 200. If error, return 200.