sacrvm — Latin: “a sacred thing; a rite.” Also MARCVS, rearranged.
Full-stack developer, architect, tech lead by day — .NET, Azure, and whatever else the project needs. Visionary by night, using AI to raise thirty years of craft to a higher power. What lives here are the private passions.
A suite of DJ tools on one shared engine: analysis, tagging, playback and broadcast, installed side by side on a single runtime. Key, BPM, energy and loudness detection built for harmonic mixing — not a plug-in for someone else's library, but the library itself.
Every number in my code is one of three things: measured, derived, or chosen — there is no fourth case. Claims keep the measurement that produced them, and when one turns out wrong, the retraction stays in the file.
The expensive bug is not a wrong calculation — it is a correct calculation on a false premise, because nothing breaks. A surprising result gets checked against something external before it gets believed.
There is no undo, by design. Anything that moves, renames or deletes your files says exactly what it is about to do, names every file it will touch, and waits.
Each project keeps a ledger of what is known to be broken and what was built on top of it anyway. A workaround that lives only in code gets explained away — and an empty list proves nothing.
Verdicts come from the product — the built executable, the real screen — never from a flattering preview. A green test that proves nothing is a bug like any other.
Agents build for me around the clock, budgeted and scoped. Nothing they make is committed, shipped or believed until my own eyes and ears have signed it.