// IDENTITY
About::
The handle is p4r4d0xb0x. I move between the layer underneath the abstractions and the things stacked on top of it.
- posts
- 39
- whoami
- p4r4d0xb0x
- cat ~/.focus
- low-level systems · infrastructure · AI/ML · security · math
- cat ~/.principle
- automate it, then write down why
So I never have to understand it twice
If I do not write down what I read and understood, six months later I am reading the same document from scratch. This site is a personal archive built to cut that loop.
The primary reader is me, six months from now. Anything that fails that bar never gets published.
The floor, and what sits on it
There are two axes of interest. One is the floor — memory, binaries, kernels, networks: the layer you only see after peeling off one abstraction.
The other is what gets stacked on top of it — models, pipelines, deployment. Security and reverse engineering follow naturally, because that is where the two axes meet.
Do it twice and it becomes a tool
Once I have done the same task twice, I stop doing it by hand. The blog publishing pipeline, the release-note generator and the content-rewriting CLI all came out of that rule.
Artifacts explain what I have built faster than claims do.
The limits of these documents
Everything here is grounded in personal experience and study. Some posts may not reflect the latest syntax or ecosystem changes.
If you spot something wrong, tell me and I will fix it — the comments under each post or the email below both work.
Contact
Technical questions, corrections and collaboration proposals are all welcome. Replies may be slow, but everything gets read.