30 years in IT, a weakness for automation and a passion for MIDI hardware. I build editors that finally make synths, controllers and effects processors readable.
The MIDI Studio editors are public alphas you can use today in a Chromium browser. The rest is in testing or in preparation: here is a preview.
Browser editor for the Behringer BCR32 controller: live front panel, assignments, MIDI Learn, Cubase MIDI Remote export.
Editor and librarian for the TC Electronic FireworX multi-effects: routing, modulation, banks, random variations.
Editor for the TC Electronic M3000 (live over SysEx) and M2000 (offline) reverb processors.
Editor for Korg AI² synthesis: the X5DR live over MIDI (Program, Combi, Multi, Drums, Global) and 20 more models as files, conversions between models, library.
++
Graphical editor for the CS12 surface: rebuilt front panel, TFT screen, knobs, fader, slots and pages, exportable profiles, Cubase link.
A WYSIWYG word processor that feels like Word and saves Markdown. Rust, native and WebAssembly.
It fits the spirit of the times: ditch Word and heavyweight formats and go back to simple things. A Markdown file has no macros, no plugins and no database to patch. Minimal attack surface, readable in twenty years by any editor, versioned with Git. Everything WordPress is not: the security, portability and maintainability of a plain text file.
Take charge of your career instead of enduring it: active career management for people who work.
Efficient management of your real-estate portfolio: your properties, tracked and managed in one place.
Pulled automatically from my GitHub every time the site is built.
Well-understood laziness is respecting your own time.
I started with the computing of the early days and went through legacy, cloud, CI/CD and now AI. My principle hasn’t changed: simple, verifiable, automated. The MIDI Studio editors illustrate it: every write to the hardware is read back and confirmed, nothing is stored without an explicit action, and known limits are documented rather than hidden.
— Do you use AI?
A question I was once asked, with a very serious face.
Excellent question. Let us examine the exhibits: repositories, commits, tests, changelogs of suspicious polish. None of it constitutes a formal confession. Vibe-coding tools do not issue a signed receipt, and to my knowledge “wrote code very fast” has never been admitted as evidence in any court.
No confession, therefore presumption of innocence. And if a detector claims otherwise, remember that it also flags correct punctuation and bullet lists.
