Skip to content
View GerMP21's full-sized avatar
  • Synaptech Solutions
  • Uruguay
  • 07:49 (UTC -03:00)
  • LinkedIn in/germanmp

Organizations

@Synaptech-Solutions-SAS

Block or report GerMP21

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
GerMP21/README.md

German — software developer in Uruguay: LLM systems, audio plugins and developer tools

Synaptech Solutions LinkedIn Ko-fi GitHub

01 — whoami

Hi, I'm German 👋 I'm a software developer based in Uruguay. I like finding creative solutions to problems, and I'm always learning in a field that never stops changing. These days I build LLM-integrated solutions and AI automation, audio plugins for music production, open source developer tools, and SaaS products for my own business. Still, part of me misses building models the old-fashioned way, by hand with TensorFlow or scikit-learn, and I'm always looking for an excuse to get back to it. Feel free to explore my repositories, open an issue or reach out if you'd like to build something together.

show as text

Hi, I'm German 👋

I'm a software developer based in Uruguay. I like finding creative solutions to problems, and I'm always learning in a field that never stops changing.

These days I build LLM-integrated solutions and AI automation, audio plugins for music production, open source developer tools, and SaaS products for my own business. Still, part of me misses building models the old-fashioned way, by hand with TensorFlow or scikit-learn, and I'm always looking for an excuse to get back to it. Feel free to explore my repositories, open an issue or reach out if you'd like to build something together.

02 — projects

Omnisnap (Go, AGPL v3): shows which elements render differently in every browser engine your users run, with one command and the browsers already installed. It compares element geometry instead of pixels, reports each difference at the element where it starts, and writes a self-contained report; it also runs as a GitHub Action and from npm or PyPI. Release candidate v0.1.0-rc.5.

Corrosion (Rust, VST3 + CLAP): an industrial physical-modeling instrument. Bowed, struck, scraped and blown pipes, plates, chains and cables, followed by drive, body, space and a diode clipper.

DGI RUC proxy (Node.js, Express): a JSON REST API for Uruguay's DGI taxpayer (RUC) web service. It handles the SOAP envelopes, WS-Security signing and XML-in-CDATA parsing behind bearer-token authentication.

mysql-split-import (Python): imports multi-gigabyte mysqldump files in resumable, per-table transactions, so a dropped connection costs one part instead of the whole night. Standard library only.

dotfiles (Shell): my CachyOS + niri desktop, with scripts that install, link, set up and verify the whole system.

show as text
  • Omnisnap (Go, AGPL v3): shows which elements render differently in every browser engine your users run, with one command and the browsers already installed. It compares element geometry instead of pixels, reports each difference at the element where it starts, and writes a self-contained report; it also runs as a GitHub Action and from npm or PyPI. Release candidate v0.1.0-rc.5.
  • Corrosion (Rust, VST3 + CLAP): an industrial physical-modeling instrument. Bowed, struck, scraped and blown pipes, plates, chains and cables, followed by drive, body, space and a diode clipper.
  • DGI RUC proxy (Node.js, Express): a JSON REST API for Uruguay's DGI taxpayer (RUC) web service. It handles the SOAP envelopes, WS-Security signing and XML-in-CDATA parsing behind bearer-token authentication.
  • mysql-split-import (Python): imports multi-gigabyte mysqldump files in resumable, per-table transactions, so a dropped connection costs one part instead of the whole night. Standard library only.
  • dotfiles (Shell): my CachyOS + niri desktop, with scripts that install, link, set up and verify the whole system.

03 — how i work

