About
Who is behind LexLabs, and why the site exists.
I’m Sharquille Andrew, and I’m teaching myself network security the slow, honest way: by building a homelab, breaking it on purpose, and writing down what happened.
Why “LexLabs”
The name is literal. Lex is my shorthand for learning, and labs is where all of it happens: a rack of modest machines, a Proxmox host, EVE-NG topologies, and more cable management than my desk appreciates. Every note on this site started as an experiment at that bench. If a write-up exists here, it’s because I ran the thing, watched it fail at least once, and fixed it.
How I work
I care about evidence more than confidence. My projects keep build logs, toolchain receipts, and gated checkpoints, and my lab’s outbound traffic is a decision rather than a default. Terraform and Ansible describe the infrastructure so I can rebuild any part of it without memory or grief. When something breaks, the question is never just “how do I fix it” but “what will I write down so the next one is faster.”
What I’m working toward
Short term: Security+ certification, a control plane for the homelab that is segmented and documented like production, and steady progress on Iron Harbor, a course platform I’m authoring about network security automation.
Longer term: a career doing this for real, on networks bigger than my spare room.
About this site
Built with Hugo, styled by hand, and set in Newsreader and JetBrains Mono. No analytics, no tracking, no noise. If you want to say hello, the links are in the footer.