Gitlab Handbook's HN Page
31–40 of 200 posts
Re: Gitlab Handbook's HN Page
#32Re: Gitlab Handbook's HN Page
#33> We learned that the key to a post reaching the front page was the content itself. Well that's good news, at least
Re: Gitlab Handbook's HN Page
#34Hey there, I’m a member of the GitLab Community Relations team. My team is responsible for this page. I shared the page today at a DevRel meetup where OP was presenting on Hacker News. I’m grateful he chose to share it with all of you. Thanks, Dan. If there are ways we can improve how we engage with the HN community, myself and our team would love your feedback.
Re: Gitlab Handbook's HN Page
#35Re: Gitlab Handbook's HN Page
#36Re: Gitlab Handbook's HN Page
#37Engagement with the Hacker News community. An euphemism for "the next best thing to free ads" :)
* traffic (which is nice, but not super sticky)
* the comments (which I've found to be insightful and useful in showing both flaws in my arguments as well as additional areas for research/writing)
* the follow-on traffic, as people share it in newsletters, slacks, facebook groups, twitter, etc, etc
The best way to engage with the HN community? To be part of the community (comment, share interesting things that are not your own, etc) :).Re: Gitlab Handbook's HN Page
#38Re: Gitlab Handbook's HN Page
#39Earlier quoted context omitted.
Kind of makes you wonder what they learned was key on other channels.
Presumably there would be a similar page in the Gitlab Handbook if they had findings