Docs come first. Before I write any code I write down what I'm building and why, along with what "done" looks like, and the code has to answer to that document. The specs live in the repository next to the code, are versioned with it and get reviewed like code. I switch between two spec-driven development tools depending on the job: OpenSpec when I'm changing an existing system. Every change starts as a proposal with its tasks and the spec changes it implies. Once it ships, it gets archived and merged into the main specs, so they always describe how the software behaves today. agent-skills when I want the whole path from idea to release: refining the spec, breaking it into tasks, building in small verifiable steps, testing, reviewing and shipping. Working this way is also what makes AI coding agents useful to me. I use Claude Code and OpenCode. An agent working from a written spec has a contract to follow, and I can review what it produces against that spec rather than against a chat history. It's the same habit behind my audio plugins, where every design document starts with a single sentence. If you'd like to contribute to one of my projects, the specs are the best place to start.

OpenSpec agent-skills Claude Code OpenCode

show as text

Docs come first. Before I write any code I write down what I'm building and why, along with what "done" looks like, and the code has to answer to that document. The specs live in the repository next to the code, are versioned with it and get reviewed like code.

I switch between two spec-driven development tools depending on the job:

  • OpenSpec when I'm changing an existing system. Every change starts as a proposal with its tasks and the spec changes it implies. Once it ships, it gets archived and merged into the main specs, so they always describe how the software behaves today.
  • agent-skills when I want the whole path from idea to release: refining the spec, breaking it into tasks, building in small verifiable steps, testing, reviewing and shipping.

Working this way is also what makes AI coding agents useful to me. I use Claude Code and OpenCode. An agent working from a written spec has a contract to follow, and I can review what it produces against that spec rather than against a chat history.

It's the same habit behind my audio plugins, where every design document starts with a single sentence. If you'd like to contribute to one of my projects, the specs are the best place to start.

04 — coming soon

Opencode-Hyperflow An OpenCode plugin that runs development from product spec to release as a state machine with quality gates. The LLM orchestrates while deterministic TypeScript tools do the work: planning waits until every open question is resolved, implementation is test-first, and shipping requires lint, tests, coverage, security scanning and fuzzing. It won't install, delete, commit or deploy anything without your approval. Status: v0.1.0 MVP: 11 agents, 21 commands, 16 skills and 37 tools, with 113 tests passing. License: MIT.

show as text

Opencode-Hyperflow

An OpenCode plugin that runs development from product spec to release as a state machine with quality gates. The LLM orchestrates while deterministic TypeScript tools do the work: planning waits until every open question is resolved, implementation is test-first, and shipping requires lint, tests, coverage, security scanning and fuzzing. It won't install, delete, commit or deploy anything without your approval.

Status: v0.1.0 MVP: 11 agents, 21 commands, 16 skills and 37 tools, with 113 tests passing. License: MIT.

05 — stack

Stack — LANGUAGES: Python · Rust · TypeScript · JavaScript · PHP · HTML · CSS; FRONTEND: htmx · SvelteKit · React · Tailwind CSS; MOBILE: React Native · Expo; BACKEND: FastAPI · NestJS · Express · GraphQL · REST · Zitadel; DATA: PostgreSQL · MySQL · MariaDB · MongoDB · Neo4j; SCRAPING: Playwright · Patchright · Scrapy · Selenium · Browser Use; AI / ML: LangChain · LangGraph · NumPy · pandas · scikit-learn; more: TensorFlow · Claude · Gemini · OpenAI; AUDIO: Rust · nih-plug · egui · CLAP · VST3; WORKFLOW: OpenSpec · agent-skills · Claude Code · OpenCode; TOOLS: Linux · GNU · Docker · Neovim

show as text
  • LANGUAGES: Python · Rust · TypeScript · JavaScript · PHP · HTML · CSS
  • FRONTEND: htmx · SvelteKit · React · Tailwind CSS
  • MOBILE: React Native · Expo
  • BACKEND: FastAPI · NestJS · Express · GraphQL · REST · Zitadel
  • DATA: PostgreSQL · MySQL · MariaDB · MongoDB · Neo4j
  • SCRAPING: Playwright · Patchright · Scrapy · Selenium · Browser Use
  • AI / ML: LangChain · LangGraph · NumPy · pandas · scikit-learn
  • More: TensorFlow · Claude · Gemini · OpenAI
  • AUDIO: Rust · nih-plug · egui · CLAP · VST3
  • WORKFLOW: OpenSpec · agent-skills · Claude Code · OpenCode
  • TOOLS: Linux · GNU · Docker · Neovim

