+
+ I teach information technology at the community-college level in Central Texas. My classroom blends structured curriculum with a relaxed, community style — a lot like troubleshooting a vintage radio while sharing a plate of gumbo.
+
+ When a platform update breaks a thousand identical PCs, the fix isn't a newer certificate or a bigger hammer. It's tracing the signal path one stage at a time. That's the whole of my teaching, whether the stage is a vacuum tube, a network switch, or an emulation layer.
+
+
+
+
+
+ New: The ARM Wall
+ When Outlook and Teams went dark on ARM-powered PCs this week — same app, same Friday, but only the Surface machines broke — thousands of IT desks lit up. My new short film traces the signal path: why the emulation layer is the fault, and the three things to check before you reimage the box. It's also on my 4ort.mov channel.
+
+ Live headlines tracking the ARM story.
+
+
+
+
+
+ What I know, what I've made, what I'm saying
+
+
+
+
+
+
+
+
+
+
+ A student once asked me why her laptop couldn't reach the gateway. We traced the path together — physical link, IP config, DNS, firewall rules — and I realized I was using the same mental map I use when a vintage radio won't tune: follow the signal, test each stage, don't guess — measure.
+
+
+
+ The Five-Stage Diagnostic Flow
+
+ - Verify the source — Is the device powered? Is the radio plugged in? Is the laptop on?
+ - Check the path — Trace the physical connection. Coax? Ethernet? Wi-Fi signal strength?
+ - Test the stage — Measure voltage at each tube. Ping the gateway. Check switch port status.
+ - Isolate the fault — Swap a known-good component. Replace the tube, swap the patch cable, try another port.
+ - Verify the fix — Retest the full signal path. Tune the station, browse the web, confirm the service.
+
+
+
+
+ Worked Example: "No Internet"
+ Student reports: laptop shows connected, but no pages load.
+
+ | Stage | Classic Radio | Modern Network | Test |
+ | 1. Power | Plug in radio | Device on | Power light lit? |
+ | 2. Physical link | Antenna connected | Ethernet/Wi-Fi | Link light on? |
+ | 3. Stage signal | IF stage working | IP config valid | ipconfig / ping gateway |
+ | 4. Isolation | Swap tube | Try known-good cable | Move to another port |
+ | 5. Verify | Station comes in | Web page loads | Full end-to-end test |
+
+
+
+
+ Common Failure Modes
+
+ - Signal lost at first stage — No link light, no antenna connection, cable unplugged.
+ - Stage works in isolation but not in circuit — Good ping to gateway, but DNS fails. The local oscillator is fine, the IF filter is the problem.
+ - Intermittent fault — Works when warm, fails when cold. Solder joint, thermal expansion, or a loose RJ-45 clip.
+
+
+
+
+ Printable Diagnostic Flowchart
+ Download the one-page PDF: circuit-thinking-flow.pdf
+ Pin it above your bench. Teach your students to trust the signal path, not their assumptions.
+
+
+
+
+
+
+
+ These guides grew out of my classroom at Central Texas College. When a student stares at a router config the way I once stared at a chassis full of tubes, the same diagnostic logic applies: follow the signal, verify each stage, don't guess — measure.
+
+
+
+
+
+ Why This Approach?
+ I've watched students memorize OSI layers without ever seeing a signal on a scope. When you trace a hum in a 1950s Philco, you learn why Layer 1 matters. The components change; the reasoning doesn't.
+ Each guide includes worked examples, common failure modes, and a printable one-page diagnostic flowchart you can pin above your bench.
+
+
+
+