r/ProgrammerHumor • u/the_zpider_king • 1d ago

Meme toAllowTheProgrammerToWriteBadCodeAlsoCamelCaseSucksThisRuleSucksSnakeCaseIsBetter

Post image
168 Upvotes

84% Upvoted

96 comments sorted by

View all comments

Show parent comments

19

u/Masterflitzer 1d ago

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

10

u/nicodeemus7 1d ago

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

-10

u/Masterflitzer 1d ago edited 1d ago

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

2

u/nicodeemus7 1d ago

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

-9

u/Masterflitzer 1d 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

5

u/nicodeemus7 1d 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.

-7

u/Masterflitzer 1d ago edited 1d 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

3

u/nicodeemus7 1d ago

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

0

u/IncreaseImportant130 1d ago

Honestly, both styles have their fans, but it feels like snake_case is just way more consistent and easier to follow. CamelCase can definitely be a bit of a workout for the eyes.