Programming languages Python is the language I know best. I've used it professionally, and it's the home of my favorite area: machine learning. Rust is the one that excites me most right now. It's as fast as C, and its borrow checker makes code safer, which opens the door to systems programming and games. JavaScript and TypeScript came with two years of focused web development after my bachelor's degree. I pick up new frameworks and libraries quickly. PHP is the newest addition: I'm exploring it at the moment.

show as text

Programming languages

  • Python is the language I know best. I've used it professionally, and it's the home of my favorite area: machine learning.
  • Rust is the one that excites me most right now. It's as fast as C, and its borrow checker makes code safer, which opens the door to systems programming and games.
  • JavaScript and TypeScript came with two years of focused web development after my bachelor's degree. I pick up new frameworks and libraries quickly.
  • PHP is the newest addition: I'm exploring it at the moment.

Frontend htmx is my first choice. I love low-JS development: the server renders HTML, and htmx adds just the interactivity a page needs, with no build step and no client-side state to keep in sync. When a project really calls for a JavaScript framework, I reach for SvelteKit for its developer experience, or React for single-page apps. Tailwind CSS keeps the styling quick either way.

show as text

Frontend

htmx is my first choice. I love low-JS development: the server renders HTML, and htmx adds just the interactivity a page needs, with no build step and no client-side state to keep in sync. When a project really calls for a JavaScript framework, I reach for SvelteKit for its developer experience, or React for single-page apps. Tailwind CSS keeps the styling quick either way.

Mobile I build cross-platform mobile apps with React Native and Expo.

show as text

Mobile

I build cross-platform mobile apps with React Native and Expo.

Backend I build REST and GraphQL APIs, including authentication and authorization, with Zitadel as my identity provider. Building GraphQL APIs with NestJS is the part I enjoy most.

show as text

Backend

I build REST and GraphQL APIs, including authentication and authorization, with Zitadel as my identity provider. Building GraphQL APIs with NestJS is the part I enjoy most.

Databases I studied SQL and relational database design in depth during my degree, which is why PostgreSQL is my default. I've used MongoDB at work, and graph databases like Neo4j interest me for data science and social applications.

show as text

Databases

I studied SQL and relational database design in depth during my degree, which is why PostgreSQL is my default. I've used MongoDB at work, and graph databases like Neo4j interest me for data science and social applications.

Scraping Scraping was my first job, and I still love it. I use Scrapy for large crawls, Playwright and Selenium when a site needs a real browser, Patchright when it actively fights automation, and Browser Use when an AI agent has to find its own way through a site.

show as text

Scraping

Scraping was my first job, and I still love it. I use Scrapy for large crawls, Playwright and Selenium when a site needs a real browser, Patchright when it actively fights automation, and Browser Use when an AI agent has to find its own way through a site.

AI and machine learning I build LLM-powered applications with Claude, Gemini and OpenAI models, using LangChain and LangGraph to orchestrate agents and workflows. Deep learning is still what I enjoy most: stacking layers and watching the loss drop epoch after epoch never gets old.

show as text

AI and machine learning

I build LLM-powered applications with Claude, Gemini and OpenAI models, using LangChain and LangGraph to orchestrate agents and workflows. Deep learning is still what I enjoy most: stacking layers and watching the loss drop epoch after epoch never gets old.

