Naming Guidelines
Read OriginalThis article discusses the critical importance of naming in programming, framing it as a core design activity. It summarizes and extends guidelines from community experts, advocating for clear, precise, and terse names that reveal intent. It provides concrete examples of good and bad practices, such as using one word per concept, omitting redundant type information, and leveraging strong types over strings.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
Fix your upgrades and migrations with Codemods
Cassidy Williams
•
2 votes
2
Designing Design Systems
TkDodo Dominik Dorfmeister
•
2 votes
3
Introducing RSC Explorer
Dan Abramov
•
1 votes
4
The Pulse: Cloudflare’s latest outage proves dangers of global configuration changes (again)
The Pragmatic Engineer Gergely Orosz
•
1 votes
5
Fragments Dec 11
Martin Fowler
•
1 votes
6
Adding Type Hints to my Blog
Daniel Feldroy
•
1 votes
7
Refactoring English: Month 12
Michael Lynch
•
1 votes
8
Converting HTTP Header Values To UTF-8 In ColdFusion
Ben Nadel
•
1 votes
9
Pausing a CSS animation with getAnimations()
Cassidy Williams
•
1 votes
10
From Random Forests to RLVR: A Short History of ML/AI Hello Worlds
Sebastian Raschka
•
1 votes