1.Practicing general maintenance.
a.Use abbreviations.
b.reserved words cause errors.
c.Must start variables with a lowercase letter.
d.Variables should be lowercase or mixed-case letters.
e.none
f.Establish a naming standard for relating similar functions.
g.Do not pluralize the words you use in the class name.
h.Put a the prefix for a clear and self-explanatory package name in all lowercase letters.
i.Starting interface names with an uppercase "I" helps you distinguish an interface from a class.
j.Components that do not use concatenated words begin with an uppercase letter.
2.Use comments in your code.
a.Add comments after you format your code.
b.Use documentation comments to describe interfaces, classes, methods, and constructors.
3.Check your code organized
a.Put your code all in one location.
b.Easier to attach code to an objects.
c.Know difference between the global and root scopes.
1.Scope indicates when, where and how long.
2.To target items use this before it.
3.Use keywords
d.create class files.
e.reuse code whenever possible.
4.No case sensitivity is involved
5.Maintain your code
a.Add white space to your code.
b.Use braces ({}) for if statements.
c.When you write a condition, don't add the redundant ==true in your code
d.include a space following each expression in a for statement
e.none
f.Don't use parentheses with any return statements
g.Your statement should include a comment
h.none
i.none
L'espace. De l'Antiquit nos jours
6 years ago