Audio plugins I write audio plugins for music production in Rust, using nih-plug for the DSP and plugin plumbing and egui for the interface, and ship them as CLAP and VST3. Each plugin begins as one sentence about what it does. That sentence stays at the top of the design document, and I build out from it, adding features as I see fit. When a feature doesn't fit the sentence, it goes to a different plugin. I like controls that mean something physical. Corrosion asks how big the pipe is and how rusted. Once you know what a knob does to the object, you can stop reading the manual. There are no mode menus. Each plugin is one continuum, with the familiar sound as the default and the strange stuff a few turns away. Before anything is released, it passes automated tests, real-time safety checks (the audio thread never allocates memory) and the standard plugin validators. That doesn't make it bug-free, but it does catch the obvious crashes before you do. And Rust, of course, catches plenty more. Everything is free software under GPLv3. If you buy a build on Ko-fi, you're funding the next plugin and getting builds you can install straight away. In development These are at the concept stage: each has a PRD and a DSP spec, and each has to pass an offline Python prototype before any Rust gets written. Orrery: a reverb made of sound sources orbiting the listener, or a rotary speaker with forty rotors. Radius sets how far each source travels, in meters (0.30 m is a Leslie horn). Coherence sets how the orbits line up: locked pairs are a rotary speaker, evenly spread is a string ensemble, scattered is a granular cloud. Drift spreads their speeds across just intervals, from unison to a chord. Because the reverb tail is made of the same orbiting copies, the space itself rotates. Sideband: a ring modulator whose carrier follows the note you play. Ratio sets the carrier relative to that note: at simple ratios the sidebands land on just intervals, so a single note becomes a power chord or a triad; at 1 it's an octave fuzz; off the grid it's a bell. Density morphs the carrier from a sine to an impulse train, ending in a sample-rate crusher that tracks the note. Purity moves it between harmonizer and clangorous ring mod. Out of the box it's an octave fuzz. Undertow: an envelope-driven phaser and resonant filter on one modulation bus, with bipolar depth, so the filter can sweep up while the phaser sweeps down from the same note. Its flagship routing, Vortex, puts the phaser inside the filter's resonance loop, giving one filter several moving resonant peaks.

Corrosion

show as text

Audio plugins

I write audio plugins for music production in Rust, using nih-plug for the DSP and plugin plumbing and egui for the interface, and ship them as CLAP and VST3.

Each plugin begins as one sentence about what it does. That sentence stays at the top of the design document, and I build out from it, adding features as I see fit. When a feature doesn't fit the sentence, it goes to a different plugin.

I like controls that mean something physical. Corrosion asks how big the pipe is and how rusted. Once you know what a knob does to the object, you can stop reading the manual.

There are no mode menus. Each plugin is one continuum, with the familiar sound as the default and the strange stuff a few turns away.

Before anything is released, it passes automated tests, real-time safety checks (the audio thread never allocates memory) and the standard plugin validators. That doesn't make it bug-free, but it does catch the obvious crashes before you do. And Rust, of course, catches plenty more.

Everything is free software under GPLv3. If you buy a build on Ko-fi, you're funding the next plugin and getting builds you can install straight away.

In development

These are at the concept stage: each has a PRD and a DSP spec, and each has to pass an offline Python prototype before any Rust gets written.

  • Orrery: a reverb made of sound sources orbiting the listener, or a rotary speaker with forty rotors. Radius sets how far each source travels, in meters (0.30 m is a Leslie horn). Coherence sets how the orbits line up: locked pairs are a rotary speaker, evenly spread is a string ensemble, scattered is a granular cloud. Drift spreads their speeds across just intervals, from unison to a chord. Because the reverb tail is made of the same orbiting copies, the space itself rotates.
  • Sideband: a ring modulator whose carrier follows the note you play. Ratio sets the carrier relative to that note: at simple ratios the sidebands land on just intervals, so a single note becomes a power chord or a triad; at 1 it's an octave fuzz; off the grid it's a bell. Density morphs the carrier from a sine to an impulse train, ending in a sample-rate crusher that tracks the note. Purity moves it between harmonizer and clangorous ring mod. Out of the box it's an octave fuzz.
  • Undertow: an envelope-driven phaser and resonant filter on one modulation bus, with bipolar depth, so the filter can sweep up while the phaser sweeps down from the same note. Its flagship routing, Vortex, puts the phaser inside the filter's resonance loop, giving one filter several moving resonant peaks.

