-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blog: How we do dogfooding at PostHog #8856
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works really well. I think we can tighten it throughout and bring the word count down. Also suggested a slight structural tweak. Bunch of comments on the draft but I reckon this would work well as a newsletter.
|
||
- **Dogfooding as a silver bullet.** Dogfooding shouldn't be the only strategy you use to develop your product. Your goal should be to build something your users want, not just yourself. To do this, talk to users, research your industry and competitors, build, get feedback, and iterate. | ||
|
||
- **Overly dogfooding.** Dogfooding too much can slow you down. You must be comfortable with shipping features before they are fully ready. Real-world feedback is the most valuable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this feels like the same point as the point above?
Co-authored-by: Andy Vandervell <92976667+andyvan-ph@users.noreply.github.com>
Changes
I'm not sure this is the right structure for this, so before too detailed of edits I want to make sure I get that correct. Also, what do you think of this as a newsletter article?
Closes #8736
Checklist
Article checklist
Useful resources