21
Owenvii
1y

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

... Im sorry I even asked

Comments
  • 5
    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
  • 1
    @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
  • 4
    @Owenvii To be fair my comment implied that the people writing the code are competent
  • 2
    @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
  • 1
    @Owenvii Yeaaaah... Sorry bout that
  • 1
    those are warnings, not errors
  • 3
    @Midnigh-shcode The only correct number of warnings is zero. Except linter warnings. Fuck those
  • 0
    @12bitfloat i almost agree. but they're still warnings, not errors, so the OP is incorrect
  • 1
    @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
  • 0
    @Midnigh-shcode bad code standards are a problem tho, im not incorrect at all
  • 1
    More warnings than most projects have LOC.
  • 1
    Thanks for reminding me of this song. I am going to sleep thinking on it.
Add Comment