I have seen this, but with “Y”, “N” instead. That was the way the database stored it and the way the UI displayed it, but everything inbetween converted to boolean instead, because there was logic depending on those choices. It wasn’t that bad, all things considered, just a weird quirk in the system. I think there was another system that did just use those strings plain (like WHERE foo = 'Y'
in stored procedures), but nothing I had to work with. We just mapped “Y” to true when reading the query results and were done with it.
(And before anyone asks, yes, we considered any other value false. If anyone complained that their “Yes”, “y” or empty was seen as false, we told them they used it wrong. They always accepted that, though they didn’t necessarily learn from it.)
deleted by creator
GOTO is the only thing that makes sense. It’s the “high-level” concepts like for-loops, functions and list comprehension that ruined programming.
series.append(series[k-1]+series[k-2]) for k in range(2,5)]
RAVINGS DREAMT UP BY THE UTTERLY DERANGED
And with “this decade” you mean within the last 10 years or since 2020? Either way, I’m scared… Just kidding, if this is a bank we’re talking about, they’re actually ahead of the curve.
Did you know that the type of a variable is determined by the frequency of plasma oscillations among the objects valence electrons?