Making Bad Code Good

Given by Dan Wilson - DataCurl

Very broad overview of reasons we write bad code. Generally , every reason we are rushing day in and out to push our code for the build. Kind of seemed like a principle yelling at us for running in the halls.

Some very broad ideas:
- Change Boolean evaluations into functions
- Try never to nest conditionals even thou they may be easier to develop at first, someone else doesnt need to go through the same process you did just to make a small change
- Its not always about writing less lines of code, sometimes its better to write larger functions then smaller ifelse so others can read the true function of the conditional or loop easier
- Put evaluations at the top in silents and configurations so someone can easily modify setups.

Broad elementary discussions on the advantages of commenting

Since we are using SVN, why would we comment out large blocks of code, use small comments with revsions stated to make files easily readable by others

Save money on kb being sent:
- Use upper level styles and less lower level duplication of styles
- Put those styles stored externally and loaded into the browser only once on the site
Example: use the over with classes for header areas

Stop Code:
put conditionals that stop the rest of the page from processing at the top to save kbs and time for others reading

Elementary overview of why descriptive naming is import and why common naming is bad

Strong final emphasis on using var scoping to prevent var leaking.