Software developer. Systems enthusiast. Always learning.
I like understanding what happens underneath—and making the surface feel right.
Selected work · Noxius Studium · My repositories
I'm Deadtrix21. I learn by building: take an idea apart, turn it into something executable, and find out which assumptions survive.
My interests sit between low-level systems, cryptography experiments, and thoughtful interfaces. I care about memory use, throughput, and small application footprints—but I also care about the details that make a tool pleasant to use. Moving between those layers is part of the fun.
Not everything here is a finished product. Some projects are practical tools; others are experiments or reference implementations. I would rather make that distinction clear than pretend every repository is production-ready.
- What is the machine actually doing? Native code, memory behaviour, FFI boundaries, and the cost of moving data.
- Can I make the behaviour explicit? Event systems, comparable APIs, shared specifications, and useful diagnostics.
- Would I enjoy using this? Desktop utilities, clear controls, and interfaces with attention to detail.
A lot of my recent work lives under Noxius Studium. That is where the wider collection of tools and experiments lives.
A music workspace for Hermes Desktop: Spotify Connect, internet radio, a persistent local library, mixed playlists, and source-aware controls. One listening workflow, without pretending every provider has the same playback engine. Audio visualization is available only where the source exposes samples—not Spotify Connect.
Draft enhancement, reusable prompt libraries, multi-step undo/redo, and explicitly started, owner-bound live voice for Hermes Desktop. Native send controls stay intact. Ordinary voice transcripts remain temporary; delegated tool work stays with the captured chat.
A Python event bus with threaded and asyncio implementations, grouped subscriptions, priority, TTL, hooks, and metrics. An exploration of making message delivery and its boundaries easier to inspect.
My experimental cryptography and native-library work. The public repository currently contains binary artifacts, example files, and screenshots, rather than the implementation source. It is a research project—not a claim of independently audited or production-proven cryptography.
Also worth exploring: REST / GraphQL / SOAP / gRPC, an educational comparison built around one shared resource registry, SQLAlchemy domain model, and contract tests. My private workbench also includes South African ID-number conformance, Rust/Tauri desktop tooling, and Kotlin cross-platform experiments; those are not public downloads.
Have a reproducible bug, a focused improvement, or an interesting technical question? Open an issue or pull request in the relevant public repository.
If my work helps you build something, a visible link back is appreciated. Check each repository's license before reuse—public visibility does not mean identical terms.
Keep the curiosity. Test the assumption. Make the next version better.