Frank Xue — software engineer
Building useful software with AI.
I enjoy building software with AI coding assistants. I usually start with a problem I have encountered, write down what I want to make, and use AI to help implement it. I want to keep exploring what useful things I can create this way.
The projects here are mostly written in Rust: gm-crypto-rs is a library for China's SM2, SM3 and SM4 cryptography standards, published on crates.io; the tools for AI coding agents and CI runners are private projects; and the explainer-video pipeline is written in Python, with public source and pre-release status.
View selected work(02) About
A little about me.
In a sentence
I'm a software engineer who cares about clarity: code that can be audited, tools that explain their state, and interfaces that do not make routine work feel mysterious.
Read the longer version(03) Selected work
One project, in depth.
Case study
gm-crypto-rs is a pure-Rust library for China's SM2, SM3 and SM4 cryptography standards, published on crates.io. While working with Chinese cryptographic tools, I found relatively few related tools in the Rust ecosystem, which led me to start this project. The case study covers the problem, how the work was divided, the evidence, and what it doesn't claim, including that it has not been independently audited.
Read the case study(04) Notes
Working through a problem.
-
Building gm-crypto-web
A small browser tool for checking SM2, SM3 and SM4 against known vectors without installing anything — and the parts I'd rather say out loud than leave implied. Read →
-
Sharing code is not the same decision as sharing a package
The reflexive move when two things share code is to extract it into its own package. That's the wrong test. The right one is a trigger, decided and named before anyone needs it. Read →
-
A constant-time claim is a trust problem, not a comprehension problem
Explaining constant-time execution is the easy part, and it isn't what a skeptical reader needs. What transfers warrant is a detector that must flag a deliberately introduced leak, and a caveat written before anyone asks for it. Read →
(05) Contact
Say hello.
Direct
GitHub is the most direct way right now — @frankxue831. An issue or discussion on any of my repos reaches me too; for other conversations, LinkedIn works.
How to get in touch