We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Don't Settle for Poor Names (or for Poor Design)

Formal Metadata

Title
Don't Settle for Poor Names (or for Poor Design)
Title of Series
Number of Parts
88
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language
Producer
Production Year2018
Production PlacePittsburgh

Content Metadata

Subject Area
Genre
Abstract
Have you ever been frustrated with code that is sprinkled with poorly named classes, methods, and variables? One of the most valuable things you can do as a developer is to choose good names and to sensitize your teammates to the benefits of improving names. It turns out that improving names is deeply connected to improving design. And vice-versa. You will see and experience this deep connection as we explore a real world example. By the end of this talk, you will have learned a process to get you started with improving names and improving design—a process simple enough for you to teach others.