Open
Conversation
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 6 errors, 14 warnings, 0 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 |
|---|---|---|---|
| 16:11 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 16:29 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 34:15 | warning | 'Blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 36:373 | warning | 'Blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 38:241 | warning | 'blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 38:312 | warning | 'blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 38:346 | warning | 'blitzscale' is a possible misspelling. | PostHogBase.Spelling |
| 46: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 |
| 47: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 |
| 48:18 | 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 |
| 50:5 | warning | Capitalize 'Revenue Analytics' for PostHog's product. Use 'Revenue analytics' for the general industry concept. | PostHogBase.ProductNames |
| 50:39 | warning | Capitalize 'Customer Analytics' for PostHog's product. Use 'customer analytics' for the general industry concept. | PostHogBase.ProductNames |
| 54:18 | 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 |
| 57:54 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 63:111 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 65:224 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 65:364 | 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 |
| 69:3 | warning | 'unpeel' is a possible misspelling. | PostHogBase.Spelling |
| 69:21 | 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 |
| 69:242 | warning | 'Annika' is a possible misspelling. | PostHogBase.Spelling |
eli-r-ph
reviewed
Apr 29, 2026
|
|
||
| Other times you might have an idea for a great product we should build. In that case, use the <PrivateLink url="https://github.com/PostHog/requests-for-comments-internal/blob/main/_TEMPLATES/request-for-comments-new-product.md">New Product RFC template</PrivateLink>. You might choose to hack together a prototype of the product to demo and show off, which you should do! Blitzscale only needs to get involved if you want to start working on this product full time. At that point, we are choosing whether to invest a pretty serious amount of money into launching it, so we want to get that right. | ||
|
|
||
| The best products are often ones that not everyone thinks is a good idea before launch. For example, Tim was against building Session Replay, and it's probably the thing PostHog is most known for today. To make sure we take big bets, _any_ blitzscale team member can OK a new product being built, even if other blitzscale members disagree. That blitzscale person will be the one who the new team reports to. This way we avoid consensus stopping us from making big bets. |
There was a problem hiding this comment.
s/thinks is a good/thinks are a good/
|
|
||
| Other times you might have an idea for a great product we should build. In that case, use the <PrivateLink url="https://github.com/PostHog/requests-for-comments-internal/blob/main/_TEMPLATES/request-for-comments-new-product.md">New Product RFC template</PrivateLink>. You might choose to hack together a prototype of the product to demo and show off, which you should do! Blitzscale only needs to get involved if you want to start working on this product full time. At that point, we are choosing whether to invest a pretty serious amount of money into launching it, so we want to get that right. | ||
|
|
||
| The best products are often ones that not everyone thinks is a good idea before launch. For example, Tim was against building Session Replay, and it's probably the thing PostHog is most known for today. To make sure we take big bets, _any_ blitzscale team member can OK a new product being built, even if other blitzscale members disagree. That blitzscale person will be the one who the new team reports to. This way we avoid consensus stopping us from making big bets. |
Collaborator
There was a problem hiding this comment.
Suggested change
| The best products are often ones that not everyone thinks is a good idea before launch. For example, Tim was against building Session Replay, and it's probably the thing PostHog is most known for today. To make sure we take big bets, _any_ blitzscale team member can OK a new product being built, even if other blitzscale members disagree. That blitzscale person will be the one who the new team reports to. This way we avoid consensus stopping us from making big bets. | |
| The best products are often ones that not everyone thinks is a good idea before launch. For example, Tim was against building Session Replay, and it's one of our most popular products. To make sure we take big bets, _any_ Blitzscale team member can OK a new product being built, even if other Blitzscale members disagree. That Blitzscale person will be the one who the new team reports to. This way we avoid consensus stopping us from making big bets. |
Collaborator
There was a problem hiding this comment.
(judging by #brand-mentions, people still overwhelmingly talk about PostHog for analytics above other stuff)
Collaborator
|
Should this be Blitzscale team members who manage product teams? (Like, I assume our future sales lead or I shouldn't do this. Could be fun though.) |
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
4 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.
Changes
As we get more blitzscale team members, there's a higher change that we end up only building new products everyone agrees is a good idea. That's a sure-fire way of making sure we never take big bets. Update guidance to say only one blitzscale team member has to think a new product is a good idea for us to invest in it.
Also update some of the guidance on what new products are a good idea, like building products for the future not the past.
Checklist
vercel.json