+* Emacs
+** =add-hook= vs =eval-after-load=
+Ref [[http://stackoverflow.com/questions/2736087/eval-after-load-vs-mode-hook][eval-after-load-vs-mode-hook]]
+#+BEGIN_QUOTE
+Code wrapped in =eval-after-load= will be executed only once, so it is typically used to perform
+one-time setup such as setting default global values and behaviour. An example might be setting
+up a default keymap for a particular mode. In =eval-after-load= code, there's no notion of the
+"current buffer".
+
+Mode hooks exectue once for every buffer in which the mode is enabled, so they're used for per-buffer
+configuration. Mode hooks are therefore run later than =eval-after-load= code; this lets them take
+actions baed upon such information as whether other modes are enabled in the current buffer.
+#+END_QUOTE
+
+* ObjectiveC
+** =#import= vs. =#include=
+[[http://stackoverflow.com/questions/439662/what-is-the-difference-between-import-and-include-in-objective-c][what-is-the-difference-between-import-and-include-in-objective-c]]
+- =#import= directive as added to Objective-C as an improvied version of =#include=
+- =#import= ensures that a file is only ever included onces so that you never have a problem with recursive includes
+- Bacically, use =#import= for Objective-C thins, =#include= for C stufff.
+
+
+* Books
+** Intruduction to Algorithms