On naming, Carl has the best suggestions, as I see it:
5.2 Word Names 5.2.1 Use the Shortest Word that Communicates the Meaning 5.2.2 Use Whole Words Where Possible 5.2.3 Hyphenate Multiple Word Names 5.2.4 Begin Function Names with a Verb 5.2.5 Begin Data Words with Nouns 5.2.6 Use Standard Names
CelesteM
That looks like an excellent list right there.
Geomol
I don't do much OO programming, because it is so hard to find useful objects. :)
If I was to create a game, I would make a character object (the character, you play), objects for objects in your surroundings, etc. That is easy, because it relaty to the real world.
If I should write code, which would sort filenames in a directory, I would write a function, not use OO.
CelesteM
But in reality, each file is a separate object...
Geomol
I can only recommend reading Bertrand Meyer, if you wanna do OO (and even if you don't do OO). And I don't program in Eiffel, which is used in his book. He just have many real good ideas.
*has*
"But in reality, each file is a separate object..."
Yes, it just confuses, when what you need really is a function to just do the job.
CelesteM
That sounds like the kind of book that I'm looking for. Thanks!
I know. LOL It was sarcasm.
Gregg
Meyer is very good. Reusable Software talks about library design, which is the most general kind of development.
Geomol
You are welcome. :) OO was thought to be the breaktrough in programming and to be used for all programming. It wasn't and it isn't.
Gregg
Code Complete, while dated, was a seminal text on the subject. Anything by McConnell is good.
Geomol
back in the 80ies.
(80ies was for my comment about OO, not your comment, Gregg.)
CelesteM
Reusable software sounds like a good place to start for what I'm looking for.
Gregg
201 Principles of Software Development (Davis) is also wonderful IMO. It may seem like a silly little book, but I think it has more tabs in it than any other book I own.
Also, not on coding specifically, but anything by Robert Glass is worth reading. He writes about software failure.
Finally, the Pragmatic Programmer (Thomas and Hunt) is great.
CelesteM
Excellent.
Sunanda
For some very historical roots (yet still completely relevant issues), take a look for David Parnas and Information Hiding -- it's perennial guidelines (from the 1970s!) for healthy ways to structure large systems.