What do you build?
I build low-level software with a bias toward direct control, small tools, and reproducible proof.
Main work: DBYTE, DBYTEPAD, DEADGL, firmware probes, board bring-up, and binary tooling.
The goal is simple: tools that explain themselves, fail clearly, and stay small enough to understand.
What is DBYTE?
DBYTE is my language/toolchain work for binary parsing, buffer patching, byte search, typed integer work, and automation.
It is built around practical systems work: bytes, files, tests, VM behavior, modules, and reproducible verification.
Not a toy language. Not a framework mascot. A tool that has to earn its place.
What kind of code do you like?
Native-first, testable, deterministic, and honest about failure modes.
C, Rust, assembly, shell tooling, graphics experiments, reverse engineering notes, and hardware-facing code.
Less ceremony. More proof. No magic unless the magic is documented.
Can I use or redistribute your work?
Check the license inside each repository first. If a repo has no explicit license, ask before reusing it as public code.
For learning, research, and good-faith experimentation, you are welcome to study the work.
Do not use my code, names, or projects to scam people, impersonate me, or ship malicious garbage.
Where can I reach you?
Open an issue on the relevant repository if it is about the code.
For DBYTE-related stuff, use the site, docs, or Discord linked above.
I do not sell private builds through random accounts; anyone claiming that is not me.
Core stack
Small tools. Clear proof. No fake polish.