home.social

#namingconventions — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #namingconventions, aggregated by home.social.

  1. How Do You Choose Python Function Names? – Real Python

    Rules and conventions for naming Python functions emphasizing:
    ➡️the importance of using descriptive, snake-case names.
    ➡️the use of underscores for internal methods
    ➡️differences in naming conventions for variables and classes.

    The article is based on Python Enhancement Proposals PEP8

    realpython.com/python-function

  2. "Why did you call your file 'text.pdf.pdf'."

    "What do you mean?"

    "Why do you have the extension twice?"

    "Oh, that? Safety."

    "What?"

    "It's like when you tie your shoes. You put a safety knot to prevent it from untying, right?"

    "Yes."

    "It's the same with the double extension. I want to make sure that the computer really knows it is a PDF."

    "Your explanation is stupid-stupid."

    "Why do you say stupid twice?"

    "Safety. I really want you to know that it is stupid."

    #FileExtensions #NamingConventions #PDF #safety #stupid #nonsense

  3. So, umm, I want to name this project: Tiny Island Dark Dungeon Intergalactic Explorer Saga

    a.k.a.: T.I.D.D.I.E.S

    The goal is to keep it family friendly.

    But the acronym is... alluring.

    #GameDev #NamingConventions #AMIRITE #GodotEngine

    (Yes, I'm using both Kenney's and Quaternius models LOL)

  4. 🧵 1/3: What’s the difference between a carousel, a swiper and a slider?

    The terms are used interchangeably, but I would argue, there’s a semantic difference.

    #Carousels are circular. They start over once you reach the last item.

    #Swipers are linear. You can swipe back and forth, but once you reach the last item, you can’t swipe any further.

    #Sliders are input elements (e.g. volume controls), and thus entirely diffenret #UI #components

    #ux #uidesign #namingconventions

  5. @Inspiredharvey it's a helpful naming convention, and they tend to be used infrequently enough that they don't visually dominate, in my experience. It helps differentiate between an Enum and a normal attribute at a glance.

    Same goes for the convention of globals having `CAPS` and "private" vars starting with `__` (though name mangling there actively does something, I learnt recently).

  6. So... #NamingConventions in #vfx...

    By default, none of the DCCs seem to force anything on you and instead let you save & render stuff everywhere you like.

    #Nuke at least has easy version-up for your script - but doesn't adapt your output file names.

    #Houdini has $JOB and $HIPNAME as useful shortcuts to your work directory but hardly any versioning.

    How are you dealing with versions, render output locations and the spectre of overwriting stuff in your #pipeline?