.com
Hosted by:
Unit testing expertise at your fingertips!
Home | Discuss | Lists

Intent Revealing Name

The book has now been published and the content of this chapter has likely changed substanstially.



How do you make code easily understood?

Paraphrased from "Intent Revealing Method Selector" in Kent Beck's "Smalltalk Best Practice Patterns":

Name your methods (and variables) based on the intent of the user (caller for methods). Describe the goal they would seek to fulfil, not the mechanism or algorithm used to fullfil it.

Further Reading

This is described in Kent Beck's "Smalltalk Best Practice Patterns" [SBPP] as a best practice in the smalltalk community.

Page generated at Wed Feb 09 16:39:06 +1100 2011

Copyright © 2003-2008 Gerard Meszaros all rights reserved

All Categories
Introductory Narratives
Web Site Instructions
Code Refactorings
Database Patterns
DfT Patterns
External Patterns
Fixture Setup Patterns
Fixture Teardown Patterns
Front Matter
Glossary
Misc
References
Result Verification Patterns
Sidebars
Terminology
Test Double Patterns
Test Organization
Test Refactorings
Test Smells
Test Strategy
Tools
Value Patterns
XUnit Basics
xUnit Members
All "External Patterns"
Abstract Factory
Adapter
Command
Comparator
Complete Constructor Method
Composite
Data Access Object
Data Transfer Object
Decorator
Domain Model
Facade
Factory Method
Foreign Method
Guard Clause
Hexagonal Architecture
Integration Build
Intent Revealing Name
Interpreter
Layered Architecture
Lazy Initialization
Marker Interface
Noun Phrase Name
Null Object
Observer
Pluggable Behavior
Private Workspace
Prototype
Registry
Remote Facade
Remote Proxy
Repository
Self-Call
Service Facade
Service Layer
Session Facade
Singleton
Skippable Sections
Smoke Test
State
Strategy
Template Method
Thread-Specific Storage
Transaction Script
Ubiquitous Language
Virtual Clock