yakey2008 · May 4, 2014 05:23 · May 4, 2014 · May 3, 2014 · May 3, 2014 · May 3, 2014
diff --git a/languages.md b/languages.md
@@ -1,8 +1,9 @@
 # Languages to Learn
-- [x] CoffeeScript
-- [x] Jade
-- [x] less
+- [x] Golang
+- [x] Dart
 - [x] Core Python
 - [x] JavaScript
 - [ ] C 
 - [ ] Lisp
+
+## Note: This is my personal languages checklist, Feel free to replace it with your languages of choice.
diff --git a/languages.md b/languages.md
@@ -3,6 +3,6 @@
 - [x] Jade
 - [x] less
 - [x] Core Python
-- [ ] JavaScript
+- [x] JavaScript
 - [ ] C 
 - [ ] Lisp
diff --git a/languages.md b/languages.md
@@ -2,7 +2,7 @@
 - [x] CoffeeScript
 - [x] Jade
 - [x] less
-- [ ] Core Python
+- [x] Core Python
 - [ ] JavaScript
 - [ ] C 
 - [ ] Lisp
diff --git a/languages.md b/languages.md
@@ -1,3 +1,4 @@
+# Languages to Learn
 - [x] CoffeeScript
 - [x] Jade
 - [x] less

diff --git a/architecture.md b/architecture.md
@@ -1,8 +1,8 @@
 # Architectural Questions
 
-Are responsibilities well defined?
-Are the collaborations well defined?
-Is coupling minimized?
-Can you identify potential duplication?
-Are interface definitions and constraints acceptable?
-Can modules access needed data—when needed?
+- [ ] Are responsibilities well defined?
+- [ ] Are the collaborations well defined?
+- [ ] Is coupling minimized?
+- [ ] Can you identify potential duplication?
+- [ ] Are interface definitions and constraints acceptable?
+- [ ] Can modules access needed data—when needed?
diff --git a/delibrateprogramming.md b/delibrateprogramming.md
@@ -1,4 +1,3 @@
-
 # How to Program Deliberately 
 
 - [ ] Stay aware of what you're doing.

diff --git a/architecture.md b/architecture.md
@@ -0,0 +1,8 @@
+# Architectural Questions
+
+Are responsibilities well defined?
+Are the collaborations well defined?
+Is coupling minimized?
+Can you identify potential duplication?
+Are interface definitions and constraints acceptable?
+Can modules access needed data—when needed?
diff --git a/debugging.md b/debugging.md
@@ -0,0 +1,7 @@
+# The debugging checklists
+
+- [ ] Is the problem being reported a direct result of the underlying bug, or merely a symptom?
+- [ ] Is the bug really in the compiler? Is it in the OS? Or is it in your code?
+- [ ] If you explained this problem in detail to a coworker, what would you say?
+- [ ] If the suspect code passes its unit tests, are the tests complete enough? What happens if you run the unit test with this data?
+- [ ] Do the conditions that caused this bug exist anywhere else in the system?
diff --git a/delibrateprogramming.md b/delibrateprogramming.md
@@ -0,0 +1,11 @@
+
+# How to Program Deliberately 
+
+- [ ] Stay aware of what you're doing.
+- [ ] Don't code blindfolded.
+- [ ] Proceed from a plan.
+- [ ] Rely only on reliable things.
+- [ ] Document your assumptions.
+- [ ] Test assumptions as well as code.
+- [ ] Prioritize your effort.
+- [ ] Don't be a slave to history.
diff --git a/guradianknot.md b/guradianknot.md
@@ -0,0 +1,9 @@
+# Cutting the Gordian Knot
+
+- [ ] When solving impossible problems, ask yourself:
+- [ ] Is there an easier way?
+- [ ] Am I solving the right problem?
+- [ ] Why is this a problem?
+- [ ] What makes it hard?
+- [ ] Do I have to do it this way?
+- [ ] Does it have to be done at all?
diff --git a/languages.md b/languages.md
@@ -0,0 +1,7 @@
+- [x] CoffeeScript
+- [x] Jade
+- [x] less
+- [ ] Core Python
+- [ ] JavaScript
+- [ ] C 
+- [ ] Lisp
diff --git a/law of demeter.md b/law of demeter.md
@@ -0,0 +1,7 @@
+# Law of Demeter for Functions
+
+- [ ] An object's method should call only methods belonging to:
+Itself
+- [ ] Any parameters passed in
+- [ ] Objects it creates
+- [ ] Component objects
diff --git a/orthogonal.md b/orthogonal.md
@@ -0,0 +1,6 @@
+# How to maintain orthogonality 
+
+- [ ] Design independent, well defined components
+- [ ] Keep your code decoupled
+- [ ] Avoid global data
+- [ ]  Refactor similar functions
diff --git a/prototype.md b/prototype.md
@@ -0,0 +1,8 @@
+# Things to prototype
+
+- [ ] Architecture
+- [ ] New functionality in an existing system
+- [ ] Structure or contents of external data
+- [ ] Third-party tools or components
+- [ ] Performance issues
+- [ ] User interface design
diff --git a/testing.md b/testing.md
@@ -0,0 +1,9 @@
+# Aspects of Testing 
+
+- [ ] Unit testing
+- [ ] Integration testing
+- [ ] Validation and verification
+- [ ] Resource exhaustion, errors, and recovery
+- [ ] Performance testing
+- [ ] Usability testing
+- [ ] Testing the tests themselves
diff --git a/whentorefactor.md b/whentorefactor.md
@@ -0,0 +1,7 @@
+# When to Refactor ?
+
+- [ ] You discover a violation of the DRY principle.
+- [ ] You find things that could be more orthogonal.
+- [ ] Your knowledge improves.
+- [ ] The requirements evolve.
+- [ ] You need to improve performance.
diff --git a/wisdom.md b/wisdom.md
@@ -0,0 +1,8 @@
+# The Wisdom Acrostic ( Customer specific)
+
+- [ ] Why do you want to learn them?
+- [ ] What is their interest in what you have got to say?
+- [ ] How sophisticated are they?
+- [ ] How much details do they want?
+- [ ] Whom do you want to own the information?
+- [ ] How can you motivate them to listen to you?
Original file line number	Diff line number	Diff line change
		@@ -1,4 +1,3 @@

		# How to Program Deliberately

		- [ ] Stay aware of what you're doing.