Part two of the refterm live stream is now available on YouTube - "Slow Code Isolation":https://youtu.be/lStYLF6Us_Q
-
-
Replying to @cmuratori
Thanks for introducing that idea of "cache the answers and never call the slow code". In hindsight, it's an obvious concept, but I hadn't ever thought about it.
1 reply 0 retweets 6 likes -
-
Replying to @cmuratori @failbottt
Unfortunately a lot of people are taught that caching is the most difficult problem in computer science! So they will never write an in-memory cache. They are happy to use a distributed cache-over-http tools like redis though (for reasons I don't understand).
1 reply 1 retweet 3 likes -
Replying to @hasen_judy @cmuratori
Yeah, and this was the motivator for my initial comment. My exposure to cache had been mostly, "it's hard so you shouldn't do it".
1 reply 0 retweets 0 likes -
Replying to @failbottt @hasen_judy
Wait - so this is two people responding to these tweets by saying they were taught caching is hard. Who is teaching that?? Where were you taught that? That is very unsettling if that is being taught to students! Caches are trivial!
2 replies 0 retweets 1 like -
Replying to @cmuratori @hasen_judy
From the web world: https://martinfowler.com/bliki/TwoHardThings.html … Specifically, this quote propagates widely. As a self-taught programmer I was confronted with this quote early and often: >There are only two hard things in Computer Science: >cache invalidation and naming things. -- Phil Karlton
3 replies 0 retweets 0 likes
But cache invalidation doesn't even exist as a problem if the lookups into the cache are unique. This is a horrible thing to be telling people.
-
-
Replying to @cmuratori @hasen_judy
That's why we're glad you're here! :)
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.