Friday, July 06, 2007
Six ways to write more comprehensible code
---------------------------------------------------------------------
Title: Six ways to write more comprehensible code
As a developer, time is your most valuable resource. These six tips on how to write maintainable code are guaranteed to save you time and frustration: one minute spent writing comments can save you an hour of anguish.
Learn more:
http://www.ibm.com/developerworks/linux/library/l-clear-code/
developerWorks
IBM's resource for developers.
http://www.ibm.com/developerworks/
Golden Rules for Living
If you open it, close it.
If you turn it on, turn it off.
If you unlock it, lock it up.
If you break it, admit it.
If you can't fix it, call in someone who can.
If you borrow it, return it.
If you value it, take care of it.
If you make a mess clean it up.
If you move it, put it back.
If it belongs to someone else and you want to use, get permission.
If you don't know how to operate it, leave it alone.
If it's none of your business, don't ask questions.
If it ain't broke, don't fix it.
If it will brighten someone's day, say it.
If it will tarnish someone's reputation, keep it to yourself."
7-6-2007_12512
1) think end game
2) multi layer and dimensional over end to end
3) adapt to pace
4) manage expectations and question authority
5) functional strength
6) gorilla sprints - lateral sprints
7) tombstone - doc holliday - how did it end? Kurt Russel acting at its finest
8) watching a movie with no sound just visuals
9) body language and reading lips
10) elisha cuthbert
11) tabasco - left v. right shoulder - devil/angel scenario
12) cross training styles - spike tv/ufc - "caveman training" - tire lifts, bear crawls, sledgehammering, plyometrics, rope crawls
13) presence precedes position
14) recovery speed can be more important than execution speed
15) shoot moves - ufc, mma styles
16) the kill point – wahlberg
17) Eat for performance
18) Finding every way/angle to work your body
19) Slo mo mojito hip sway ala barcardi
20) Casey from TopChef 3