• RustyNova@lemmy.world
    1·
    5 months ago

    I don’t know and that’s the problem :(

    I keep asking myself what to choose, only for changing it a day after cursing myself to choose a stupid name.

    Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place. But that’s also a detriment when you know what you want. You can start typing without the prefix but you’ll have to go through the better suggestions of intellisense first.

    Little endiant is the same thing, but in reverse. Great when needed, but bad for browsing.

    Although I do have some fix I’m starting to use. But it’s not applicable everywhere, and not in every language.

    What I do is use module as prefix. Instead of dialogue_file_open, I create a file_open in the dialogue module, allowing either directly calling file_open, or dialogue::file_open. Using intellisense on the module allow for easy browsing too!

    Although in OP’s post I’d rather have file_open_dialogue as it convey the more significant meaning, being to open a file, first. Then “dialogue” is just the flavour on top

    • sudo42@lemmy.worldEnglish
      1·
      5 months ago

      Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place.

      If only someone would train a program… we could call it a Large Language Model… to knowingly group the names together so we wouldn’t have to choose between human-readable format or dB format.

      Guess that will never happen because instead we’re stuck using “AI’s” to inflate stock prices instead. /s

      I remember seeing a proposed language that would allow each programmer to choose what name to use for each item. Don’t like ‘open_file’? Choose to see it as ‘file_open’ every time you review the file in the future.

      While we battle with each other endlessly, we keep forgetting that the computer doesn’t care.