Viewing profile — iliketoworkhard
iliketoworkhard
HN member- Joined
- Thu, Aug 29, 2019, 5:18 PM UTC
- HN karma
- 6
- Public activity
- 8 items
- HN profile
- View on Hacker News ↗
About iliketoworkhard
No profile information was provided.
Recent public activity
-
comment
Comment #21987444
Same with my old bose SoundSports
-
comment
Comment #21902519
I really need to pick up Solaris. I felt like Sapiens rewired my brain in a way. Homo Deus only drove in the message that we are nothing but algorithms
-
comment
Comment #21336936
And why weren’t all headers considered in the cache key to begin with? The key computation will never not be O(1). Only thing I can think of is too many cache entries with the same…
-
comment
Comment #21336879
What is CGI in this context? I’ve only heard of it in a movie special effects context.
-
comment
Comment #21139021
In general caching systems are volatile and not meant to be used to store data that cannot be afforded to be lost. Of course that doesn't stop clients from storing critical data on…
-
comment
Comment #20834935
Thank you! Sounds like a case where a consumer was updated but producer wasn't.. more room for error for the dev Interesting point about things getting caught on prod, no amount of…
-
comment
Comment #20831656
Splunk aggregation is a life saver. If you assign a unique id to each request, you can trace its path thru it's entire lifecycle, including asynchronous post-tasks. This can also h…
-
comment
Comment #20831578
Great points! Would you mind elaborating to a relatively inexperienced engineer how the following scenarios can end up happening? > queue sending to dead endpoints > circular queue…