• @MrPoopyButthole
    link
    English
    331 year ago

    You see, that’s why you divide all the smaller distinct batches of logic into their own functions and then give the wrapper function a name like blahBlahOrchestrator or blahBlahManager waves hands mysteriously

    • @MajorHavoc
      link
      18
      edit-2
      1 year ago

      I prefer to have a blahBlahManagerFactory, with an incredibly brittle undocumented XML configuration file. /s

      I find that it makes everyone’s work day simpler, because they simply cannot do their jobs. /s

      • @[email protected]
        link
        fedilink
        English
        91 year ago

        If you don’t have your config in .txt files with incredibly confusing implicit syntax, you’re doing it wrong.

      • AggressivelyPassive
        link
        fedilink
        51 year ago

        That’s a bit too constraining for my taste. What if I want to orchestrate something like blahBlah, but in a flexible way? Something like an AbstractBlahBlahableFactoryBuilder?

        • @MajorHavoc
          link
          21 year ago

          Lordy. That’s even worse than I was willing to take it. You win. Shudder Lol.

        • @MooseBoys
          link
          51 year ago

          I think you meant IAbstractBlahBlahManagerFactoryControlBeansHandlerFactoryFactory6ProxyHandlerAsync_Compat3, and of course its test counterpart, IAbstractBlahBlahManagerFactoryControlBeansHandlerFactoryFactory6ProxyHandlerAsync_Compat3::FakeMockVirtualDeviceTestManagerBeansFactory2_HACK_DO_NOT_USE

    • @[email protected]
      link
      fedilink
      61 year ago

      I wrote a bunch of if statements to work out how to handle various types of errors, and called it ErrorClassifier. Can I add “AI engineer” to my resume now?

      • Rob
        link
        English
        31 year ago

        Only if you name it ErrorClassifierGPT