MY Programming Principles
1. DO NOT WRITE CODE WHEN FEELING TIRED, BORED, or URGED!
Should this very first principle be damned, the rest below are
subject to be damned as well.
2. Avoid calling functions inside a function which has a specific task unless the sub-functions are related to accomplishing the main task. Otherwise, it's hard to expect what the function does and it defeats reusability.
bad1) setXP(){ set the xp and check condition to call levelUP() }
bad2) changeGender(){setCostume(),setAge(),setWhatever() ...}
ok) drawPyramid(){ drawTriangle(), drawSquare() }
For more details on the higher concept of this principle, check;
http://java.dzone.com/articles/java-modularity-2-why
And remember how I made robots and played with LEGO.
3. Always put javadoc for most of functions; The best is to make a descriptive name for the function.
4. Whenever naming something, words that happen to be repeating should come first. For instance:
(x) AcceptPopup, WarningPopup, flashingText, floatingText
(o) PopupAccept, PopupWarning, textFlashing, textFloating
5. Try to make member variables private and set getter and setter functions. It's easier to track down who sets what and when, how or why when debugging.
6. Make one simple project which can be used as a playground, a sketchbook, a science lab, or an assembly line for testing a new feature, function, algorithm, graphics, component, performance, etc before actually putting into the main project.
7. KISS (Keep It Simple and Stupid); Don't try to make something which does everything.
8. Generic approach to a solution: meaning NO HARD CODING!!
titsay
snowghoul
discoholicmusic
yousharknotpass
amandla
romaincrisis