How I work

Ecommerce and business-platform developer.

I build systems that sell or that run an operation, I keep them in production, and I keep changing them without ever taking the service down.

  1. Understand the existing system and its constraints quickly.
  2. Make decisions with the right people and the right scope.
  3. Ship without losing the readability of the system.
Order

Nonprofit salaried — 2020-2021

Aremedia

A salaried role in public health, in 2020. I built a self-hosted reporting tool for field teams and the association's public website.

The people using it worked outside, often in one-off encounters, and the data was about health. That ruled out anything that needed a stable connection, a login they would forget, or a service that keeps the answers on its own servers.

Read more

So I set up a self-hosted LimeSurvey they could use in the field, and built the public site aremedia.org on WordPress.

Full-stack developer & technical lead — 2021-2026

Jewely Ecommerce

Custom ecommerce CMS for jewellers and watch retailers. One Laravel / Vue codebase shared by several houses, a PIM (the central product database), and connectors to ERPs and marketing catalogs.

Five years at Jewely (then Flippad), from September 2021 to the summer of 2026, in charge of the client houses' ecommerce sites: uptime, maintenance, new features, requests from brands. My clients on my own; the ERP and the PIM had their own leads, whom I worked with.

Read more
  • 2025: a jeweller's site finished, then a pre-owned watch shop built alone on that base, from an agency's design. Technical choices and the client relationship: the case study.
  • 2026: that base becomes a CMS shared by several houses: a feature built once, rolled out house by house, each on its own instance. One CMS for several houses, audit before you merge.
  • Rolex: the Bespoke space (new watches) built and put online at three client houses; Certified Pre-Owned at one of them, the only one to offer it.
  • Product data: the first Python scripts scraping brand sites (sitemap, then product page), later built into the PIM, which now feeds more than 20,000 entries with images and videos. The ERP → PIM → shops connectors: automatic product creation, Google Merchant Center (SKU, MPN, second-hand and refurbished), Meta catalogue. Product-data flows between ERP, PIM and shops, a neutral PIM, one transformation per shop.
  • Marketing and measurement: dynamic Meta campaigns for brands such as Tudor and Repossi; conversion indicators, Google's and Microsoft's Consent Mode v2, search and sharing previews. Consent orchestration, technical SEO and structured data.
  • Handover: a ticketing tool for support and an ERP documentation fed from a spreadsheet, scoped then handed to the teams.

Cross-cutting DevOps — 2024-2026

Infrastructure

Jewely's deployment environment: Docker Swarm on AWS, an nginx load balancer, automatic deployment through ECR, EventBridge, Lambda and SSM.

This environment was set up by Jewely's AWS server lead. I was its main user, and I took part in improving it.

Read more

A full disk stopped the new version from starting. Swarm went back to the old one, and the deployment was still reported as successful. I analysed the incident, then took part in the reliability work: comparing the image in production with the expected one, detecting rollbacks, cleaning the servers before their disks fill up. I wrote the deployment agent that runs these checks.

PrestaShop developer, for Jewely — 2024-2026

PrestaShop store

PrestaShop shop of a jeweller and watch retailer. I led the migration from PrestaShop 1.7 to PrestaShop 8 and evolved the connector with the Odeis ERP.

I led the migration from PrestaShop 1.7 to PrestaShop 8: I ported the overrides, the theme and the modules, and adapted them to what version 8 brings.

Read more

On the site, I added the English version, Google Consent Mode v2, reCAPTCHA on forms and the Rolex space, and improved accessibility and speed.

I evolved the connector with the Odeis ERP, which updates prices and stock several times a day, and took part in the product sync with the Jewely PIM. Missing products are created inactive, then completed in Jewely before they go online.

Built for the Jewely client houses

Four jewellers and watch retailers, clients of Jewely. For now two of them run on the shared CMS I built. I also built the Rolex Bespoke space, which presents new watches, and put it online for three of them, then the Rolex Certified Pre-Owned space for one of them.

  • 5years at Jewely
  • 20,000+product entries enriched
  • 4client houses

Self-employed, research and development — 2026, in progress

In-house Tools & AI

A business platform where an open language model runs on site, with no network egress, as a controlled capability serving an organisation's files, tasks and validations. A Laravel MVP against llama.cpp, and guarantees measured before they are promised.

Started on 18 October 2026. A day of measurements first: two open 8-billion-parameter models (Qwen3-8B to extract, Ministral 3 8B to draft) on an 8 GB card, thirteen experiments, each with a written criterion. The model is not a security boundary: trapped documents make both models give way in free-text summary, and a closed output sheet makes them hold 60 times out of 60.

Read more

Then the product's first workflow, in Laravel, built and measured on 19 October: an inference gateway that picks the model by role, refuses before calling (pause, quota, length, one call at a time), logs without content; a form filter and provenance checks on dates, names and references; a file resumed end to end (sheets, closed briefing, tasks created at review) in 6 to 7 seconds, a letter from a template, an email sheet; administration, audit log, consumption, operations scripts; 307 tests without a real call. The code stays private; the method and the measurements are public: the case study, the article.

For whom: organisations that handle documents about people and do not want them to leave. The test ground is fictional and marked as such; the first real pilot is still to be found.

Self-employed, sole technical lead — 2026

DispaTech

A towing-dispatch platform, born of a home-repair business and turned into a white-label product. I was its only technical person, from design to production.

Self-employed and the project's only technical person: I held the tech lead's role and the developer's at once. Every technical decision was mine, from the architecture to the hosting, and I wrote the software's licence.

