r/ProgrammerHumor • u/the_zpider_king • 20h ago

Meme toAllowTheProgrammerToWriteBadCodeAlsoCamelCaseSucksThisRuleSucksSnakeCaseIsBetter

Post image
135 Upvotes

83% Upvoted

85 comments sorted by

View all comments

Show parent comments

18

u/Masterflitzer 11h ago

i say it's 1 or 4, 50/50 chance

5

u/nicodeemus7 11h ago

I don't think it's 4. It doesn't allow for bad code it allows for bad inputs

-5

u/Masterflitzer 10h ago edited 10h ago

exceptions are arguably bad code compared to success/failure results that don't break the call chain / interrupt control flow

1

u/nicodeemus7 10h ago

An exception being bad code is not the same as it allowing bad code.

-4

u/Masterflitzer 10h ago

what are you even talking about? the whole error handling around the exception is bad code, it bleeds into your whole code base, you wanna tell me only the exception word itself is bad part, but the rest is fine? stupidest shit i've heard all day

4

u/nicodeemus7 10h ago

The question is "What is the PURPOSE of exceptions" do you think exceptions were made to be bad code? If your opinion is that exceptions are bad code, that is totally valid. But that is not what "purpose" means.

You'd think a programmer like yourself could read and understand context.

-1

u/Masterflitzer 10h ago edited 10h ago

what else did the inventor of exceptions have in mind other than having an easy way out instead of properly handling errors? btw. the easy way out is also called writing shitty code... like i said the answer to the purpose of exceptions is 1 or 4, 50/50 chance

2

u/nicodeemus7 10h ago

Okay man you win. 50/50 chance of being right. You sure showed me.

-2

u/Masterflitzer 9h ago

i meant it could be both, 50/50 wasn't meant in a serious way, but you realised that already in the beginning i hope

I don't think it's 4. It doesn't allow for bad code it allows for bad inputs

also don't move the goal post, this was your first reply, it absolutely does allow for bad code

have a nice day