Top all-time · #6533
Heap
Company blog · heap.engineeringprogrammingdata
Heap is the company blog at heap.engineering, writing about programming and data. Since 2017, 12 different Hacker News readers have linked it 16 times, most often “Decrypting PgBouncer’s Diagnostic Information”. No feed was found, so read it on the site itself.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
Engineering posts on infrastructure and performance, including the technical story of Asana's rewrite. One commenter says the post on the rewrite matched pain points their own team had hit.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Heap is the only digital insights platform that shows everything users do on your site, revealing the "unknown unknowns" that stay invisible with other tools.
Most-linked posts?
- Decrypting PgBouncer’s Diagnostic Information2 people · 2 mentions · first linked 2017-12-30
- Analyzing the Performance of Millions of SQL Queries2 people · 2 mentions · first linked 2017-11-27
- Migrating to React and MobX Without Stopping Feature Development2 people · 2 mentions · first linked 2017-08-17
What Hacker News says?
Terraform ( https://www.terraform.io ), which we use, is a neat way to abstract this configuration data. We keep the configuration files in git, and can do GitHub pull requests over our whole infrastructure and apply the configuration with confidence (to change the existing setup or re-create it from scratch). This works for multiple cloud providers and is great for security purposes (all changes are auditable, no c…
Comment linking /terraform-gotchas/
on “Is Amazon's cloud service too big to fail?”Submitted Running 10M PostgreSQL Indexes in Production as a story · 263 points
HN discussionI would love a resource like that! We went through a very similar process on my team [0], and I was pleased to see this post validating some pain points we had seen. > In hindsight, we chose the correct trade off. This is key, and I think it's almost something you have to blindly follow when going into the transition. It's a lot easier to justify the decision to incrementally rewrite in retrospect than it is to get…
Comment linking /migrating-react-mobx-while-shipping-new-features/
on “Treating performance as a product: The technical story of Asana’s rewrite”Submitted Terraform Gotchas and How We Work Around Them as a story · 158 points
HN discussionSubmitted Making Our APIs Solid, by Breaking Them in Production as a story · 5 points
HN discussionSubmitted How Basic Performance Analysis Saved Us Millions as a story · 5 points
HN discussionSubmitted Migrating to React and MobX Without Stopping Feature Development as a story · 3 points
HN discussionSubmitted How to Structure Permissions in a SaaS App as a story · 2 points
HN discussionSubmitted Decrypting PgBouncer’s Diagnostic Information as a story · 2 points
HN discussionSubmitted Analyzing the Performance of Millions of SQL Queries as a story · 2 points
HN discussionSubmitted How We Are Migrating to React and MobX Without a Rewrite as a story · 2 points
HN discussionSubmitted How Basic Performance Analysis Saved Us Millions as a story · 2 points
HN discussionSubmitted How We Write Front-end Code At Heap as a story · 1 points
HN discussionSubmitted Decrypting PgBouncer's diagnostic information as a story · 1 points
HN discussionSubmitted Analyzing Millions of SQL Queries When Each One Is a Special Snowflake as a story · 1 points
HN discussionSubmitted Redshift Pitfalls and How to Avoid Them as a story · 1 points
HN discussion
