Selected work ↗   ·   Migration pipeline ↗

Thirteen years in client-facing operations taught me where software fails outside the demo.
I now use that experience to scope, build, verify, and hand over practical products.

_{01.1 / PYTHON · DOCUMENT INFRASTRUCTURE}

Deterministic conversion of Markdown, HTML, RST, XML, and PDF sources into GitBook-ready Markdown. The pipeline rewrites links, validates output, records content hashes, supports dry runs, and leaves machine-readable manifests and reports.

Evidence: 9 tests · 89.42% coverage · Python 3.11–3.13 CI · Ruff · package build · gitleaks clean

_{01.2 / NEXT.JS · POSTGRESQL · PRODUCT}

A Croatian pet-services marketplace with authentication, bookings, realtime messaging, responsive interfaces, and operational tooling. This is the primary product focus and the project moving toward real operation.

Product surface: marketplace discovery · sitter workflows · booking flows · messaging · operational controls

_{01.3 / NEXT.JS · MARINA OPERATIONS · PRODUCT}

A fixture-backed operations desk that turns vessel readiness, incidents, ownership, and departures into a clear daily launch workflow across marina bases and desk dates.

Workflow proof: readiness classification · incident triage · owner assignment · departure board · multi-base/day scenario controls

PetPark Mobile → — Expo and React Native companion application carrying the PetPark product language from web to mobile.

Midnight Consent Demo → — Tested research implementation for exposing a verified fact without exposing its underlying private record; clearly bounded as a mock and Compact sketch, not production cryptography.

Operations & hospitality — MarinaFlow · Hotel Fortunata

Learning & daily practice — Učiteljica AI · Zora

Climate & connected systems — Solarna mjera · Smart Hive Observatory

Guided journeys & configuration — Dental Treatment Journey · Forma 32

PRODUCT ENGINEERING — TypeScript React Next.js React Native

SYSTEMS & DATA — Python REST APIs Webhooks Supabase PostgreSQL

DELIVERY EVIDENCE — Pytest Vitest Playwright CI Dry runs Decision logs

I am most useful where the requirement is still ambiguous, the workflow crosses people and systems, and “works on my machine” is not a sufficient definition of done.

01 / Outcome — define the real result and its failure conditions.
02 / Contract — make boundaries, data, ownership, and acceptance explicit.
03 / Build — complete the smallest useful path through UI, API, and data.
04 / Prove — test behavior, edge cases, operational constraints, and release state.
05 / Handover — leave decisions, evidence, and repeatable tooling behind.

Rijeka, Croatia · Remote across European time zones · Croatian / English / Italian

For migration engineering, integrations, product delivery, or workflow automation,
start with the document migration pipeline or review the selected work.