I BUILD THINGSTHAT SHOULDN'TEXIST YET.
Mohammed Kanod is a builder, experimenter, and computer science student exploring the friction between autonomous software, operating system kernels, and physical computation.
Curious by default. Not interested in conventional SaaS templates or safe formulas. I build prototypes to find where systems break and understand why they work.
ENGINEERING &
SYSTEMS ARCHITECTURE.
COMING SOON.
Selected engineering dossiers, prototypes, and systems architectures are currently being compiled.
NOT EVERYTHING I BUILD
IS SUPPOSED TO WORK.
COMING SOON.
Empirical hardware telemetry, acoustic synthesis modules, and adversarial protocols will be indexed here.
LEARN → BREAK → BUILD → QUESTION → REBUILD
“Why does it have to work this way?”
Standard architectures exist for historical convenience, not theoretical optimality. Always interrogate first principles before accepting standard libraries or conventional patterns.
“A working prototype teaches more than endless planning.”
Speculation produces debate; working software produces truth. When an architectural hypothesis is uncertain, write the minimal proof of concept and run it.
“The most interesting projects begin with a strange question.”
Linear goal-setting produces incremental iterations. Unconventional breakthroughs emerge when following deep technical curiosity into unfamiliar domains.
“If something breaks, find out why.”
A system crash or dropped packet is not an inconvenience—it is telemetry. The boundary where software behaves unpredictably reveals its true architecture.
I LIKE SYSTEMS
MOST WHEN THEY
FIGHT BACK.
When software runs as intended, it follows instructions. But when it fails under adversarial conditions, its true assumptions are revealed. I focus on kernel boundaries, memory safety, and raw protocol integrity.
I'M STILL FIGURING
THINGS OUT.
This portfolio is not a monument to a finished expert. It is an honest, real-time chronicle of someone in the thick of learning, experimenting, and finding where the boundaries break.
As a Computer Science and Cybersecurity student, my formal education is the baseline, but the real insights come from late-night experiments—reading systems papers, compiling code from scratch, and reverse-engineering protocols.
I don't believe in fake polish. True technical understanding comes from having the patience to break things down to first principles and the stamina to rebuild them until they hold.
CURRENTLY.
CYBERSECURITY & KERNEL SYSTEMS
Deep-diving into low-level operating system boundaries, eBPF telemetry, memory safety in Rust, and network protocol defense.
LAB INFRASTRUCTURE
Low-latency nodes, kernel monitoring, and private model inference running in continuous integration.