Location: Dallas, TX, USA
Remote: Yes
Willing to relocate: Austin, TX only
Technologies: Appsec, Pentesting, Red-Teaming, Golang, Python, Java.
Résumé/CV: https://www.kickresume.com/cv/jNx0E/
Email: tanner.barnes(@)kashx.io
---
Dev turned cyber-security-engineer. Looking to move out of the consulting space into an Appsec role or security focused dev in the tooling space.
I needed a way to support N number of monitors to a long running task which lead me to making MultiNWriter. It supports adding/removing duplicated writers at runtime allowing things like adhoc websocket monitors to a command execution output.
I currently work as a Penetration Tester for a consultancy where I work on multiple different projects from web application testing, internal/external network assessments, Cloud Config Reviews, and Social Engineering. While I get some opportunities to build bespoke tooling for my colleagues I would like to make that my focus and get back to using my passion as a developer. A job where I could build security focused tooling/products would be amazing but am open to any dev position.
This is interesting to me because my mother has MS and it's _because_ the blood-brain barrier is too open that she has health issues. Surprising there's good reason to open it up.
I learned about this from a talk given by one of the authors. The guy next to me asked, "If you open up the blood-brain barrier, doesn't that mean nasty things can cross, too?" and the author was like, "yep." There are definitely risks.
It's an interesting problem - I was reading about bipolar, which also (probably) has the issue of too open a blood-brain barrier. There is a theory that repairing the blood-brain barrier would help, but as drugs repair the barrier, it's harder to get drugs into the brain from the blood, which means the doses need to be higher, which means the side effects are worse.
I could imagine a treatment protocol of opening the blood-brain barrier and then administering a low dose of a drug, or something along those lines
