Caching Code Diary Entries

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

• Always cache rate limited API call results
• Cache should be cleared before rebooting with new code
• Cache simple entities
• Create new tag or branches for each change you want deployed on git dep
• Delegation attributes can confuse your cache invalidation logic
• Do not do assignment or method calls within cache blocks
• Instance variable module memoization does not work
• Lazy evaluation cannot be cached
• Never switch on session variant data in publicly cached resources
• When invalidating caches ensure every element that might vary is part of the key