77,427 views
Turn down the lights
Turn up the lights
Change Player Size
Watch this video in a new window
How To Design A Good API and Why it Matters
Google Tech Talks
January 24, 2007
ABSTRACT
Every day around the world, software developers spend much of their time working with a variety of Application Programming Interfaces (APIs). Some are ...
More From: googletechtalks
51:58
51,051 views
30:40
10,506 views
1:10:16
49,970 views
1:01:04
47,046 views
56:31
28,129 views
54:09
16,750 views
49:25
58,256 views
55:27
38,013 views
1:03:47
46,969 views
59:28
9,057 views
57:22
18,173 views
54:57
26,158 views
1:11:16
28,670 views
54:05
22,698 views
53:16
3,431 views
51:16
213,670 views
105 ratings
Sign in to rate
27,405 views
© 2009 YouTube, LLC
Just the other day I was asking programming friends for help with naming. I wanted to check for a win on the diagonals of a tic-tac-toe board. And I wanted a name better than "IsTopLeftBottomRightDiagonalA Win." :D
Often when I ask for naming help I'm met with "Just use that name and move on." After hearing that enough I began questioning if I was wasting my time. It's good to hear that naming IS coding.
"IsTopLeftBottomRightDiagonalA Win" seems unnecessarily long imo. How about i.e. CheckDiagonals
About your problem, making a name for a function that checks for win on a tic-tac-toe board.
"IsTopLeftBottomRightDiagonalA Win."
Huh? I don't think so.
Why would you make a separate function checking each winning combination?
Wouldn't you just make one function that checks all combinations?
Anyway, the problem is in your design.
chris69666 made a good point.