For example, using descriptive variable names or name-spaces: some languages put limits on your ability to do this, often by draconian identifer length limits.

Another example is limiting side-effect. What is even meant by side-effect can be very different from one language to another, and the notion of where the grey line between good side-effect and bad side-effect is even more tightly coupled to the language in use.

Anyway, that's just nit-picking, sorry, but the point I guess I meant to make is that "good practices" are something that has to be a little more specific than being "smart, safe, efficient and innovative." That's basically being "good, safe, good, and good" at programming (I give credit to "safe" because it's at least one thing on that list that isn't self-evident... but it is nearly so). I guess my point is that "good, safe, efficient, and innovative" are more like a philosophy or a mantra, than a good practice, and good practices do tend to be at least somewhat language specific.

------------
:Wq
Not an editor command: Wq
[download]