I think the posts main mistake is expecting the reader to care about or know this author.
I expect the post is written for readers who care about or know the author.
Goodbye, Forever, Probably
11–20 of 26 posts
Re: Goodbye, Forever, Probably
#12I think the posts main mistake is expecting the reader to care about or know this author.
About their ongoing availability of their personal website (that does have some audience, however niche), the author states
> As for what the future holds for whitep4nth3r, I’m actually not sure. I know I’m not that important in this vast and strange ever-evolving world; I know this won’t affect many people in the grand scheme of things, but I’m sure some of you will be wondering if I’ll still be around.
So I'm not sure your criticism makes any sense
Re: Goodbye, Forever, Probably
#13I think the posts main mistake is expecting the reader to care about or know this author.
What did you expect, though?
dead-dove.jpg
Re: Goodbye, Forever, Probably
#14Small discussion (18 points, 8 hours ago, 11 comments) https://news.ycombinator.com/item?id=48774195
Why can't we vouch for flagged stories like we can for flagged comments? What's there to counteract flagging, just upvotes?
We can under certain conditions (not all flags are the same). It wasn't flagged when I linked it (might be because of the typo?)
Re: Goodbye, Forever, Probably
#15I wish this person the best of luck in their next role. I've known some great DevRel people, but it's a difficult role. The company can frequently have very different ideas about what DevRel should look like than the person hired into the role. The best DevRel people I know spent their time doing things to fill in gaps left by the company such as providing better documentation, example repos, and filtering through al…
In practice, "what's actually best for the community" (growing a community of engaged engineers who feel listened to and who understand what you're doing) is not necessarily easy to show by metrics. I think the author is making a subtler point that, even if you don't hate DevRel work, the most useful kind of work is often unappreciated or devalued by decision makers.
Re: Goodbye, Forever, Probably
#16Uninteresting rant by a nobody, why is this posted here? Account created 13 days ago en passant.
Re: Goodbye, Forever, Probably
#17I think the posts main mistake is expecting the reader to care about or know this author.
She linked to it on her social media and got the word out to people that know her. I don't think she expected it to 'break containment' like this.
It is also a post located on her own personal website, which naturally contains information about herself and is focussed around herself.
I don't think there is any 'mistake' here.
Re: Goodbye, Forever, Probably
#18I think the posts main mistake is expecting the reader to care about or know this author.
Jeesh guys, if you don't care, why did you comment or read it?
I personally thought the post was quite interesting and I honestly felt a strong desire to subscribe. It's a shame they're shutting down.
Re: Goodbye, Forever, Probably
#19I think the posts main mistake is expecting the reader to care about or know this author.
It’s a personal website…
Does remembering a time when blogs and personal websites were a significant part of the Internet experience now mark me as old…
It seems that the expectation today is everything is written or created for an audience and probably for monetization or “influence”.
Re: Goodbye, Forever, Probably
#20I wish this person the best of luck in their next role. I've known some great DevRel people, but it's a difficult role. The company can frequently have very different ideas about what DevRel should look like than the person hired into the role. The best DevRel people I know spent their time doing things to fill in gaps left by the company such as providing better documentation, example repos, and filtering through al…
In practice, "what's actually best for the community" (growing a community of engaged engineers who feel listened to and who understand what you're doing) is not necessarily easy to show by metrics. I think the author is making a subtler point that, even if you don't hate DevRel work, the most useful kind of work is often unappreciated or devalued by decision makers.
True, but in practice "the community" as the DevRel person sees it can be very different than the customer base that the company wants to address.
For example, this DevRel person talks a lot about their Twitch stream and all of the work they put into a game on it that also used Sentry (their DevRel employer). It's all very cool and impressive work, but for a company like Sentry with 100,000+ customers there are millions of engineers across those companies that make up their developer base. Streaming to a couple hundred people on Twitch doesn't even register as interacting with the community.
Reading some of the linked posts there's an ongoing frustration with being asked to provide metrics and prove value, which gets to the core of what I was trying to say above: What some people want to do for DevRel for a small audience (Twitch streaming, podcasts, workshops) is often at odds with what the company expects them to do for their large base of active developers and users.