Why does your kind have to create multiple files, classes, and variables to do one simple task? It makes no fucking sense. Your code was literally written to confuse anyone that has to work on it. Every fucking time I see this shit, my head explodes. It makes no sense. What the fuck is this? What other form of retardation do you have?

Then you have the essay writing galore of code and the never-ending typos that change every goddamn file as if it's not hard enough to trace where the random crap jumps into.

Complimentary? Complomentory? Complmntary? Carrier, carrie, carrer? Fuck you, you fucking piece of shit. Not only do you import entire files and each script runs random methods and variables you can't possibly trace, you- you fuck. I can't even grep the fuck out of this crap. Admit it, you did this for job securiy because you belong in a goddamn asylum, you sick demented fuckhole. The time you spent abstracting shit into oblivion could have been used fixing typos or writing consistent variables or consistent fucking I don't fucking know anymore. I hate this shit.

  • 1
    Sounds like "I've just graduated / just gone on a course / just watched a YouTube video about abstraction, and now I need to make sure everything has a million layers and is fully abstracted beyond the point it makes sense" syndrome.

    Catchy, I know.

    Worse is the "management has told me to write this in 50 layers, 48 of which make no sense" syndrome.

    The worst thing about it is these people generally feel enlightened, and come out with crap like "I used to think like you, I really did, but this way is so much better because it allows me to deal with these 10 hypothetical scenarios that are unlikely to happen much more easily."

    No excuse for typos though. There's a reason IDEs these days often have spellcheck for variable names. I fail code reviews over that sort of thing - seems picky, but it's trivial to correct at the time and can easily cause a whole bunch of confusion in future.
  • 2
    @AlmondSauce The common brag is to make things extensible and yet every time you add a small change, it breaks. He made some configurations that are either ignored or you have to copy/paste everywhere several times for it to work. I don't know what kind of bootcamp teaches people how to code like this.

    It was a lot of stress when I did code reviews because there are so many little things that people can't do right. It makes you think, "Do I really have to point this out?"
  • 1
    @rutee07 Oh, that's just "can't code" syndrome in that case. Unfortunately if it goes on for too long, it's terminal. No known cure...

    Yeah, sometimes I feel like that in reviews too. In my case it's usually more embarrassing for the author than me, so it tends to get stamped out after a while.
  • 1
    For each action you need one class for the controller, one class for the service action, one class for the input DTO, one class for the persisted model, one class for the model mapper, one class for the model validator, one repository class for persistence, one class for the result and one class to hold an error object.

    Oh, I almost forgot, you need interfaces for everything.
  • 1
    @ReverendLovejoy Fuck it. I'm getting a gun.
  • 2
    @rutee07 What you need is an IWeapon<T, TT> interface supported by an abstract Handgun<IBullet, T> class implemented by the Revolver class.

    Remember to declare IBullet as an extension of the IBallistics interface.
  • 0
    @ReverendLovejoy Interface is a parent of implementation. Why do you prefix it like it’s DotNet days?
    Do you use Hungarian notation too?
  • 0
    @Ninetou because it *is* .NET days
Add Comment