06 — setup

Setup — SYSTEM: CachyOS on a ThinkPad T480 · LUKS full-disk encryption; DESKTOP: niri (scrollable-tiling Wayland) + Noctalia shell · vim-style keys; TERMINAL: Alacritty + zsh (vi mode, starship); EDITORS: Neovim (native LSP, Treesitter, Telescope) · Doom Emacs · VSCodium; DEV: Docker · Postman · MySQL Workbench; MUSIC: Ardour · VCV Rack · yabridge; APPS: Obsidian · LibreOffice · GIMP; BACKUPS: Syncthing to a second PC

show as text
  • System: CachyOS on a ThinkPad T480 · LUKS full-disk encryption
  • Desktop: niri (scrollable-tiling Wayland) + Noctalia shell · vim-style keys
  • Terminal: Alacritty + zsh (vi mode, starship)
  • Editors: Neovim (native LSP, Treesitter, Telescope) · Doom Emacs · VSCodium
  • Dev: Docker · Postman · MySQL Workbench
  • Music: Ardour · VCV Rack · yabridge
  • Apps: Obsidian · LibreOffice · GIMP
  • Backups: Syncthing to a second PC

CachyOS on a ThinkPad T480, fully encrypted (LUKS), running the scrollable-tiling Wayland compositor niri with the Noctalia shell, keyboard-driven with vim-style keys. Configs and setup scripts are in my dotfiles. Linux is my main development environment, and I'm at home on the command line with tools like tar, rsync, grep, sed, gawk, xargs, parallel and screen. I use Neovim for its speed and extensibility, and Docker to run services and keep environments reproducible.

niri Noctalia

show as text

CachyOS on a ThinkPad T480, fully encrypted (LUKS), running the scrollable-tiling Wayland compositor niri with the Noctalia shell, keyboard-driven with vim-style keys. Configs and setup scripts are in my dotfiles.

Linux is my main development environment, and I'm at home on the command line with tools like tar, rsync, grep, sed, gawk, xargs, parallel and screen. I use Neovim for its speed and extensibility, and Docker to run services and keep environments reproducible.

07 — telemetry

GitHub stats: contributions, commits, pull requests, issues, reviews, public repos, stars and top languages, updated daily

Contribution activity graph for GerMP21

08 — contact

Have a project that needs another developer? Feel free to reach out.

show as text

Have a project that needs another developer? Feel free to reach out.

Now: building Omnisnap and Opencode-Hyperflow, writing plugin specs, exploring PHP

Pinned Loading

  1. Corrosion-VST Corrosion-VST Public

    Industrial physical-modeling instrument (VST3 + CLAP, Rust): bowed, struck, scraped and blown modal models of pipes, plates, chains and cables, with a post chain of drive, body, space and a diode c…

    Rust 2

  2. Omnisnap Omnisnap Public

    Element-level cross-browser layout diffs from the browsers you already have. Point it at a URL to see which elements render differently, the measured cause of each difference and which engine is at…

    Go 3

  3. DGI-WS_PersonaGetActEmpresarial-Proxy-Client DGI-WS_PersonaGetActEmpresarial-Proxy-Client Public

    A production-ready Node.js server that provides a modern, secure RESTful API for querying taxpayer information (RUC) from Uruguay's DGI SOAP web service.

    JavaScript 1

  4. mysql-split-import mysql-split-import Public

    Import a mysqldump file that is too large to import in one go.

    Python

  5. dotfiles dotfiles Public

    CachyOS + niri (Wayland) setup with a Tokyo Night theme, tested on a ThinkPad T480.

    Shell