Totally understanding the hesitation - but I’d love to hop on discord and actually discuss what happened several years back. Regardless - I definitely would love to convince you that my abilities as a developer most certainly outweighs whatever risk you feel bringing me on would entail. Over the past few years that I’ve aged/matured, I’ve worked at a stealth startup, built up a non profit + working on my own startup, and am going to be working at SpaceX where we’re working under ITAR regulations among many others: so definitely understand what providing me elevated access would entail.
As for remote repos - I’ll provide more info when we have a chance to chat! I can’t give repo access to most things that I’ve written and think it’d be much easier for me to show you stuff to evaluate.
~ @lordusan
Certainly. If the staff decides to move forward with interviews, I'll make sure that I'm in the loop so I can speak with you then. I don't really have any doubts about your technical prowress--though I am curious to look more into what you've done, I certainly feel the pain of not being able to include proprietary repos in a portfolio--but I do still believe that ComDev will be a good starting point so that I'm more comfortable lifting various access restrictions in the potential future.
That being said, quite a bit has changed on the security policy side. We do operate relatively closely to the PoLP in terms of DevSecOps roles--that is, I've ensured that OS-level access is rarely granted, even among Admins. Future potential CI/CD integrations will hopefully make most manual OS-level operations relatively unnecessary, save for general maintenance and rare emergencies.
I do look forward to the staff decision on this--we're not in much need of SysAdmins right now, but we're certainly short on Software Engineers.
