Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Naming: How to come up with meaningful names #58

Open
PierceAndy opened this issue Mar 30, 2017 · 0 comments
Open

Better Naming: How to come up with meaningful names #58

PierceAndy opened this issue Mar 30, 2017 · 0 comments

Comments

@PierceAndy
Copy link

PierceAndy commented Mar 30, 2017

Synopsis:

How better naming in your project can improve your codebase readability.

  1. Use intention-revealing names.
  2. Make meaningful distinctions.
  3. Avoid disinformation.

Slides: https://github.com/nus-oss/lightningtalks/files/924667/Better.Naming.pptx

Audience

  • CS students

Objective

  • Encourage audience to use better names in projects

Topic

  • Better naming

PUNCH

  • Worst variable names
  • There are only two hard things in Computer Science

WIIFY

  • Makes code more readable
  • Makes code easier to understand
  • Makes code maintenance easier

Promise

  • Simple rules for creating better names
  • How these rules make for better names

Know

  • What makes for a good name
  • How to come up with better names

Believe

  • It's worth doing
  • It's not hard to do

Do

  • Use better names in projects

Call-to-action

  • Know about these rules, and try applying them to your projects

Key points + content

  • Use intention-revealing names
    A good name tells you what it does, why it exists, and how it is used
  • Make meaningful distinctions
    Distinguish names in such a way that the reader knows what the differences offer
  • Avoid disinformation
    False clues obscure the meaning of code, and may lead to false conclusions
@PierceAndy PierceAndy changed the title Naming things Better Naming: How to come up with meaningful names Apr 1, 2017
@damithc damithc modified the milestone: 2017-C2 (week 13 Monday) Apr 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants