Ruby Code Diary Entries

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job.

• Always double check symbol vs string keys in hash objects
• Destructuring arrays in enumerable requires array of arrays
• Double splat cannot handle nil
• Exceptions should be qualified with their modules just like classes
• How reloading code works
• How to use yard to see where dependency integrations will break
• Look for the ensure keyboard in backtraces
• Never copy raw ruby console output when intending to use the data again
• Never forget hashes or hash like objects such as session can have nil and therefore will break method chains
• Searching for a method name is insufficient to know whether it is safe to delete it
• Tempfile gives random extensions by default
• Understand the difference between implicit and explicit blocks
• Understand what is available in ruby blocks
• Warning at exit handlers are inherited from parent processes