Update when _not_ to do offsites in SF/London#17835
Open
timgl wants to merge 5 commits into
Open
Conversation
Clarified guidelines for team offsites regarding location preferences and attendee responsibilities.
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 39 errors, 65 warnings, 4 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 |
|---|---|---|---|
| 7:82 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 21:46 | warning | 'Mykonos' is a possible misspelling. | PostHogBase.Spelling |
| 23:178 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 23:293 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 39:180 | warning | Use American English. Use 'traveling' instead of 'travelling'. | PostHogBase.AmericanEnglish |
| 39:201 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 44:125 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 53:207 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 58:32 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 59:3 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 65:26 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 68:24 | warning | 'hoc' is a possible misspelling. | PostHogBase.Spelling |
| 68:39 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 68:83 | suggestion | Prefer 'proper nouns or they' over 'she'. | PostHogBase.Inclusivity |
| 75:117 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 76:230 | warning | Use American English. Use 'organizing' instead of 'organising'. | PostHogBase.AmericanEnglish |
| 77:58 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 79:285 | warning | 'Figjam' is a possible misspelling. | PostHogBase.Spelling |
| 90:64 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 91:3 | warning | 'Dogfooding' is a possible misspelling. | PostHogBase.Spelling |
| 92:11 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 93:56 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 95:167 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 99:103 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 99:158 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 99:313 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 105:4 | warning | 'Hedge House' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 107:39 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 107:219 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 107:355 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 107:368 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 113:49 | warning | 'homebase' is a possible misspelling. | PostHogBase.Spelling |
| 113:66 | warning | 'Farringdon' is a possible misspelling. | PostHogBase.Spelling |
| 117:18 | warning | 'onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 119:4 | warning | 'Marrable's' is a possible misspelling. | PostHogBase.Spelling |
| 119:15 | warning | 'Farringdon' is a possible misspelling. | PostHogBase.Spelling |
| 120:8 | warning | 'Zetter' is a possible misspelling. | PostHogBase.Spelling |
| 120:15 | warning | 'Clerkenwell' is a possible misspelling. | PostHogBase.Spelling |
| 121:17 | warning | 'Clerkenwell' is a possible misspelling. | PostHogBase.Spelling |
| 122:4 | warning | 'Yotel' is a possible misspelling. | PostHogBase.Spelling |
| 125:16 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 126:22 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 127:30 | warning | 'Clerkenwell' is a possible misspelling. | PostHogBase.Spelling |
| 131:178 | warning | Use American English. Use 'optimize' instead of 'optimise'. | PostHogBase.AmericanEnglish |
| 131:220 | warning | 'accom' is a possible misspelling. | PostHogBase.Spelling |
| 133:4 | warning | 'Border Control' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 137:136 | warning | 'colleauges' is a possible misspelling. | PostHogBase.Spelling |
| 137:190 | warning | 'colleauges' is a possible misspelling. | PostHogBase.Spelling |
| 137:992 | warning | Use American English. Use 'traveling' instead of 'travelling'. | PostHogBase.AmericanEnglish |
| 143:290 | warning | 'Embroker' is a possible misspelling. | PostHogBase.Spelling |
| 145:137 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 153:218 | warning | Use American English. Use 'maximize' instead of 'maximise'. | PostHogBase.AmericanEnglish |
| 155:36 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 157:116 | warning | 'repurpose' is a possible misspelling. | PostHogBase.Spelling |
| 157:445 | warning | Use American English. Use 'canceled' instead of 'cancelled'. | PostHogBase.AmericanEnglish |
| 185:128 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 185:141 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 196:145 | suggestion | Prefer 'proper nouns or their/them' over 'her'. | PostHogBase.Inclusivity |
| 205:48 | warning | 'intracontinental' is a possible misspelling. | PostHogBase.Spelling |
| 224:72 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 244:131 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 246:37 | warning | Use American English. Use 'organize' instead of 'organise'. | PostHogBase.AmericanEnglish |
| 250:109 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
contents/handbook/people/spending-money.md — 22 errors, 21 warnings, 2 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 7:98 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 10:88 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 21:24 | warning | 'Janani' is a possible misspelling. | PostHogBase.Spelling |
| 26:205 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 38:56 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 40:51 | warning | 'Hiberly' is a possible misspelling. | PostHogBase.Spelling |
| 47:130 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 49:358 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 53:26 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 54:31 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 63:6 | warning | 'Team Leads' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 64:194 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 68:64 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 78:17 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 78:33 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 82:5 | warning | 'Onboardings' is a possible misspelling. | PostHogBase.Spelling |
| 84:51 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 84:57 | warning | 'Janani' is a possible misspelling. | PostHogBase.Spelling |
| 84:156 | suggestion | Prefer 'proper nouns or they' over 'she'. | PostHogBase.Inclusivity |
| 89:70 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 89:151 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 108:10 | warning | 'Janani' is a possible misspelling. | PostHogBase.Spelling |
| 110:17 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 119:40 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 119:49 | warning | 'Kendal' is a possible misspelling. | PostHogBase.Spelling |
| 133:62 | warning | 'Spotify' is a possible misspelling. | PostHogBase.Spelling |
| 142:120 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 142:129 | suggestion | Prefer 'proper nouns or their/them' over 'her'. | PostHogBase.Inclusivity |
| 145:319 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 152:109 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 158:270 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 168:113 | warning | 'Nextstand' is a possible misspelling. | PostHogBase.Spelling |
| 169:14 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 172:6 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 173:7 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 174:10 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 184:56 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 186:88 | warning | 'Zluri' is a possible misspelling. | PostHogBase.Spelling |
| 186:374 | warning | 'plaftorm' is a possible misspelling. | PostHogBase.Spelling |
| 186:456 | warning | 'Zluri' is a possible misspelling. | PostHogBase.Spelling |
| 189:231 | warning | 'Zluri' is a possible misspelling. | PostHogBase.Spelling |
| 190:176 | warning | 'Zluri' is a possible misspelling. | PostHogBase.Spelling |
| 198:73 | warning | Use American English. Use 'traveling' instead of 'travelling'. | PostHogBase.AmericanEnglish |
| 212:54 | warning | 'Hogpatch' is a possible misspelling. | PostHogBase.Spelling |
| 212:76 | warning | 'Hedgehouse' is a possible misspelling. | PostHogBase.Spelling |
Contributor
Bundle reportTotal JS (gzip)6.21 MiB (no change) Eager graph (static-import closure per entrypoint)
Largest modules in the
|
| Module | Size |
|---|---|
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 |
709.9 KiB |
./src/components/Stickers/Stickers.tsx |
696.4 KiB |
./.cache/caches/gatsby-plugin-mdx/mdx-scopes-dir/31a094f140f119e73085d847ae81b99b.js + 2 modules |
519.2 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/@codemirror+view@6.38.2/node_modules/@codemirror/view/dist/index.js |
458.1 KiB |
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules |
395.1 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.cjs.js |
364.8 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 |
./src/hooks/useCustomers.tsx + 54 modules |
353.9 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 |
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js |
281.9 KiB |
./node_modules/.pnpm/@codesandbox+sandpack-react@2.20.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@codesandbox/sandpack-react/dist/index.mjs |
266.6 KiB |
./src/components/ProductComparisonTable/index.tsx + 114 modules |
264.0 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 |
239.9 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.
Added guidelines for hub travel budget to encourage visits to SF and London.
Added reasons to avoid offsites in hubs and clarified planning details.
timgl
changed the title
charlesvien
reviewed
Jun 23, 2026
|
|
||
| #### Hub travel budget | ||
|
|
||
| We want to encourage people to visit our hubs in SF (Hogpatch) and London (Hedgehouse). You still need _some_ reason, like an event you're talking at, working with a specific person who will also be there, but |
Member
There was a problem hiding this comment.
", but ", did something get cut off here?
Member
There was a problem hiding this comment.
i think its an incomplete pr, this change also does not make sense
marandaneto
reviewed
Jun 23, 2026
Comment on lines
-261
to
-282
| ## All company offsite hackathon | ||
|
|
||
| The hackathon is always a highlight of the offsite. We tend to run them like this: | ||
|
|
||
| **Session 1: ideation dinner** | ||
| The day before the start of the hackathon we do a casual 'ideation' dinner where we encourage people to chat about ideas | ||
|
|
||
| **Session 2: hackathon kick-off** | ||
| The hackathon kick off is 1.5 hours at the end of the day. Ideally we do this in a conference room with beers and wine. | ||
|
|
||
| - Everyone writes down their ideas on multiple post-it notes in about 10 minutes. | ||
| - People come up to the front one-by-one, and they get 30 seconds to pitch all their ideas. | ||
| - Everyone gets three votes to put on whichever ideas they like most. Just do this as a tally. You can't vote on your own idea | ||
| - We dismiss all ideas with zero votes, and sort all the other ideas from top to bottom based on the number of votes. | ||
| - Everyone writes their name on the other side of the sticky bit of a small piece of post-it note, then add their name to the idea they want to work on. Every group should have at least two people in it, and ideally 3. | ||
| - Once groups are formed, everyone can go off and ideate or hack. | ||
|
|
||
| **Session 3: presentations** | ||
|
|
||
| This should be the last work related session of the offsite. Again ideally in a conference center with beer and wine provided. | ||
|
|
||
| Each group gets 5 minutes to demo and present their idea. |
Gilbert09
approved these changes
Jun 23, 2026
Comment on lines
+46
to
+51
| Some reasons to _not_ have your offsite in one of our hubs include: | ||
| - Visa restrictions into both UK and US | ||
| - Excessive travel time | ||
| - You're running a large, multi team (10+ people) offsite, and want to optimize for lots of quality time, over hanging out with other PostHog people | ||
| - You want to be heads down to start or complete a big project, and don't want the distraction of other people around | ||
| - You and a large portion of the people at this offsite have been to both London and SF a lot, and so would prefer a different location |
Member
There was a problem hiding this comment.
I think this is too prescriptive, and we'll eventually have to make this list more exhaustive ("well what about this other thing? can that be a reason? let's add it to the handbook."). I think we should be aiming for:
- Explain the reasons why the hubs are appealing
- Ask for reasons people decide to go elsewhere so we can make the hubs more appealing.
Suggested change
| Some reasons to _not_ have your offsite in one of our hubs include: | |
| - Visa restrictions into both UK and US | |
| - Excessive travel time | |
| - You're running a large, multi team (10+ people) offsite, and want to optimize for lots of quality time, over hanging out with other PostHog people | |
| - You want to be heads down to start or complete a big project, and don't want the distraction of other people around | |
| - You and a large portion of the people at this offsite have been to both London and SF a lot, and so would prefer a different location |
| - You and a large portion of the people at this offsite have been to both London and SF a lot, and so would prefer a different location | ||
|
|
||
| If you do decide to do a small team offsite somewhere outside of these two hubs, let Kendal know why. That way we can figure out how to make going to the hubs more appealing, or perhaps open new hubs. | ||
| As always, we trust you to make the right decision here, balancing personal preference with what's best for the company. If you do decide to do a small team offsite somewhere outside of these two hubs, let Kendal know why. That way we can figure out how to make going to the hubs more appealing, or perhaps open new hubs. |
Member
There was a problem hiding this comment.
Suggested change
| As always, we trust you to make the right decision here, balancing personal preference with what's best for the company. If you do decide to do a small team offsite somewhere outside of these two hubs, let Kendal know why. That way we can figure out how to make going to the hubs more appealing, or perhaps open new hubs. | |
| Traveling to new places is a perk for PostHog employees. At the same time, going to the hubs, especially for newer joiners, can be beneficial to you as an employee and to the company as a whole. We trust you to make the right decision here, balancing personal preference with what's best for the company. | |
| If you do decide to do a small team offsite somewhere outside of these two hubs, let Kendal know why. That way we can figure out how to make going to the hubs more appealing, or perhaps open new hubs. |
|
|
||
| #### Hub travel budget | ||
|
|
||
| We want to encourage people to visit our hubs in SF (Hogpatch) and London (Hedgehouse). You still need _some_ reason, like an event you're talking at, working with a specific person who will also be there, but |
Member
There was a problem hiding this comment.
I think requiring a reason defeats the purpose a bit. We just want people to get together.
Suggested change
| We want to encourage people to visit our hubs in SF (Hogpatch) and London (Hedgehouse). You still need _some_ reason, like an event you're talking at, working with a specific person who will also be there, but | |
| We encourage people to visit our hubs in SF (Hogpatch) and London (Hedgehouse). These places generally have a high density of PostHog employees around, so you'll get to meet people from other teams, which makes cross-team work much easier and more successful. SF also has the benefit of being the epicenter of everything happening in tech, and we have lots of YC founders working out of Hogpatch who you can meet and learn from. It's good to get exposure to this, especially if you don't live in SF or haven't been recently. | |
| There is no specific travel budget, this can come out of your general employee budget. We strongly encourage you to use your budget for this reason! | |
| If you do decide to come, we ask that you make the trip worthwhile - attend a conference, speak at an event, gather a few colleagues to come with you at the same time and work on something specific together. Don't just pop in and put your headphones in while there - make it worth your while. |
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
5 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.
regarding https://posthog.slack.com/archives/C06LMMS3YP4/p1782121772246829?thread_ts=1779399367.316289&cid=C06LMMS3YP4
Changes
Please describe.
Add screenshots or screen recordings for visual / UI-focused changes.
Checklist
vercel.json