aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXe Iaso <me@xeiaso.net>2023-04-22 07:54:00 -0400
committerXe Iaso <me@xeiaso.net>2023-04-22 07:54:00 -0400
commit9d9614ad8a4a1d00f7df1b0e37ec32d324151335 (patch)
tree9725b3d1a77e4a2c2269c19ae8bf39a442221017
parent88f89c7a5fc58752e5d2f7dd8fdab31ab4e991ff (diff)
downloadxesite-9d9614ad8a4a1d00f7df1b0e37ec32d324151335.tar.xz
xesite-9d9614ad8a4a1d00f7df1b0e37ec32d324151335.zip
you'd think i'm a writer or something lol
Signed-off-by: Xe Iaso <me@xeiaso.net>
-rw-r--r--dhall/resume/resume.typ2
1 files changed, 1 insertions, 1 deletions
diff --git a/dhall/resume/resume.typ b/dhall/resume/resume.typ
index dab184f..eafeb51 100644
--- a/dhall/resume/resume.typ
+++ b/dhall/resume/resume.typ
@@ -136,7 +136,7 @@ If you want someone that is dedicated to their craft, a fearless innovator and a
At Tailscale I founded the developer relations team with the goal of inspiring people to use Tailscale in fun and interesting ways. I work with the DevRel team to write articles for #text(fill: blue)[#link("https://tailscale.dev")[tailscale.dev]] to help teach people fundamentals of computer science and networking in the process of learning about new product features and things you can do with them.
-Tailscale has easily been the best job I've ever had and I've had an enormous impact on how Tailscale is percieved by developers worldwide. For a while my actions were directly attributable to MAU growth. One of the hardest project I've worked on was how to make DevRel efforts more than single flashes in the pan and create a reason for people to visit the website.
+Tailscale has easily been the best job I've ever had and I've had an enormous impact on how Tailscale is percieved by developers worldwide. For a while my actions were directly attributable to MAU growth. One of the hardest projects I've worked on was making DevRel efforts more than single flashes in the pan and create a reason for people to visit the website on a regular basis.
While I worked at Tailscale, I attempted to spearhead the use of Nix and NixOS to declaratively manage our servers. This would have given us full knowledge of what packages and services were running on which servers, allowing us to know at a glance what server was doing what. Unfortunately, this project ultimately failed in ways that taught me a lot about the importance of clean, accessible documentation that is written for people that don't already understand the topic at hand. Even when a technically superior solution may exist, it is better to meet people where they are at and move forward together as a team.