--- title: "Harrison Guo (@harrisonguo) | Hashnode" description: "Security engineer and distributed systems practitioner. Writing about systems internals, performance, security research, and AI applications. Building harris..." url: "https://hashnode.com/@harrisonguo" --- @harrisonguo # Harrison Guo @harrisonguo · WhiteRock, CA · Joined March 2026 [Website](https://harrisonsec.com/) ### [AI Gave Everyone a Red Team. It Did Not Give Anyone Judgment.](https://harrisonsec.hashnode.dev/ai-gave-everyone-a-red-team-it-did-not-give-anyone-judgment?utm_source=hashnode&utm_medium=feed) AI dropped the cost of a red team to roughly the price of the tokens, and the easy conclusion is that security skill is now a commodity. 6 min read · [harrisonsec.hashnode.dev](https://harrisonsec.hashnode.dev/ai-gave-everyone-a-red-team-it-did-not-give-anyone-judgment?utm_source=hashnode&utm_medium=feed) [1d ago](https://hashnode.com/posts/ai-gave-everyone-a-red-team-it-did-not-give-anyone-judgment/6af7409b46e187112d5a6246) ### [Rust vs C Assembly: Complete Performance and Safety Analysis - Panic or Segfault?](https://harrisonsec.hashnode.dev/rust-vs-c-assembly-complete-performance-and-safety-analysis-panic-or-segfault?utm_source=hashnode&utm_medium=feed) 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. 14 min read · [harrisonsec.hashnode.dev](https://harrisonsec.hashnode.dev/rust-vs-c-assembly-complete-performance-and-safety-analysis-panic-or-segfault?utm_source=hashnode&utm_medium=feed) [Oct 23](https://hashnode.com/posts/rust-vs-c-assembly-complete-performance-and-safety-analysis-panic-or-segfault/6adb8e295f9298d26d3dc520) ### [NATS vs Kafka vs MQTT: Same Category, Very Different Jobs](https://harrisonsec.hashnode.dev/nats-vs-kafka-vs-mqtt-same-category-very-different-jobs?utm_source=hashnode&utm_medium=feed) All three are 'messaging systems.' None of them is interchangeable with the others. 10 min read · [harrisonsec.hashnode.dev](https://harrisonsec.hashnode.dev/nats-vs-kafka-vs-mqtt-same-category-very-different-jobs?utm_source=hashnode&utm_medium=feed) [Oct 23](https://hashnode.com/posts/nats-vs-kafka-vs-mqtt-same-category-very-different-jobs/6adaf90eef2560f8c195d4b6) ### [Benchmarking an Agent Without Lying to Yourself](https://harrisonsec.hashnode.dev/benchmarking-an-agent-without-lying-to-yourself?utm_source=hashnode&utm_medium=feed) Most agent benchmarks are not wrong on purpose. They are contaminated: the task set leaked into training, the fixtures moved between runs, the. 7 min read · [harrisonsec.hashnode.dev](https://harrisonsec.hashnode.dev/benchmarking-an-agent-without-lying-to-yourself?utm_source=hashnode&utm_medium=feed) [Oct 15](https://hashnode.com/posts/benchmarking-an-agent-without-lying-to-yourself/6ad102340c908f302bae95eb) ### [API Auth Bugs Are Usually State Bugs](https://harrisonsec.hashnode.dev/api-auth-bugs-are-usually-state-bugs?utm_source=hashnode&utm_medium=feed) Most API authorization bugs get described as a missing check, as if someone forgot an if statement. They are almost never that. 9 min read · [harrisonsec.hashnode.dev](https://harrisonsec.hashnode.dev/api-auth-bugs-are-usually-state-bugs?utm_source=hashnode&utm_medium=feed) [Oct 13](https://hashnode.com/posts/api-auth-bugs-are-usually-state-bugs/6ace5f32c7aa0a2a88f98717)