Becoming the first DevRel at Tailscale
tailscale.dev
tailscale.dev
Sometimes everything clicks and it's fantastic, I get a week's worth of work done in a day. I don't have control over it, and it's terrifying because when I'm in a slump I have no idea when I'll get back out again. But it better be soon, or people are going to start asking questions!
Trying to reconcile ADHD with the expected mode of production feels futile. Cool to see there are jobs that align better. Gonna think about what this means for my future.
In the second place, why not? Does it cost you anything to acquiesce to a person wishing to be addressed a specific way? (Also, speaking as a woman, fuck the "polite she" idea.)
I knew a lot of actually-weird weirdos at my first tech job a decade ago; my coworkers since have been rather less weird on average.
Props to Tailscale for encouraging/allowing Xe to be themselves in a mutually-beneficial way.
"I started working on Developer Relations (DevRel) at Tailscale in Spring 2022."
"In Spring 2022, I sat down and started to take DevRel seriously at Tailscale. I had heard about the practice in the past, but I had never done it before."
"I got permission from my manager to get a 50/50 split between what I was doing (work on internal tooling that was not sparking joy) and this new experimental DevRel thing."
Edit: Since I'm getting downvoted. To be clear, I'm not trying to attack the person... it isn't about proving the individual's work. I'm sure they are a great contributor. What I'm questioning is the need to publish this on the tailscale website, it is something I'd expect on a personal blog. I'm questioning the clickbait title.
It's a necessary role, and one that can be thoroughly positive for all the parties involved (devs, the product, the company), but managers who are unable to understand intuitively what good DevRel looks like will always try to push for metrics that will inherently destroy any attempt at doing good DevRel.
So, well, even if this was something shared to convince a manager (hard doubt on that btw), it would still be vaulable, unless you want a bunch of marketers with IT expertise to speak at events.
You're making a few absolute statements but not providing anything to back that up. If the role is necessary, then it would be a lot easier to justify. If it is hard to write a job req for the role, then I'd question the need for a role.
(Catchy Bit: Factual Description is a standard sort of title and cropping it to just Factual Description is a standard sort of title edit here)
How so? What do you understand hyperfocus to be? Are you subject to it?
'sharpen your skills'
It doesn't imply, to me, that the sharpened blade should be used as a weapon.
- attack the problem
- circle the wagons
- on the warpath
- exploit vulnerability
- killed that interview
- nuke and pave
- shot across the bow
- shoot yourself in the foot
etc., and I don't think those stand out a ton in writing in or about our industry.I dunno. Did 'weaponizing hyperfocus' as the sole title imply malfeasance or discrimination or abuse to you or something like that? I can see getting that kind of a vibe.
Again, the word 'weaponized' was not necessary to convey the point at all. If the title was simply: "Hyperfocus: Becoming the first DevRel at Tailscale", it seems less aggressive or clickbaity. At that point, might as well just go with 'less is more' and remove the Hyperfocus part too.
It makes perfect sense to me. One of the attention regulation difficulties with ADHD is a tendency to get sucked down deep rabbit holes, and it can be extremely derailing in terms of productivity, and then consequently for morale. It's difficult to predict and often impossible to control.
In Xe's case, they figured out a way to turn the results of those unexpected, unwelcome trips into something of recognized value. Settling into this role likely provides relief from a periodic feeling of helplessness and self-loathing.
How is the original title inappropriate? How is it unclear what the article is about or why it matters?
That said, the way the title is now, seems most appropriate, it is simple and conveys the content of the post.
I see that the blog post on the tailscale website is also marked as 'personal'... and I'd argue that a corporate website isn't the appropriate place for a blog post like this. It is the first post marked as such, so maybe it is an experiment to see how it goes. I'm all for that, but this seems like a big miss to me personally.
I was going to put this on my own website but the other people on the DevRel team asked me to make it the first post on tailscale.dev. So I made it the first post on tailscale.dev.
I will take your feedback into account to improve future writing.
I think that "transmuting a source of pain to a source of joy" is a very descriptive and wonderful title. It humanizes things in a way that is not aggressive like the word 'weaponizing' is.
It's good to be exposed to different people in the world.
[0] I think Xe has indicated that they are a non-binary identifying member of the LGBTQ+ community who has ADHD so I think that counts as diverse. Hoping someone can tell me if the fact that Xe uses animals as avatars indicates something as well.
> [...] how working on DevRel has transformed a part of me from being an impediment that I was at war with into a catalytic asset that makes my job easier.
> In the process of doing this, I also had a unique opportunity to weaponize something that had previously been a horrible vice: my tendency to hyperfocus on things. This tendency has been my savior and my jailor for most of my professional career.
These are from the article itself. Learning to make hyperfocus something powerful and useful is the whole theme of the post. In what sense can the title be considered "clickbait"?
If you meant, "Not the most professional marketingspeak ever utilized", then I don't believe that's what "clickbait" means.
I said "arguably clickbait".
I don't see how that relates.
I honestly hope that's not the case of course.
Just remember Master Yoda's words:
If Once You Start Down The Dark Path, Forever Will It Dominate Your Destiny.
May the Force Be with You.
I've been a fairly large open source developer for 20+ years. It is likely that you use either software I wrote or had a hand in, every single day.
> I'm not trying to attack you but this comment sounds like it's from someone who is trying to justify their probably less envious position.
I'm not trying to attack you, but let me attack you. ¯\_(ツ)_/¯
I for one would like corporate blogs to be closer to personal blogs.
Maybe DevRel can include just talking to developers like a normal person.
Please, no. Corporations are made up of people, but are not people.
I can't imagine in 1000 years reading this on IBM's website.
* Code
* History
* Tips/Support
* Other
* Non-Computer
Here's the non-computer category for you: https://devblogs.microsoft.com/oldnewthing/tag/non-computer.The articles are good, but I don't think the findings are substantially more unique than what probably many other people in tech are experiencing.
I don't think there is some big conspiracy behind it, but I wonder if it might be the result of some algorithmic feedback loop: The system knows those sources as valuable, so posts reach the frontpage often, so people upvote them often, so the system registers them as even more valuable, etc...
That or there is some bit of HN lore that I don't know. In which case I would be interested in learning :)
It's not that "the system" knows them as valuable, it's that people have gotten to know them over time and trust them. These are people, for me, whose articles I'll always make time for. I suspect a lot of HNers feel similar, so that's a lot of upvotes, so that's a lot of frontpage hits.
to be clear you dont owe us any of this, i'm just reporting my own confusion after going on your site and not knowing what "Archmage of Infrastructure" is (i only realized that your resume is public while typing this... oops)