How we participate in 99 IRL events in a year - #19794
Open
Zaltsman wants to merge 1 commit into
Open
Conversation
Daniel's post on how the builder relations team gets product engineers out to 100+ IRL events a year without twisting arms. Generated-By: PostHog Desktop Task-Id: 7600c2ae-22ba-450c-8b32-da9c44c929a6
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 0 errors, 11 warnings, 3 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 11:99 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 11:132 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 23:262 | warning | 'yappers' is a possible misspelling. | PostHogBase.Spelling |
| 31:4 | warning | 'Product engineers FTW' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 43:22 | warning | 'Meikel' is a possible misspelling. | PostHogBase.Spelling |
| 45:24 | warning | 'Meikel' is a possible misspelling. | PostHogBase.Spelling |
| 52:83 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 55:29 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 73:132 | warning | 'Kliment' is a possible misspelling. | PostHogBase.Spelling |
| 77:179 | suggestion | Prefer 'proper nouns or they' over 'she'. | PostHogBase.Inclusivity |
| 77:263 | suggestion | Prefer 'proper nouns or they' over 'she'. | PostHogBase.Inclusivity |
| 85:19 | warning | 'yappers' is a possible misspelling. | PostHogBase.Spelling |
| 85:41 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 89:73 | suggestion | Prefer 'proper nouns or they' over 'he'. | PostHogBase.Inclusivity |
Contributor
Bundle reportTotal JS (gzip)8.15 MiB (no change) Eager graph (modules shipped in each entrypoint's initial chunks)
Largest modules in the
|
| Module | Size |
|---|---|
./src/data/mcp-tools.json |
1053.0 KiB |
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css |
754.4 KiB |
./src/components/Stickers/Stickers.tsx |
696.4 KiB |
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js |
481.4 KiB |
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules |
395.1 KiB |
./src/hooks/useCustomers.tsx + 55 modules |
370.0 KiB |
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js |
354.8 KiB |
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules |
351.4 KiB |
./src/components/ProductComparisonTable/index.tsx + 126 modules |
301.7 KiB |
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js |
281.9 KiB |
./src/components/SearchUI/index.tsx + 87 modules |
273.0 KiB |
./node_modules/.pnpm/@posthog+brand@0.8.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/magnifying-glass.mjs |
254.7 KiB |
./node_modules/.pnpm/framer-motion@10.18.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/dom/motion.mjs + 109 modules |
253.9 KiB |
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules |
247.4 KiB |
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules |
240.1 KiB |
Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).
jina-yoon
reviewed
Sep 1, 2026
|
|
||
| Every developer marketing team I've ever talked to struggles to get the people actually building their products to go out IRL (in real life) and demo them. Even though it's a clear way to help drive retention and expansion, it's only a small subset of internal yappers who prioritize this. | ||
|
|
||
| Since joining PostHog in summer 2025 we've gone from doing one IRL event to over 100 in a fiscal year and roughly 95% of those events involved an engineer (or other team member) speaking, demoing, mentoring, and conversing with existing and prospective customers. We intentionally only do events where we get to contribute this way and over 50% of the company has gone out and demoed in cities around the world, and that percentage keeps growing. |
Contributor
There was a problem hiding this comment.
Suggested change
| Since joining PostHog in summer 2025 we've gone from doing one IRL event to over 100 in a fiscal year and roughly 95% of those events involved an engineer (or other team member) speaking, demoing, mentoring, and conversing with existing and prospective customers. We intentionally only do events where we get to contribute this way and over 50% of the company has gone out and demoed in cities around the world, and that percentage keeps growing. | |
| Since I joined PostHog in summer 2025, we've gone from doing one IRL event to over 100 in a year. Roughly 95% of those events involve speaking to customers, and over 50% of the company has gone out and demoed in cities around the world – and that percentage keeps growing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
daniel-zaltsmanentry tosrc/data/authors.jsonTest plan
/blog/how-we-participate-in-99-irl-events-a-yearprofile_idCreated with PostHog Desktop