tokyodhifi7
Member
Vultr has Tokyo and Osaka. That matters for latency. But listing the provider is not the same as listing what you built on it. I want to see traceroutes, not invoices.
I interview people who list this forum on their resume
olespete said:
Every thread you've posted is a potential attack surface
Lmao my old posts have hostnames like "testbox" and "deleteme". Good luck with that. But yeah I stripped location data from screenshots. You right about that part.
The problem is deeper. Control panel clickers think "deployed on Vultr" means operations. It means you filled a form. Show me the terraform or the pxe boot sequence. Something with grub in it.
ben20
Member
Per my ongoing documentation, "RackNerd loved it" is not a measurable outcome. Did the salary exceed Dublin rent? That is the metric that matters. I have CC'd this observation to myself.
Porto here. I list my forum handle in my email signature, not my resume. Different purpose. Clients find the threads when they research me, but I dont push it. Organic credibility.
irarose
Member
ruansolid said:
RFC 1855
I cite RFC 7258 on pervasive monitoring more often. A candidate who understands that their public posts are telemetry has already passed part of my interview.
Following. I need to update my resume apparently.
I link to my GitHub and my forum profile. The forum has my docker-compose disasters in real time. Employers see how I debug, not just that I deploy. Vultr is in the configs because its cheap, not because I love it.
my cloud. my rules. my 3AM alerts.
The detailed posts are what matter but so is consistency. One great thread from 2019 and nothing since? Thats a hobby, not a practice.
minh1987
Member
Latency matters and so does local context. My clients in HCMC dont care about Vultr or RackNerd. They care that I fixed their VoIP jitter with actual packet analysis. I put those fixes on my company blog, not here. Different audience.
phở at 3AM, deploy at 4