The hottest Naming Conventions Substack posts right now

And their main takeaways

Category

Top Culture Topics

What's in a name?

The Global Jigsaw • 138 implied HN points • 30 Oct 23

🎭️ Culture Naming Conventions Cultural Traditions

Names can be challenging in different cultures - sometimes altering a name can make things simpler.
Naming conventions vary widely around the world, from westernized sequences to lengthy ancestral titles.
Some countries face issues with name diversity due to popular surnames and naming fashions.

Clean Code: The Art of Clean Naming

Brain Bytes • 2 HN points • 06 Mar 24

🕹 Technology Coding Naming Conventions

The importance of clean and clear naming in coding cannot be overstated. Good naming makes code understandable for anyone reading it.
Contextual information in variable names is crucial for code clarity and to avoid potential bugs or misuse of variables in larger codebases.
Avoiding magic numbers, abbreviations, and acronyms in code improves readability and maintainability for all developers working on the codebase.

Naming Things

The 418 • 1 HN point • 06 May 24

🕹 Technology Coding Software Development Naming Conventions Programming Engineering

Good names are crucial in programming as they become the building blocks of our shared tools, maintaining order and helping us recall resources.
Well-named things should be SEO-friendly, follow conventions, be concise but meaningful, consider collisions, guessable, and even bring a smile.
Injecting humor or cleverness into naming can add personality and help with team bonding, as well as make code memorable.

The Hard Things about Naming Things

The API Changelog • 3 implied HN points • 02 Feb 24

🕹 Technology API design Naming Conventions Developer Tools

Use familiarity when naming new operations to make it easy for developers to understand.
Use identity to disambiguate names and make the purpose of the operation clear.
Follow consistency in naming conventions across different operations in your organization to maintain clarity.

Software Component Names Should Be Whimsical And Cryptic

Outlandish Claims • 0 implied HN points • 09 Sep 22

🕹 Technology Software Development Naming Conventions Transparency

Names for software components should be whimsical and cryptic, rather than overly descriptive. Descriptive names can create a false sense of understanding and may need frequent updates.
Good software component names should be unique and serve as stable identifiers, making them opaque and memorable.
Avoid names that are too tied to the specific domain, company, or current function. Opt for names that are easy to remember, spell, and bring a smile.

Get a weekly roundup of the best Substack posts, by hacker news affinity:

Naming & Dependencies in Clean Architecture

🔮 Crafting Tech Teams • 0 implied HN points • 18 Aug 23

🕹 Technology Software Development Naming Conventions

Naming things in programming is crucial and can impact the success of refactoring.
Approaching naming and dependencies in Clean Architecture with a fresh and entertaining perspective can lead to new insights.
Continuing to learn and grow in your understanding of Clean Architecture through resources like Crafting Tech Teams can benefit your development skills.