176

> Comments are there only for you, please delete them before pushing your code.

I want to kill everyone who suggests that, slaughter them like animals!

Comments
  • 3
    Then when someone asks why you did something a specific way "fuck, hmmmm, give me an hour to evaluate my decisions and logic"
  • 2
    TODO: fix this shit

    Why didn't they fix it... This code looks like crap...
  • 3
    Worst advice I've ever heard so far...
  • 6
    Good code explains itself
  • 6
    @crapperthepooh Good luck...

    float InvSqrt (float x){
    float xhalf = 0.5f*x;
    int i = *(int*)&x;
    i = 0x5f3759df - (i>>1);
    x = *(float*)&i;
    x = x*(1.5f - xhalf*x*x);
    return x;
    }
  • 3
    @crapperthepooh esoteric business knowledge doesn't... And there's a lot of that in real code...

    Sometimes optimization breaks things.

    Good code explains itself **when it is paired unit tests that cover the use cases**
  • 3
    @Kamaropoulos

    https://en.m.wikipedia.org/wiki/...

    I see... what happens if I put in a negative #?
  • 2
    @crapperthepooh
    The code about is the inverse square root implementation in Quake 3. It's definitely a great piece of code but there is a whole paper explaining how it works.
  • 5
    Wow that escalated quickly haha, ofcourse I document classes or complex functions when there intent is not obvious, but I always aim for self explainatory code
  • 3
    @billgates and yea, we TDD 90% of the time so if someone breaks something the merge request cant be accepted
  • 3
    @billgates The end of the world... 😜
  • 1
    No no. Don't kill them. Break their fingers.
  • 1
    I prefer no comments. I like markdown docs or commit comments. If a comment is needed most likely the code requires some touch us.
  • 1
    @codefriar No mercy. Have to kill them.
Add Comment