DtnamoDB is a pretty poor DNS resolver, but @alexbdebrie is the person to talk to about it. I wound up hiring him to fix a thing on contract; strongly recommend.
If Matt looks like the kind of person you'd enjoy having in your company, I'd suggest reaching out sooner than later. His greatest challenge right now is articulating exactly what he wants to do next; once he solves that he won't be available for long.
And now: you've likely heard of @AskAManager; in this thread ask an admittedly-terrible employee what to do for an "alternate" take on workplace questions.
(DMs are open if you’d prefer not to implicate yourself.)
"Only white guys interview for an open role."
Ask the folks at your company who aren't over-represented what they think of the job description and tweak accordingly.
If everyone at the company is a white guy, you have your answer already.
Ever notice that companies always like to define a key employee leaving as "hit by a bus?"
A thread on this weird, weird, WEIRD framing.
It turns out that the number of employees who leave for "a different job" dramatically outweighs the number of employees who are hit by buses in virtually every geography.
But it terrifies companies if you raise the spectre of taking a new job. Far better to raise the spectre of your untimely demise instead, because it makes your employer more comfortable that way.
Speaking of shitposts: @azure paying @forrester for reprint rights to demonstrate @awscloud's superiority is funny / normal, but WTF is going on over at @alibaba_cloud?!