01Build Log
Infrastructure
Building My Private AI Infrastructure
Notes from building a locally controlled AI server around Linux, GPU acceleration, containers, remote administration, and local language models.
LinuxAIGPUDockerInfrastructure
Engineering Notebook
Learn. Build.
Document.
Notes from the workbench — infrastructure builds, security exercises, troubleshooting, experiments, and lessons learned.
Why I Write
Documentation Is Part of the Work
Writing forces me to explain what I built, why I made particular decisions, what failed, and what I would change the next time.
That makes documentation useful for more than remembering commands. It becomes a way to improve troubleshooting, architecture, communication, and technical judgment.
This notebook will continue growing alongside my infrastructure, cybersecurity, identity, automation, and AI work.
Notebook
Current Notes
02Incident Notes
Security
MFA Fatigue: Containment and Response
A practical look at MFA fatigue attacks, how the attack works, what defenders should investigate, and how identity controls can reduce risk.
IAMMFAIdentityIncident Response
03Lab Notes
Networking
Designing a Segmented Home Lab Network
Documenting how I think about separating infrastructure, clients, servers, management interfaces, and lab services while keeping the environment manageable.
NetworkingVLANsSegmentationSecurity
Areas
What I'll Document
Build Logs
Documenting infrastructure and security projects from planning through implementation.
Troubleshooting
Capturing failures, symptoms, investigation steps, root causes, and lessons learned.
Security Notes
Breaking down identity, cloud security, incident response, governance, and defensive concepts.
Experiments
Testing ideas around automation, private AI, Linux, infrastructure, and emerging technology.
“Documenting what I learn turns one troubleshooting session into knowledge I can reuse.”
Hands-On Work