67

Let's​ get things done :v

Comments
  • 2
    Nice. I like the double class options. a wizard-bulldozer is really awesome!
  • 1
    If your team wizard is powerful enough you might have to consider the option of totally rewriting a particular piece of code rather than finding where it went wrong :p @MagicMirror
  • 0
    @Letmecode lol ive worked with a couple of these so called "wizards" fuck them straight to hell
  • 1
    I'm not offended. My old team mates still can't figure out some of the code I wrote...
  • 1
    πŸ˜‚ my team called me gandalf yesterday. The grey wizardπŸ˜‡
  • 2
    I've been an Oprah-Bulldozer myself πŸ˜‚πŸ˜‚πŸ˜‚
  • 1
    @jpichardo same here 😊
  • 1
    Wizard code:

    This component is built using a factory which is actually a builder which we don't use providers for because we want to store our own state because we want this component to do EVERYTHING.

    NO JAVADOC REQUIRED MY CODE IS SELF DOCUMENTING.

    multiset contribution binders everywhere because fuck you the code which is run is only known at runtime.

    If you do not understand my code you should feel stupid
  • 1
    Bulldozer always. If the code is over a week old, it must have been written by an idiot (which sometimes was past me).
  • 1
    I'm none of these
  • 0
    Everyone in my team is a wizard, so I can't keep myself from bulldozing πŸ™ƒ
Add Comment