Reka Horvath
The Name of the Rose
#1about 3 minutes
Why good naming is critical for understanding code
Good names act as an introduction to a domain's core concepts, making code more approachable for newcomers.
#2about 2 minutes
How mental models influence code interpretation
We process code using the same mental shortcuts as natural language, creating meaningful chunks and making assumptions based on names.
#3about 3 minutes
The danger of misleading function names
A function's name must not misrepresent its behavior, such as hiding side effects or returning unexpected types.
#4about 2 minutes
Using specific names instead of general terms
Overly general names like 'process' or 'handle' obscure a function's true purpose and should be replaced with more descriptive alternatives.
#5about 4 minutes
Establishing a one-to-one mapping for concepts
Maintain clarity by assigning exactly one name to each concept, avoiding both synonyms and using one name for multiple different ideas.
#6about 3 minutes
A cautionary tale of catastrophic naming failure
The Knight Capital case illustrates how a seemingly small naming ambiguity, when combined with other system faults, can lead to massive financial loss.
#7about 5 minutes
Designing consistent and intuitive APIs
APIs that are consistent with domain nomenclature or established frameworks are easier for developers to learn and use correctly.
#8about 2 minutes
Keeping names updated as code and business evolve
Names must be re-evaluated and updated when underlying technology or business domain concepts change to prevent them from becoming misleading.
#9about 4 minutes
Summary of key principles for effective naming
The core principles of good naming are to avoid being misleading, consider the reader's perspective, respect context, and maintain names over time.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
20:42 MIN
Applying principles for practical software design
Modern software architectures
08:44 MIN
Writing readable code through clear naming and structure
Keep your code refactorable
06:51 MIN
Moving beyond the dogma of clean code
Intentional Code - Minimalism in a World of Dogmatic Design
30:38 MIN
Key takeaways and further API design topics
API Design - Getting Started
36:42 MIN
Applying clean code principles for naming and errors
All you need is types
04:47 MIN
Differentiating good and bad reasons for refactoring
Product Managers' Eternal Battle with Refactoring
00:28 MIN
Why developers make basic cybersecurity mistakes
Don't Be A Naive Developer: How To Avoid Basic Cybersecurity Mistakes
00:14 MIN
Introduction to Domain-Driven Design and sustainability
It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design
Featured Partners
Related Videos
43:13It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design
Carola Lilienthal
39:49Antipatterns - nemesis of software development
Mustafa Toroman
25:03Intentional Code - Minimalism in a World of Dogmatic Design
David Whitney
26:59Identifying code smells
Benjamin Bischoff
23:44The QUEST for Better Software
Richard Bown
24:52We (don't) need a software architect!?!
Hendrik Lösch
21:39Unveiling the Dark Side: Navigating the Pitfalls of Digital Ambitions
Johannes Hansen
24:38Resolving technical debts in software architecture
Carola Lilienthal
Related Articles
View all articles
From learning to earning
Jobs that call for the skills explored in this talk.
Architect / Staff Python Engineer (m/f/d)
CONTIAMO GMBH
Berlin, Germany
Senior
Python
Docker
TypeScript
PostgreSQL
Software Engineering Coach: Flexible (Domain-Driven Design, React Native More)
Skiller Whale
London, United Kingdom
Remote
€208K
Kotlin
Docker
PostgreSQL
+1
Technical Product Owner
CodeMinded