Good day. You have found your way here, and for that I am quietly grateful.
It is possible you arrived by mistake. These things happen. One opens a link, follows another, and before long stands somewhere unintended. Still, since you are here, I may as well explain what sort of place this is, and what sort of person tends to inhabit it.
I have never been especially good at accepting things simply because they work. When a system behaves in a certain way, I want to know why, and when an abstraction insists on hiding its mechanisms, I find myself wanting to lift the cover.
Some years ago, this inclination led me to an unusual project. I began designing my own assembly language for the JVM. Not because it was sensible, nor because it was efficient, but because the existing tools felt too polite, too eager to smooth over the rough edges. I wanted to see the machinery directly, even if that meant getting my hands dirty.
If there was suffering involved, it was at least a familiar and honest kind.
Much of my time is spent developing plugins for PaperMC. It began as a practical exercise, a way to make a server behave as I thought it should, but over time it turned into something closer to a long conversation with the platform itself. Each API decision leaves a trace, each workaround tells a small story about intent and compromise.
More recently, I have found myself contributing to OpenJDK. This was not something I planned in advance. It happened gradually, as unanswered questions accumulated and small irritations refused to remain private. Reading the source, proposing changes, watching them discussed and reshaped by others has been a humbling process, and a strangely reassuring one.
Alongside this, I am engaged in an ongoing struggle with Minestom. It is fast, opinionated, and unapologetically different, and it has no hesitation in exposing my assumptions for what they are. I lose often, learn a little, and return again, not quite defeated, not quite victorious, but still involved.
As for qualifications, I have collected a few. Not out of ambition, exactly. I simply dislike being wrong, and exams are efficient at pointing out where one is.
I listen to music, often while doing nothing else. It helps me think, or perhaps helps me avoid thinking too directly. I write code in much the same way others might keep a journal. Methodically, sometimes obsessively, and occasionally with regret. I read when I can. Other minds have a way of clarifying one’s own, even when they disagree entirely.
Below is a small reflection of what I listen to, drawn from Apple Music, where many uneventful evenings quietly pass.
I hold an IT Passport, issued by the Ministry of Economy, Trade and Industry. It does not grant travel privileges, but it does mark a certain shared understanding of how systems, organizations, and people tend to fail.
Other certifications include the Information Security Management Examination, the Fundamental and Applied Information Technology Engineer Examinations, the Network Specialist Examination, and the Registered Information Security Specialist credential. Each represents a period of concentrated attention, and a reminder that explaining systems to humans is often harder than building them.
I maintain a JVM assembler that uses the .jal extension and occasionally feels more expressive than it ought to be. I remain convinced that placing an opening brace on the same line is a small but meaningful ethical lapse. I develop Minecraft and PaperMC plugins, sometimes as work, sometimes as an extended experiment in restraint. I care deeply about Java, but it is the JVM itself that continues to hold my attention, with its quiet compromises and carefully hidden complexity.
Japanese is the language I think in, argue in, and occasionally misunderstand myself in. English is a language I use with care. It serves well enough for technical discussion and the occasional dry remark. Latin I know only in fragments, enough to recognize the shape of old thoughts. Esperanto was learned out of curiosity and a certain optimism, though it is rarely spoken.
I write code with more care than is probably necessary, and with a faint hope that someone, someday, will notice the intent behind it. If you wish to collaborate, contribute, or simply express confusion, you are welcome to do so.
"If you can't understand it, you don't belong here." — Mike Gancarz