My home lab is where architecture stops being theoretical. It is a working environment for reproducing failures, evaluating platforms, prototyping infrastructure and learning how systems behave before they become somebody else’s production problem.
A place to break things on purpose
I’ve always learned technology by getting close enough to it to understand the failure modes. The lab lets me test operating systems, networking, virtualization, storage, automation and embedded hardware without treating a customer or employer’s environment as the experiment.
Compute
Multi-core workstation and server hardware for development, virtualization, AI experiments and workloads that need more than a laptop.
Storage & network
Large local storage, backup systems and managed networking for testing resilient infrastructure, segmentation and real-world data movement.
Edge & embedded
Raspberry Pi, ESP32 and other small systems for appliance design, hardware integration, sensors and projects where software has to meet the physical world.
Why maintain a lab in the cloud era?
Because abstractions leak. Cloud services are extraordinarily useful, but understanding storage latency, network behavior, identity boundaries, resource contention and recovery is easier when you can see the machinery. The lab keeps that intuition sharp and gives me a place to validate ideas before turning them into architecture decisions.
If I’m going to recommend a technology, I prefer to have actually made it misbehave first.