Mirror mirror on the wall, how many code problems do we have overall?

... Im sorry I even asked

Oh my god I swear these fucking compiler warnings that are actually linter warnings always get my blood boiling. Just fuck off you useless piece of software I know how I want my fucking architecture to be so shut the fuck up

@12bitfloat i mean.. I enabled this to try to show the seniors how bad our code is to try to encourage them to change it

I got told to stop wasting time and fix the issues assigned to me

@Owenvii To be fair my comment implied that the people writing the code are competent

@12bitfloat they arn't

Some of these warnings are from them not using dispose(); aka not using 'using' statements for disposable objects...

Dear God save me

@Owenvii Yeaaaah... Sorry bout that

those are warnings, not errors

@Midnigh-shcode The only correct number of warnings is zero. Except linter warnings. Fuck those

@12bitfloat i almost agree. but they're still warnings, not errors, so the OP is incorrect

@Midnigh-shcode A warning is still a problem. Sure maybe not a serious problem but still a problem. Actually depending on the language. In C "foobar == 2;" is a warning "statement without effects" yet it is a very serious problem

@Midnigh-shcode bad code standards are a problem tho, im not incorrect at all

More warnings than most projects have LOC.

Thanks for reminding me of this song. I am going to sleep thinking on it.