Trace the whole path
A symptom rarely respects team boundaries. Start at the user, follow every layer, and test the story against reality.
OBSERVE → ISOLATE → VERIFYNetwork operations · Infrastructure · Systems
I make complex systems observable
I work where networks, infrastructure, and people meet—troubleshooting hard failures, improving messy processes, and building practical systems that hold up.
DK / 01
Systems
thinking Trace the whole path.
thinking Trace the whole path.
Select a node
01
Operating principles
Good infrastructure should feel quiet.
Not simple underneath—clear at the surface. Reliable, understandable, and ready for the strange day.
Build for the handoff
A system is not finished when it works once. It is finished when someone else can understand, operate, and recover it.
CLEAR → REPEATABLE → DURABLEAutomate the friction
Remove the repetitive parts without hiding the logic. The best tools make good decisions easier to repeat.
REDUCE → DOCUMENT → IMPROVE
02
Selected systems
Where curiosity becomes infrastructure.
Small enough to understand end to end. Real enough to expose the tradeoffs.
01
NETWORK LAB / ONGOING
Resilient home edge
Open-source firewalling, remote access, traffic visibility, virtualization, and a deliberate path toward segmentation and failover.
- OPNsense
- WireGuard
- Proxmox
- UniFi
02
SMALL-ORG IT / PRACTICAL SECURITY
Human-scale cloud operations
Turning scattered accounts, files, devices, and access patterns into a manageable workspace—with the process and safeguards to match.
- Microsoft 365
- Identity
- SharePoint
- Policy
03
OPERATIONS / TOOLING
Automation for the annoying parts
Converting repetitive checks, fragile copy-paste work, and handwritten reports into guided tools that stay transparent.
- Python
- PowerShell
- Spreadsheets
- APIs
03
About the operator
Technical depth.
Human context.
I’m Daniel, an infrastructure-minded technologist based in Ohio. I like the problems that live between systems: where a routing issue looks like an application issue, a process issue hides inside a spreadsheet, or an obscure failure needs both patience and a packet-level view.
CURRENT TRAJECTORY
SupportOperationsEngineeringWhat’s next
Going deeper in network engineering, Linux, cloud infrastructure, and automation—while staying close to the real-world problems those systems exist to solve.
THE FUTURE IS A SYSTEM WE’RE ALREADY OPERATING.