Top all-time · #8463
Galo Navarro
Personal blog · srvaroa.github.iosystemsprogramming
Galo Navarro's personal blog at srvaroa.github.io covers systems and programming. Since 2016, 9 different Hacker News readers have linked it 10 times, most often “HotSpot JVM: why does the default hashCode() conflict with biased locking?”. It is still writing: the last post was on 2026-06-13, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link Galo Navarro's posts on Java internals, such as how Object#hashCode() is derived in OpenJDK and the biased-locking rabbit hole. One commenter recommends the hashCode post.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Galo Navarro. Principal Software Engineer. Infrastructure and orchestration for AI workloads. Software delivery pipelines and developer platforms
Most-linked posts?
- HotSpot JVM: why does the default hashCode() conflict with biased locking?6 people · 6 mentions · first linked 2017-02-01
- Talk write-up: How to build a PaaS for 1500 engineers2 people · 2 mentions · first linked 2020-01-09
What Hacker News says?
You might enjoy this blog post exploring the surprisingly deep (and interesting) rabbit-hole of Java's Object#hashCode() method. https://srvaroa.github.io/jvm/java/openjdk/biased-locking/20...
Comment linking /jvm/java/openjdk/biased-locking/2017/01/30/hashCode.html
on “Optimizing hash tables: hiding the hash code”Submitted Talk write-up: How to build a PaaS for 1500 engineers as a story · 203 points
HN discussion>If left unoverridden, it only yields a description of it’s class and location in memory It contains the hashCode(), not the memory location. The default implementation of hashCode could use a memory location to generate the hash, however that isn't the case in all implementations. OpenJDK seems to have used an RNG by default in the past and currently derives a value from the thread state[1] [1] https://srvaroa.gith…
Comment linking /jvm/java/openjdk/biased-locking/2017/01/30/hashCode.html
on “Never Use toString() for Behaviour”Submitted Blending complex systems made my latency 10x higher as a story · 200 points
HN discussionPersonally, I would recommend listening to Thoughtworks' Techonology Podcast. Their approach in general to running in the cloud is a pretty good one, which I'd characterize as platform engineering-centric. Anything Will Larsen writes is bound to be worth looking at and thinking about in the context of scaling cloud operations and operational complexity. His concept of the 'pierceable abstraction' is _absolutely key_…
Comment linking /paas/infrastructure/platform/kubernetes/cloud/2020/01/02/talk-how-to-build-a-paas-for-1500-engineers.html
on “De-siloing incident management: make reliability engineering everyone's job”Submitted HotSpot JVM: why does the default hashCode() conflict with biased locking? as a story · 3 points
HN discussionSubmitted How does the default hashCode() work? as a story · 2 points
HN discussionSubmitted How does the default hashCode() work? (2017) as a story · 2 points
HN discussionSubmitted How does the default hashCode() work? (2017) as a story · 1 points
HN discussionSubmitted Contention on sun.misc.Cleaner as a story · 1 points
HN discussion
