Most of what I build starts the same way: something refuses to explain itself. A Delphi binary hiding its class model in runtime metadata. A Rust sample whose payload exists only for the instant its own decryptor runs. An application whose traffic will not take a proxy and will not say where it goes. Obscurity is the part I like. The answer is always somewhere in the artifact, if you are willing to take it apart to get at it.
The other half of the work is connective tissue. Two systems that will never agree on a vocabulary, so xLate translates between them in a single dependency-free binary. An audit lifecycle scattered across spreadsheets and screenshots, so Conformiti holds it. A questionnaire nobody answers the same way twice, so Countersign drafts from your own documentation and cites every line it writes. A demo environment that drifts the morning of the call, so Greenroom puts it back. Casework spread across ten tools and a notebook, so NocTORnal draws the graph and ties every edge to an exhibit.
Different problems, one shape: find the seam where two things fail to meet, then build the piece that makes them meet. I work across C#/Avalonia, Python, Go, C, Rust and Delphi, with a bias toward encryption, duress design, and software that behaves correctly when someone hostile is in the room. A wallet with a second truth. Folder encryption that lies on command. A kill switch for the minutes after you walk away. It is all open, because the code is the argument.