Julius L Moore
Software Engineering · Networking
Data
one project at a time.

Nurse turned engineer. Building real infrastructure, writing production code, and documenting the entire journey from healthcare to tech.

Software Engineering Networking & Infrastructure Data Analysis & Engineering
About

From bedside to backend.

I'm a nurse pursuing a Software Engineering degree at Western Governors University. But the degree is just one piece — I'm deliberately building projects across three disciplines to develop skills that make me more marketable once I graduate.

Software engineering gives me the foundation. Networking gives me the infrastructure knowledge that most developers never touch. Data engineering ties it all together — because every system produces data, and the people who can build the pipeline from sensor to dashboard are the ones who get hired.

I don't simulate labs. I build production systems on real hardware, break them, troubleshoot them, document what happened, and publish the results. Every project in this portfolio is running live — not in a sandbox, not in Packet Tracer, not in a tutorial.

The home lab isn't part of my degree plan. I'm building it because I figured out that the gap between "I studied networking" and "I built a network" is the gap that gets you hired.

78K+
Lines of production code
7
VLANs configured
5,600+
IoT sensor readings
546
Posts published per week
4
ACLs enforcing policy
5
WiFi SSIDs on 5 VLANs
Lab Network

Enterprise-grade home network.

Cisco C1111-4PWB as sole router with a public IP from Comcast. ISP gateway in bridge mode. Every device in the house routes through infrastructure I configured from scratch.

Internet → Comcast → XB8 (Bridge Mode) → Cisco C1111-4PWB (Public IP)
  │
  ├── GE0/1/0: Acer Server (VLAN 10 · SERVER)
  ├── GE0/1/1: TRUNK → GS308EP (8-port PoE+)
  │     ├── Port 3: Raspberry Pi 4B (Pi-hole + UniFi Controller)
  │     ├── Port 4: UniFi U6+ AP #1
  │     └── Port 5: UniFi U6+ AP #2
  ├── GE0/1/2: TRUNK → GS316EP (16-port PoE+)
  │     ├── Port 2–4: Apple TVs (VLAN 20)
  │     └── Ports 5–14: Wall outlets (future use)
  └── GE0/1/3: Available
VLAN 10
SERVER
192.168.10.0/24
Production servers, Pi-hole, UniFi
VLAN 20
TRUSTED
192.168.20.0/24
Personal devices, full access
VLAN 30
IOT
192.168.30.0/24
Smart home — internet only
VLAN 31
IOT-AUTO
192.168.31.0/24
Automation — MQTT to Pi only
VLAN 40
HOUSEHOLD
192.168.40.0/24
Family devices — internet only
VLAN 50
GUEST
192.168.50.0/24
Guest WiFi — client isolation
VLAN 99
MGMT
192.168.99.0/24
Switch & AP management
Troubleshooting Labs

Real incidents. Real hardware. Documented.

Every lab is a real troubleshooting incident on my home lab network, broken down step-by-step and mapped to CCNA exam topics.

LAB 001

Apple TV Connectivity Failure After Bridge Mode Cutover

After flipping the ISP gateway to bridge mode, Apple TV streaming boxes lost app connectivity while phones and laptops on the same VLAN worked fine.

NAT/PATTCP MSSPi-hole DNSDHCP vs StaticBridge Mode
11 CCNA topics · 4 OSI layers · 9 steps
LAB 002

Tailscale DNS Hijack & TCP Socket Corruption

Installing Tailscale for remote management broke all TCP connectivity — SSH, HTTPS, and streaming failed while ping worked perfectly.

VPN/OverlayDNS ResolutionTCP SocketsOSI ModelHost vs Network
7 CCNA topics · Layer 3–7 · 8 steps
Projects

Three repos. Three disciplines.

Each project targets a different skill set — all running on the same home lab infrastructure.

N

git-init-home-lab

Enterprise home network on a Cisco C1111-4PWB. 7 VLANs, 4 ACLs, dual managed switch trunks, Pi-hole DNS, UniFi WiFi with 5 VLAN-tagged SSIDs. Cisco is the sole router for the entire household.

View repo ↗
D

closet-monitor

ESP32 + BME280 → MQTT → Python → SQLite → Streamlit. Rate-of-change anomaly detection via rolling z-scores. 5,600+ readings, zero packet loss.

View repo ↗
S

fb-content-system

78K+ lines across 3 repos. 546+ posts/week to 3 Facebook pages. MCP server, Remotion rendering, multi-API orchestration, automated engagement on Railway.

View repo ↗