OPERATOR PROFILE

The human behind @frogwebp: identity, trajectory, method, and capabilities. Same mind that writes the systems and the growth logs.

OPERATOR: FRG-01
STATUS: ● BUILDING
SINCE: 2021
// MODULE_01 — IDENTITY

IDENTITY

I build data systems, and I write about everything around them: the architecture, the failures, the long detours, and what each one teaches me. I've been documenting in public since 2021, before I had anything technical to show; it started as a way to make sense of things, and became the way I work. The conviction never changed: the process is worth showing, not just the result.

I'm two things at once, and I've stopped treating that as a problem. There's the engineer, the one who cares whether a materialized view refreshes incrementally, whether a pipeline is idempotent, whether a partition is visible before it's queried. And there's the reader, the one who works through Designing Data-Intensive Applications with the same seriousness as a book about meaning. The systems are where those two finally meet.

Python PostgreSQL Apache Airflow Redpanda RisingWave ChromaDB Docker Kubernetes
// MODULE_02 — TRAJECTORY

TRAJECTORY

I'm working toward a professional data engineering role, specifically the high-velocity end: real-time streaming, observability pipelines, data architecture that has to hold up under load. The path is deliberate. I'm completing the IBM Data Engineering Professional Certificate, and around it I'm building a production-grade portfolio in public, not toy projects, but systems with tests, CI, and the kind of documentation you'd want to inherit.

// SYSTEM 01
SPECTRUM
Self-hosted analytics warehouse. Star schema, funnels, cohort retention. 32/32 tests.
VIEW CODEX →
// SYSTEM 02
PHRONIS
Real-time circuit breaking for AI agents. Detects runaway behaviour in under 500ms.
VIEW CODEX →
// SYSTEM 03
CONTEXTFLOW
Semantic search over multilingual PDFs. Local embeddings, sub-2s query. 60/60 tests.
VIEW CODEX →
// MODULE_03 — METHOD

METHOD

Two ideas run underneath all of it. The first is "show your work," Austin Kleon's argument that creativity isn't a lone genius but a scene you join by working in the open. The second is deep work: the understanding I'm after only comes from long, uninterrupted hours with one hard thing, and the willingness to stay confused longer than is comfortable.

Which is why the writing here comes in two registers, on purpose. System and concept posts are clinical, operational records, and they read like it. Growth posts are warmer, more reflective, because the human side of building alone is part of the work too. Same person, two registers. If you move between them and feel one mind underneath, that's the whole point.

// MODULE_04 — CAPABILITIES

CAPABILITIES

LANGUAGE_PROCESSING Mandarin Chinese, in active acquisition 130-DAY STREAK · daily practice
TECHNICAL_FLUENCY English, C2 (full professional) EF SET certified · primary working language
CORE_LITERATURE Designing Data-Intensive Applications by Kleppmann Show Your Work by Austin Kleon technical depth + build-in-public ethos, read with equal weight
DEPLOYMENT_MODEL Self-hosted infrastructure PostgreSQL · Redpanda · RisingWave · ChromaDB · Airflow · Podman
OPERATING_MODE Solo · freelance · building in public deep work + show-your-work, since 2021

I don't go narrow. The connections between distant things are where I actually come alive, and the restlessness that made my path here crooked is the same thing that makes me good at this. If you're somewhere on your own detour, unsure the wandering counts: it counts. Mine led here, and here is the first place the whole of me has had something to do.

// FOLLOW THE WORK

New build logs, engineering concepts, and process notes, documented as they happen. Read the Codex, browse the Log, or find me across the platforms.