Read more

Moving from subcontracting to partnership changed the business model: knowing who invoices whom, computing the commission in one place, handling VAT correctly. That is what the linked article tells.

A very formative experience: deciding alone, holding the course, and shipping a product that now runs white-labelled, with a public demo and a published licence.

Volunteer mission for an artist — 2026

florianrosinski.fr

The portfolio of Florian Rosinski, artist and researcher in communication, then the site of his project Un art voulu voyant, and astralmanach, the library that came out of it.

A volunteer mission, under his art direction: his portfolio first, then Un art voulu voyant, the site of his research and art project, with Observations, a printable sheet of the sky of a date, an hour and a place.

Read more

astralmanach was born in that project: the sky calculation of Observations, released as a public library on npm, with an API and three tools, so that the project lasts without me.

Coming at the same place: the tool that extracts hands from videos, which will have its own library, private and licensed.

Decisions

Architecture decisions, written down.

Notes on choices made at Jewely: what I measured, what I ruled out, and what it cost.

Lots

Projects

Projects I worked on. Open the ones that have an address.

  1. Lot 01 · Library, API, tools

    astralmanach

    The sky of a date, a time and a place, as data. Born inside UAVV.

    • On npm, MIT licence, ESM and types.
    • Public read-only API: OpenAPI, Postman, 34 sources.
    • Three tools: birth chart, the sky of a date, a certificate in sentences.
    • Tests, documentation, releases published with provenance.

    What I did Everything, from the first calculation to the release.

  2. Lot 02 · Site, art project

    Un art voulu voyant

    A project by Florian Rosinski about what we read in signs.

    • Observations: a printable plate of the sky for a date, a time and a place.
    • Découpes: articles where hands taken from social networks veil the text, then return it as you read.
    • A private workshop that prepares the hands. Exports as image or vector.

    What I did Development and integration, on Florian's artistic direction.

  3. Lot 03 · Product, white label

    DispaTech

    My towing-dispatch platform, offered under licence and white-labelled, with a public demo you enter in one click per role.

    • A job in five computed phases, from acceptance to the archive.
    • The technician's flow on a phone, in fifteen steps: photos, quote, certificate, report.
    • PDF documents signed on screen, and one instance per brand configured without touching the code.
    • Fictional data, reset every night.

    What I did All of the design and the development, the production and the licence.

  4. Lot 04 · Platform, self-hosted AI

    In-house Tools & AI

    An in-house AI, at your place, for you: open models that run on site, behind a filter, closed outputs and a human review. In progress since 18 October 2026.

    • Two open 8-billion-parameter models on an 8 GB card, one loaded at a time.
    • Closed sheets: 60 trapped documents out of 60 resisted, 72 out of 72 after the filter, replayed against the code on 19 October 2026.
    • The provenance of dates, names and references checked by the application, not asked of the model.
    • A file resumed in 6 to 7 s and 0.2 Wh; a log without content; quotas and a pause button.

    What I did Research, measurements, design and development, alone. Private code, public method.

Trajectory

  • Commerce and product data

    I keep catalog, stock, media, and URLs agreeing with each other across an ERP, a PIM, and a shop — currently for more than 20,000 products.

  • Laravel delivery

    I work on Laravel platforms that are already serving customers, which means shipping changes without taking the shop down to do it.

  • Writing decisions down

    When I choose between two approaches I write down which one and why, so the next person does not have to guess or ask me.

Strengths

  • Proposals, not just tickets

    I don't wait to be asked: I come with a proposal, an alternative and what each one costs, then we decide together.

  • Front end and design

    Interface challenges please me as much as the machinery: typography, motion, accessibility, a page that holds on every screen.

  • Network and infrastructure culture

    DNS, TLS, reverse proxies, containers: I know where a request goes and what slows it down, from the browser to the database.

  • Between disciplines

    Product data, search, privacy, integrations between business tools: I talk to each trade in its own terms.

Focus areas

  • Laravel in production

    Evolving Laravel platforms that serve customers every day, in stages, without interrupting the service.

  • Technical SEO and information architecture

    URLs, metadata, structured data, and public content logic.

  • Consent and analytics

    Pixels, data layers, and analytics handled inside a privacy-aware frame.

References

Case studies and notes to go deeper.

An archive for more precise cases: constrained nonprofit tooling, data flow between ERP, PIM, and commerce, web formats, sitemaps, robots.txt, and delivery quality.

The Outils & IA internes dashboard on fictional data: three tasks due within seven days, eight documents to read, no record waiting for review
Case studyOctober 2026Own product, in progress

In-house Tools & AI: a self-hosted AI, at your place, for you

A business platform where an open language model runs on site, with no network egress, behind a filter, closed outputs, provenance checks and a human review. First workflow built and measured on 19 October 2026: a file resumed end to end in Laravel against llama.cpp.

  • Laravel 13
  • PHP 8.4
  • SQLite
  • llama.cpp
The dispatch dashboard of the DispaTech demo: jobs in progress, to handle and closed, and how the jobs split across phases, on fictional data
Case studyOctober 2026Own product

DispaTech: a towing-dispatch platform, white-labelled

My towing-dispatch platform, turned into a white-label product: a demo you enter in one click per role, fictional data reset every night, a published licence.

  • Node 24
  • Express 5
  • Prisma 7
  • PostgreSQL

AvailableRole or mission · Nancy, Paris, remote

Available for a position or a mission.

A short message is enough: context, timing, goal.