• @[email protected]
    link
    fedilink
    55
    edit-2
    1 year ago

    My friends, please stop writing "something"s that do 1001 different things.

    With regards,
    Devs cleaning up old projects

    • @marcos
      link
      151 year ago

      Yeah, that won’t happen.

      And if you propose a separable set of functionality that you can mix as you like, you’ll get shut down on the base that it’s not viable (doesn’t matter if you had written it already), it’s too complex to understand (doesn’t matter that everybody keeps doing everything wrong because nobody can understand the current one) and YAGNI (doesn’t matter that keeping the current one running takes most of the time from everybody).

  • @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

  • SokathHisEyesOpen
    link
    fedilink
    English
    281 year ago

    It is with great pride that we present you with the Patriot Children initiative. It provides funding for schools to have fireworks shows on July 4th.

    *^(It also extends the Patriot Act for 900 years, makes it legal for corporations to own slaves, and revokes the 4th amendment.)

  • [email protected]
    link
    fedilink
    English
    281 year ago

    There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors

  • @[email protected]
    link
    fedilink
    141 year ago

    It really is.

    I’ve learned a lot about language by coming up with names and seeing other people’s.

    I think we are blessed with things like set/get. Such wonderful, simple, short concepts that compliment each other so well.

    And they rhyme.

    • @MajorHavoc
      link
      21 year ago

      Well played. I threw up in my mouth a little reading that.

  • @[email protected]
    link
    fedilink
    1
    edit-2
    1 year ago

    When writing a small, throwaway project, I stick with theIP, theDir, theVar, etc. More fun that way. This is with shell scripts, btw. I’m sure compiled code would be far more of a mess far quicker doing this.

    ETA: also someVar, someDir, etc