My name is KennyB, and for over a decade, I served as a senior finance and operations executive (CFO) for mission-driven organizations. I led teams, managed multi-million dollar budgets, and ensured our organizations were compliant and fiscally sound. But behind the scenes, there was another part of my job: I was always the glue between IT deploying new business tech and driving its adoption and value.
This site is my public lab notebook: practical guides, reproducible setups, and leadership patterns that scale.
I was the person who served as the *de facto* product owner, business analyst, and project manager for every major enterprise system we implemented—from ERP and HRIS platforms to CRM and spend management tools. I loved it. I discovered that my real passion wasn't just solving the business problems, but architecting, implementing, and teaching the technical solutions that empowered the organization to do its work better, faster, and more securely.
Let's go.
So, I decided to make a change.
I'm now formally transitioning my career into the world of technology and cybersecurity, building on years of practical, in-the-trenches experience.
## My Unique Perspective
My background as a CFO gives me a unique perspective. I don't just see technology; I see the business case behind it. I understand risk not just as a technical vulnerability, but as a potential impact on the balance sheet, on compliance, and on reputation. I bridge the gap between the executive and board table and the command line, translating complex business needs into secure, effective technical requirements.
## What You'll Find Here
This blog is a chronicle of my journey and a place to share what I'm learning along the way. I focus on three core areas:
1.**Home Lab & Projects:** Deep dives into the practical, hands-on tech projects I'm working on, from building a virtualization cluster with Proxmox to deploying SSO with authentik, and everything else as I continue to philosophically and pragmatically center data sovereignty.
2.**Cybersecurity News & Commentary:** Analysis of current events and security topics, always with an eye toward the business and financial implications.
3.**Career & Certification Journey:** Documenting my path from a non-technical background into a formal cybersecurity role, including my experience with certifications like the (ISC)² CC and CISSP.
Whether you're a fellow career-changer, a tech professional who wants to better understand the business side of things, or just someone who loves to tinker, I hope you'll find something valuable here. Thanks for reading.
> Sometimes the difference between a 'production-ready stack' and 'why is my NAS on fire?' is one missing space in a YAML file.
> Sometimes the difference between a 'production-ready stack' and 'why is my NAS on fire?' is one missing space in a YAML file. *bang head on wall here*
It started innocently enough:
It started innocently enough:
a single `docker-compose.yml`, neat and tidy, humming along like a well-trained orchestra. Then I added *one* new service—my self-hosted note app—and everything fell apart.
a single `docker-compose.yml`, neat and tidy, humming along like a well-trained orchestra. Then I added *one* new service—my self-hosted note app—and everything fell apart.
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
