Hacker Newsnew | past | comments | ask | show | jobs | submit | corywatilo's commentslogin

I'll consider a refresh button just for you. Thanks for the kind words.


Hi, OP here. I was employee #13 at PostHog, joining as a designer (who now moonlights as a design engineer). I'm responsible for the website. I've been part of crafting the brand for 4.5 years – joined when the company just started monetizing.

There are only two of us who work on the website, myself and a front end engineer. (He was hired to work on the website and doesn't directly work in the product.)

We've spent roughly half of the last six months on this site. Other than our incredible graphic designer, no other resources were brought in.

A lot of our time is spent on brand-related side quests – they're consistently a net positive for the brand. You can see some examples under "Some things we've shipped" at https://posthog.com/teams/brand

This was a passion project of mine. I'm the one who ultimately chose to spend time I did on it. I think what we built is really cool, and I hope it serves as inspiration for other designers to think outside the box when it comes to solving their unique challenges.

Every company operates differently. Yes, many companies do have employees with too much time on their hands. Others do waste a lot of money in advertising. And a lot of companies are stagnating.

But I can assure you, PostHog is none of those.


The teams window seems to be broken for me, on a non latest version of Firefox. However the blog posts window in the submission works flawlessly.

In the teams window, The first page doesn't load the images but does the content, clicking another item in the menu does show the expected page but again with no images. At some point, clicking the menu items does not load the correct page. At some point after that the images load in, however the correct link to the correct post does not appear. I have to click about 6 times on the same menu link to see a cycling of different posts (possibly the ones I was clicking before) to see the expected post.


how do i learn more?


Info in my profile. If you don't mind I'll shoot you an email, would love your thoughts on some things.

btw - hats down for your work @ PostHog! We are all big fans and deeply inspired by it


lol wow nice catch


posthog design is great- you should be proud. Keep it up


We emailed back and forth several times. CEO was on the thread, was aware of my concerns, chose not to do anything. The result of the back-and-forth was the proposal I shared in the post.


I'm allergic to sales calls. =] Plus, when has jumping on a "quick call with sales"[1] ever resulted in paying less money?

[1] posthog.com/sales


We (at PostHog) have a very unique implementation of Inkeep in our community forums[1], and it's been a lot of fun working on a custom solution with the Inkeep team.

Our ultimate goal was to make our experience explicitly not feel like you're talking to AI.

So rather than trying to intercept questions from being posted to our forums, we trigger Inkeep _after_ a question is posted. If we're able to find an answer with a high degree of confidence, our "AI user" (Max) will show an answer within about 30 seconds.

The OP can then provide feedback that we're using to train further answers.

If the answer is marked as helpful, we display the answer publicly (and disclaim it as an AI response)[2]. If the answer is marked as _unhelpful_, the answer only shows to the OP and we review the feedback to figure out how we can improve (ie: do our docs need to be improved so Inkeep has better source material?).

It's been fun getting creative with the Inkeep team on a solution that worked for our specific use case. I'm planning on rolling out Inkeep more broadly in other areas of our site as we verify that our highly confident answers are genuinely useful to our users.

IMO Inkeep has been the first AI solution that hasn't sucked – and that's high praise coming from me!

[1] posthog.com/community [2] https://posthog.com/questions/autocapture-event-bubbling


Not seeing the first two but feel free to send screenshots to <firstname>@posthog and I'd be happy to take a look.

As for cookie banners, that's something we can both agree on. ;)



1. This should have been enabled by default.

2. You shouldn't have to read docs to find it.

3. It should have been covered in their onboarding.

I'm convinced this is a dark pattern for their sales funnel.


Alternate title: "How to scare an engineer in three words"


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: