Blog

Blog

Each article details the technical choices of a project: its architecture and the solutions chosen. They are written for a technical reader.

  • Technical article · myFenyx

    myFenyx: the architecture of a rewards application

    The technical choices of myFenyx, the internal rewards application of Fenyx Group: wallet kept by year, denormalised ranking, two-step exchange and sign-in by one-time code.

    • Flutter
    • PostgreSQL
    • Django

  • Technical article · Encheria

    Encheria: embedded geography, universal links and subscriptions

    The technical choices of Encheria, a mobile application devoted to judicial real-estate auctions: embedded geography, universal links, app store subscriptions reconciled on read.

    • Flutter
    • PostgreSQL
    • Spring Boot
    • nginx

  • Technical article · Sanu

    Sanu: access model, real time and verification

    The technical choices of Sanu, a management and point-of-sale system for retail in West Africa: access model, live channel and verification.

    • Flutter
    • PostgreSQL
    • Spring Boot
    • nginx
    • React

  • Technical article · Tontini

    Tontini: the seats, calendar and ledger of a tontine

    The technical choices of Tontini, a tontine bookkeeping application: seats reserved before the members arrive, a payout calendar rebuilt on every change, a ledger written on confirmation.

    • Flutter
    • PostgreSQL
    • Django

  • Technical article · Soccercup

    Soccercup: a tournament derived from an event log

    The technical choices of Soccercup, an application for managing amateur football tournaments: scores and standings derived from an event log, groups and knockout stages in a single table.

    • Flutter
    • PostgreSQL
    • Spring Boot

  • Technical article · Huitivi

    Huitivi: filter and radius search without a spatial database

    The technical choices of Huitivi, a prototype of a property listings application for Togo: search described by a single filter document, radius search without a spatial database, media reserved for subscribers.

    • Flutter
    • PostgreSQL
    • Django

  • Technical article · Locwind

    Locwind: the position at the centre of the map and local storage

    The technical choices of Locwind, an application that records named geographic positions: position taken at the centre of the map, location read only once, local storage.

    • Flutter

  • Technical article · Rentapp

    Rentapp: due dates, payments and phone sign-in

    The technical choices of Rentapp, a prototype rent payment application: due payments generated on read, a payment tied to its instrument, sign-in by phone, one-time code and PIN.

    • Flutter
    • PostgreSQL
    • Django

  • Technical article · Mooduo

    Mooduo: a mood journal kept by two, without accounts

    The technical choices of Mooduo, a prototype mood journal kept by two: pairing without an account, one row per couple and per hour, a WebSocket channel that carries only a signal.

    • Flutter
    • PostgreSQL
    • Django

  • Technical article · Plugin repository

    A Claude Code plugin repository organised by roles

    The technical choices of a repository of Claude Code plugins: separate roles for Spring, React and Flutter, a verifiable hand-off and a verdict that knows only two words.

    • Flutter
    • Spring Boot
    • React

  • Technical article · Flutter packages

    Three Flutter packages shared between applications

    The technical choices of three Flutter packages shared between applications: a generic bloc state, a sign-in grafted onto the host application's HTTP client, persisted settings.

    • Flutter

  • Technical article · Monitoring

    Monitoring: self-hosted GlitchTip and SonarQube

    The technical choices of two self-hosted services, GlitchTip for error tracking and SonarQube for code analysis: memory budget, secrets kept out of the logs, re-runnable deployment.

    • PostgreSQL
    • Docker
    • nginx

  • Technical article · Trading tools

    Trading tools: from a relay to a data pipeline

    The technical choices of a series of personal tools around MetaTrader 5: from a 124-line relay to a market-data pipeline, with idempotent writes, a measured broker clock and at-most-once commands.

    • PostgreSQL

  • Technical article · Deployment console

    A deployment console that calls the existing scripts

    The technical choices of the deployment console: a page that calls the delivery script each project already has, permissions denied by default and a risk named rather than hidden.

    • Docker

  • Technical article · Inoskera

    Inoskera: a brand guide written before the stylesheet

    The technical choices of the InosKera Group website: a brand specification written upstream of the stylesheet, two-level tokens for the dark theme, English copy written for its market.

  • Technical article · Iforla

    The Iforla site: delivery, local stack and enrolment module

    The technical choices of a language school's website on WordPress: delivery over FTP verified by hash, local stack realigned with production, custom-written enrolment module.

    • Docker
    • WordPress and PrestaShop

  • Technical article · Adanora

    PrestaShop shops: child theme, custom module and versioning

    The technical choices of two PrestaShop shops, one in service and the other left at the project stage: child theme, custom module and the choice of what to version in the tree of a CMS.

    • Docker
    • WordPress and PrestaShop

  • Story · myFenyx

    myFenyx: turning a manual HR process into a real application

    How myFenyx replaced, at Fenyx Group, a rewards scheme run by hand by human resources with a Django and Flutter application.

    • Flutter
    • Django