Self-taught developer in Paris. I work mostly on the parts of a system nobody sees — schemas, access rules, and the tests that keep them honest.
VYVE (private) — a marketplace, since May 2026. Postgres with row-level security throughout, an escrow payment flow, and the tax structure that has to match it. Around 340 commits so far. The hardest part turned out not to be the code: it was deciding who is allowed to see what, and then proving the database actually enforces it rather than assuming the application layer will.
forge — a pipeline that reads six engineering feeds every morning, ranks what it finds by cross-source corroboration, and turns the survivors into project specifications. The interesting part is the quality gate: it counts assertions, checks how many of them compare a literal to itself, and rejects the build if too many do. It also refuses to publish anything on its own — runs end at a review queue.
arielb57.github.io — my portfolio and activity dashboard. Static, no framework, no runtime dependencies, rebuilt from the GitHub API once a day.
I write tests that can fail. I would rather ship something small and finished than something large and nearly working, and I try to write down the limitations before someone else finds them.
All of this was built with AI assistance, and I would rather say so up front than have someone work it out. Some repositories were produced end to end by forge from a specification and reviewed before publication — those carry a .forge.json manifest and are marked on my portfolio. The rest I built directly, deciding and correcting as I went. What does not vary is that I read everything before it goes public: a repository I cannot explain is not worth having.
Applying to university next year, and using the time until then to build things that are worth showing rather than things that are easy to count.