News for hackers. Stuff that matters.
Re:Debugging a Memory Leak on Heroku by schneems on Tuesday October 13, 2015 @11:18AM (#10381027)
It's all about your own internal GC. When you meet someone, you don't know if they're worth remembering or not. It takes a few encounters (or generations) before your mind realizes that this is necessary information. If you want to prevent an object from being GC'd in Ruby you can assign it to a constant. In real life you can hack your brain by making an association with an constant in your life. A good trick is to try to remember their face and the name of a celebrity. The extra few seconds you spend thinking about what celebrity has the same name is usually enough to trick my brain into remembering. Can't think of anyone famous? Ask them. At least you'll spend a bit of time talking about their name and it's a fun ice breaker.
Re:Debugging a Memory Leak on Heroku by paulmd on Tuesday October 13, 2015 @01:41PM (#10382072)
One trick from ancient times is the Method of loci:

https://en.wikipedia.org/wiki/Method_of_loci

(linked on HN yesterday)