• Frist (unregistered)


  • chreng (unregistered)

    What! All closing parantheses on same line?! Unreadable.

  • George Gonzalez (unregistered)

    Yeah, Borland used that paradigm in the first draft of their OO library, where you could pass a second parameter to new(), another new(), and so on, and so on. That made things really hard to read and you had to write a recursive constructor if you were reading an arbitrary number of items from like a config file. Sketchy times!

  • Hannes (unregistered)

    Nice one. I have a similar method in one of the projects I have to maintain. It contains of 32 nested if-else branches and ends with 15 closing braces in a row. I have to admit, it looks pretty cool if you scroll by fast. Maybe that's what the original developer was aiming for?

  • Nope (unregistered)

    Maybe instead of the captcha we should include a literacy test? BlakeyBrat seems to be having a nervous breakdown.

  • Jeff Grigg (unregistered)

    I would definitely use reflection to do that.

    Loop from 44 down to 1, nesting the object creation, and then just create the SystemHandler instance in code.

  • Drts (unregistered)

    LOL an internet fighter here :-D

    I bet a scared little shit in the real life :-))))

  • Ulysses (unregistered)

    Don't knock Mireille's coworker. This is a perfectly suitable use of the Platformer Pattern. Just don't fall off the edge!

  • Colin D (unregistered)

    Wow This is impressively insane. Now tell me how you plan to wear my skin and I'll be secretly excited. You go fight the man BonkeyRatt

  • Zahndethus (unregistered)

    That is one of my favorite internet copy pastas. Kudos to you, oh internet troll!

  • (nodebb)

    Only 700 different ways? I have 700.1 ways I can kill someone. Slacker!

  • satan (unregistered)

    The builder pattern as described sucks. I've seen it before. The pitfalls include, not knowing what needs to be done for initialization. A constructor with X arguments tells you exactly how to create something. The more complex the thing that the builder makes, the more risk there is for error at initialization. The more method calls that are required, the more likely error is to be introduced for doing actions out of order and unit testing can become a PITA when there are 128 ways to initialize an object. 3 concrete constructors makes unit testing a snap.

    The real WTF is the pattern itself.

  • Bonkey (unregistered)

    Don't worry fellas. His pecker is half an inch shorter than average while erect and he can't get a second date.

  • Norman Diamond (unregistered)

    581 different ways.

  • TheC (unregistered)

    Wow!! I wonder why Link21 is so special...

  • Hannes (unregistered)

    " your IP is being traced right now"

    Did you write a GUI Interface in Visual Basic to track his IP address?

  • Someone (Not So) Else (unregistered) in reply to Nope

    Maybe we could try some text with SQL injection and similar stuff in it? If that succeeds when BlankeyeRash reads that, we could put a shutdown into its crontab.

  • null (unregistered)

    The real WTF is starting the numbering at '1'.

  • Robert Jones (google)

    "I am trained in gorilla warfare" We agree with you! you're ape-scheiss.

  • menem (unregistered)

    9/10 loled, nice grammar is a plus

  • fa (unregistered)

    The builder has its problems. It employs a somewhat convoluted logic in order to get a simple, easy to read interface. It does not naturally follow from OO design. Novice users often encounter it in libraries, and either have to struggle or accept the syntax on good faith.

  • Dieter H (unregistered) in reply to satan

    Mistake people make is that builder should always be used over constructor. It's not the case. In fact, neither should be used often (DI or SL). If one of them should be used, it depends upon how it needs to be used.

    Builder is what it says on the box, it's used for flexible configuration.

    A constructor is less flexible. That doesn't mean there's no use for it anymore. When it's a better fit, it's a better fit.

  • Freyaday (unregistered)

    Hey, thanks for introducing me to that pattern! Seems like it'll come in handy.

  • Ugh (unregistered)

    The builder pattern is useful when there are more than a couple optional parameters in a constructor. Other than that, it can be cumbersome. Order of call for the builder pattern shouldn't matter as the builder itself merely holds the data for passing into a private constructor (some implementations pass the entire builder into a constructor).

    "Gorilla warfare." Ha. I'd pay money to see a video of this clown fighting a simian. If he's lucky, he'll only get his face ripped off.

  • Speech Impediment (unregistered)

    Looks just like LISP to me.

  • Jasa Pembuatan Website (unregistered)

    Thanks a lot admin for your information and share to us. Jasa Pembuatan Website

Leave a comment on “Indentured”

Log In or post as a guest

Replying to comment #:

« Return to Article