Names should always indicate role.

Problems

• Declarative

• Design for Change

• Coupling to accidental implementation

Solutions

1. Rename your variable according to the role.

Sample Code

Wrong

Right

Detection

This is a semantic rule. We can instruct our linters to warn us from using names related to existing classes, types o reserved words since they are too implementative.

Tags

• Declarative

Conclusion

The first name we can across is related to an accidental point of view. It takes time to build a theory on the models we are building using our MAPPERS. Once we get there, we must rename our variables-

Relations

Code Smell 38 - Abstract Names

Maxi Contieri ・ Nov 30 '20

#oop #codenewbie #naming #webdev

More info

What exactly is a name? — Part I: The Quest

Maxi Contieri ・ Feb 9 '21

#codenewbie #tutorial #webdev #oop

XUnitPatterns

Credits

Photo by Sangga Rima Roman Selia on Unsplash

This idea came from this tweet

Types are essentially assertions about a program. And I think it’s valuable to have things be as absolutely simple as possible, including not even saying what the types are.

Dan Ingalls