Earlier quoted context omitted.
Set to merge.
You're gonna break the internet! Infinite loops are bad.
We need to link to Stack Overflow.
Gitlab Handbook's HN Page
101–110 of 200 posts
Re: Gitlab Handbook's HN Page
#102GitLab's been good for our company, having it all under one roof has been nice. But recently I've had (and continue to have... still not resolved) a pretty unpleasant experience with their support software. It just seems like the typical comedy of errors where a series of software integration papercuts between them and Zendesk adds up to a really bad experience, made much worse by the fact that our issue hasn't been…
Not directly relevant, but I've had all sorts of issues, similar in nature, with other companies that use Zendesk and integrations with Zendesk. It seems surprisingly bad given its popularity.
Re: Gitlab Handbook's HN Page
#103> Never submit GitLab content to Hacker News. Submission gets more credibility if a non-GitLab Hacker News community member posts it, we should focus on making our posts interesting instead of on submitting it. I appreciate this policy, it makes it clear that HN is a place to engage with the community, rather than a free advertising channel. Looking at the CEO's profile, the last time he made a submission about Gitla…
I wish all marketers in the world can read this...
[deleted]
Re: Gitlab Handbook's HN Page
#104Since it is a common usenet/forum/flame warrior method, I have a strong opinion about: Address multi-faceted comments by breaking them down and using points, numbering and quoting. Except when the facets are purely technical, this approach trends toward full defensive point by point rebuttal. Once the points counting starts, the logic of points-counting becomes part of the public performance. In general, people don’t…
I think it's quite situational, but I quite agree. I also find that when you do this and get into a conversation with somebody who does this, the back-and-forth also just bloats up and gets bigger and more multi-faceted as the conversation progresses.
I find that it's much better to just address the general argument and maybe the very major points specifically if necessary. I think bad-faith arguments on the internet have made a lot of people really defensive and aggressive, though. I've seen a lot of people smugly arguing past each other about how they aren't discussing things properly ("you didn't even address all of my points"), and the discussion always devolves to just arguing about arguing.
Re: Gitlab Handbook's HN Page
#105Hey 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.
What does DevRel mean? I’ve never seen this term.
This is particularly amusing given the guideline “Avoid using corporate jargon like 'PeopleOps'.”
Re: Gitlab Handbook's HN Page
#106Earlier quoted context omitted.
Lobsters is a good one. (You need an invite.) And I'm a member of some slacks that are just killer in terms of content and discussion. Too bad about the memory hole.
You should consider moving that slack to discord. Discord has unlimited server history for free with pretty good search. The only features you lose compared to slack are ones that are largely only useful for organisations. (If you do move it to discord, invite pls :P)
...Can we not have more projects move to a proprietary, closed source chat system? (And one that tracks every mouse movement you make...)
Zulip, Discourse, Element(formerly Riot) / Matrix all exist and are fairly nice. And of course, IRC. Searching works well for Zulip/Element.
Re: Gitlab Handbook's HN Page
#107Hey 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.
Hey John, I'm interested in DevRel and Evangelism on your team. I've read some of your documentation and enjoyed what I've read. I'm a dev of 5 years and I'd like to apply to your team. Could you give me some pointers and tips about the interviews? Thanks!
Re: Gitlab Handbook's HN Page
#108Earlier quoted context omitted.
You should consider moving that slack to discord. Discord has unlimited server history for free with pretty good search. The only features you lose compared to slack are ones that are largely only useful for organisations. (If you do move it to discord, invite pls :P)
Discord is too associated with gamer culture which is fairly rancid.
this is a nonsense argument. you can moderate and restrict your discord channel to enforce whatever culture you want. if you don't want bad culture infesting your channel then don't let it happen. i would still suggest people use matrix over discord, but it has nothing to do with gamer culture.
Re: Gitlab Handbook's HN Page
#109Re: Gitlab Handbook's HN Page
#110Earlier quoted context omitted.
Discord is too associated with gamer culture which is fairly rancid.
this is a nonsense argument. you can moderate and restrict your discord channel to enforce whatever culture you want. if you don't want bad culture infesting your channel then don't let it happen. i would still suggest people use matrix over discord, but it has nothing to do with gamer culture.
Discord has a centralized profile system built around gamer culture and the idea of using a “handle” that is rightly disconnected from your identity. It has so many features designed around gaming.