Long-form writing on runtime, distributed systems, kernel internals, Go concurrency, memory models, eBPF, and assembly walkthroughs.
After a few years writing production Go, I stopped thinking of chan as a data pipe and context as a parameter. They're both lifecycle primitives — chan draws the boundary of 'how many alive', context draws the boundary of 'when to die'. Here's why that mental model changes the code you write.
After Four Pillars of Concurrency, the natural question: what does a system actually look like when it uses all of them deliberately? IronSys is a composite blueprint — the concurrency architecture I'd build today if I were starting over, with the trade-offs each choice buys.
Most engineers still reach for the mutex. That's one of four options, and usually not the best one. A working engineer's map of shared-state, CSP, actors, and STM — and when each is the right tool.
Go isn't magic and it isn't faster than Java. It just stops asking the kernel to help. A first-principles look at goroutines, 2KB stacks, and why high-frequency trading engines chase the exact same answer.
Deep dive comparison of Rust and C at assembly level. See how Rust's memory safety, bounds checking, and zero-cost abstractions compare to C's raw performance through actual GDB debugging sessions and assembly analysis.
A comprehensive documentation of my virtualized environment stack designed to analyze, patch, and rebuild legacy Windows applications — from XP-era binaries to modern Win10 apps needing backwards compatibility.
How I placed 2nd solo at BSides Vancouver 2025 Blue Team CTF using only ChatGPT and Splunk: threat hunting, incident response, registry forensics, and AI-driven analysis.
© 2026 HarrisonSec. All rights reserved.