About the Lab
BytesNation is a one-person tech lab where hardware meets software meets infrastructure. Everything here is built by hand, broken on purpose, documented in the open, and shared so the next person does not start from zero.
No sponsors. No editorial calendar. No content for content's sake. Just field notes from someone who builds things and writes down what happens.
The Builder
Combat veteran. Self-taught systems architect. 16 years building, securing, and troubleshooting enterprise networks, firewalls, and datacenter infrastructure.
Started hosting gaming servers as a teenager. That turned into managing enterprise networks. Enterprise networks turned into firewalls. Firewalls turned into datacenter architecture. Somewhere along the way, 3D printers and microcontrollers showed up on the bench because the best way to understand a system is to build one from scratch.
Now I run BytesNation to document the process: the builds, the failures, the iterations, and the things I wish someone had told me 16 years ago.
No degree. No formal training. No certifications on the wall collecting dust. Just obsessive curiosity and a habit of breaking things until they work.
MokeyBytes. This is who builds the lab.
Why Build in the Open
Most of what I know came from someone else's build log, teardown, or lab notebook. Knowledge hoarding is a dead end. Sharing accelerates everyone. BytesNation exists because I got tired of being the guy who "figured it out" and never wrote it down.
Document everything
Successes are easy to share. Failures are where the real lessons live. Both get documented here.
Share the process
Polished results are useless without context. The decisions, tradeoffs, and dead ends matter more than the final output.
Hand the map forward
Someone else's build log saved me hundreds of hours. This is how I pay that forward.
What Gets Built Here
These domains are not siloed. A 3D-printed enclosure houses a microcontroller that monitors network traffic that feeds a security dashboard running in the datacenter. Everything connects.
3D Printing Lab
Mods, slicer profiles, material tests, and build logs.
Microcontroller Builds
ESP32, Arduino, custom boards, and sensor rigs.
Networking
Topology maps, lab routing, VLANs, and packet flow.
Cybersecurity
Threat modeling, detection experiments, and hardening.
Datacenter Architecture
Capacity planning, rack layouts, and power design.
On the Bench
Active builds, prototypes, and experiments. Some ship. Some teach you what not to do next time.
MK-01 Printer Retrofit
Hotend swap, enclosure airflow tuning, and power monitoring.
Focus: Reliability
Edge Lab Node
Mini rack build with routing, observability, and storage.
Focus: Networking
Packet Forensics Rig
Capture box with analysis pipelines and alerting.
Focus: Detection
How I Work
The principles behind the builds.
Systems thinking
Every component exists in a system. Fixing a symptom without understanding the architecture just moves the problem somewhere else.
Iterate, then document
Build it. Break it. Rebuild it. Then write down what actually worked and why the first three attempts did not.
Security is not a feature
It is a constraint. Every design decision, every network topology, every deployment pipeline gets evaluated through a threat model.
Open by default
Configs, topologies, slicer profiles, automation scripts. If it is not a secret, it is public. Gatekeeping knowledge helps no one.
Connect
The lab is open. Pick a channel.