At 14 he started shipping. At 19 he ships kernel-level security infrastructure, a programming language, and a 151-test blockchain validator. The bottleneck was never the code — it was the chassis.
Every kernel trace, every cargo build, every QEMU boot of an LSM-patched kernel, every 151-test suite — all of it shares 8 gigabytes with the editor, the browser and the CI runners, on a CPU that predates the mainstream eBPF toolchain he now contributes to upstream.
| CPU | Intel Core i5-8250U — 2017, 4C/8T, 15 W |
|---|---|
| Memory | 8 GB RAM — the actual ceiling of his career so far |
| GPU | NVIDIA GeForce 940MX — 2016 |
| Storage | 240 GB SATA SSD (WD Green) + 1 TB 5400 rpm HDD |
| OS | Arch-based · Omarchy + Hyprland · LUKS full-disk encryption |
| Upgrade path | none — sealed purchase, five years and counting |
Note: the machine predates the eBPF toolchain it now builds. The code kept evolving. The chassis didn't.
Kernel-level anti-ransomware agent for Linux — ~280k events/s at <8% CPU, automated SIGKILL response. crates.io + GHCR + release binaries, 99 tests, 4 CI pipelines. ★20.
A language built from scratch — one typed source compiles to readable Python, Bash and bytecode. 300+ tests with a differential harness across all three backends. Live browser playground.
A from-scratch Solana validator: ledger, Reed-Solomon erasure coding, Tower BFT,
Gossip, RPC — 151 tests, -D warnings enforced, cargo audit clean.
A stackable Linux Security Module with upstream-style patches, built and run in QEMU. The kind of code that decides what a machine is allowed to do.
Bare-metal chain-of-trust: real SHA-256 + post-quantum ML-KEM-768 in firmware — who gets to boot, proven in silicon-adjacent code.
File encryption that assumes the adversary records now and decrypts later — ML-KEM-768 + AES-256-GCM, fuzz-tested.
Plus: NV2_ENGINE — a voxel engine on wgpu with real NASA climate worlds and an embedded neural net, published to crates.io. Externum on PyPI since v2. CI/CD, releases and containers on every active repo. 14 packages across 4 registries. An accepted article on LinuxSecurity. Three open pull requests in aya-rs/book — the eBPF community's own docs. And, for stamina's sake: The Stitcher Trilogy, three crime-horror novels published on Amazon. Same discipline, different craft.
“I don't need a laptop that's faster than everyone else's.— the entire pitch, in one sentence
I need one I'm allowed to upgrade.”
If there's a creator, student, community or review path to a Laptop 13 Pro or Laptop 16, here's what comes back — written for engineers, no marketing gloss:
cargo build, real RAM ceilings, kernel tracing, QEMU, containers —
what actually breaks, what doesn't, measured, not narrated.
framework-system is Rust; the public firmware trackers are where he
already works. Upstream contributions where his chain-of-trust and kernel experience
actually helps.
Five years of software,
compiled four gigabytes at a time.
The next chapter should be upgradeable.