Home / Companies / PostHog / Blog / Post Details
Content Deep Dive

10,000 PRs a month is easy: How devex is evolving at PostHog

Blog post from PostHog

Post Details
Company
Date Published
Author
Paul D'Ambra
Word Count
1,959
Company Posts That Month
15
Language
-
Hacker News Points
-
Post removed?
No
Summary

PostHog has significantly increased its shipping cadence, growing from 1,441 pull requests (PRs) in January to 4,725 in June, with only a 10% rise in engineering staff. This acceleration is chiefly attributed to the increased use of AI, enabling faster and more efficient development processes, such as agent-driven PRs and self-driving loops, which have risen from 20% to 70% of monorepo PRs. While the increased volume of PRs doesn't inherently equate to speedier handling, PostHog is leveraging agentic loops and custom tools to prepare PRs for human review, and has transitioned towards cloud-based development to overcome local machine limitations. Continuous Integration (CI) remains a bottleneck, with efforts focused on optimizing the CI process and reducing unnecessary test runs through advanced techniques like building abstract syntax trees. PostHog's approach prioritizes reliability over perfection, maintaining high service uptimes and using automated testing to ensure system stability. The introduction of agents like StampHog and ReviewHog for code reviews has reduced the human workload, allowing engineers to concentrate on more impactful reviews. PostHog aims to further enhance efficiency by developing agents capable of autonomously testing code, thereby reducing human involvement in routine tasks and enabling quicker adaptation to the accelerated pace of development.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Developer Experience 1 547 257 91 +27%
LLM 1 7,115 1,261 236 +13%
Loop engineering 1 141 56 36 +29%
Real-time 1 5,674 1,350 233 -6%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.