HELLO, MY NAME IS

LES.

FULLSTACK ENGINEERDESIGNERAI ORCHESTRATOR
NO HANDOFFS

FULLSTACKENGINEERDESIGNERAI ORCHESTRATOR

Frontend, backend, DevOps. I run what I ship.

GRAPH ENGINEERINGDEPLOYED CLOUD AGENTSAI PHOTO & VIDEO GENERATIONLOOP ENGINEERINGEVAL HARNESSHARNESS DEVELOPMENTINTEGRATED ANALYTICS PLATFORMMODEL CONTEXT PROTOCOL

RECENT
WORK

©2026 / 001

HFS2S

PRODUCT / AI / INFRASTRUCTURE

A private workspace that turns real workflows into tested, shareable apps — without pretending the engineer is optional.

©2026 / 002

TASTE LAB

PRODUCT / UX / AGENTIC AI

Find something worth cooking, plan the week, and get the groceries — without turning dinner into project management.

©2026 / 003

COCOVRON

BRAND / EDITORIAL / ART DIRECTION

A cinematic design exercise that gives single-origin coconut sugar the editorial treatment usually reserved for wine.

©2026 / 004

PROTOCOL

PERFORMANCE / HEALTH / PRODUCT

Training, fuel, labs, recovery, and protocols calibrated to what you are actually training for — in one daily system.

©2026 / 005

SERYOSO FIT

MEMBERSHIP / OPERATIONS / DESIGN

A HIIT membership app that keeps bookings, guest passes, QR check-ins, and the front desk out of each other’s way.

©2026 / 006

FITPACT

FITNESS / ACCOUNTABILITY / PRODUCT

A fixed-term fitness and nutrition pact for two people: pick a term, keep separate lanes, and finish together without turning it into a leaderboard.

ANTI–VIBE CODE.PRO–AGENTICENGINEERING.

Agents get scoped work, real tools, eval harnesses, observability, security boundaries, and review. A human stays accountable.

Les Echem in a design studio
LES ECHEM / BCN / 2026

FOUR RULES FOR
RUNNING AGENTS

[01]

Scope before speed.

Give the work edges. Make success inspectable.

[02]

Guardrails in code.

CLAUDE.md is a suggestion. Schemas, hooks and permission boundaries are the rule.

[03]

Observability by default.

Traces, token cost, replayable runs — instrumented up front, not after the incident.

[04]

Keep a human owner.

Accountability does not get delegated.

FIFTEEN YEARS.
THIRTY APPS.
ONE PRACTICE.

Where each of those comes from, and what it changes once the build starts.

01

30 apps shipped in 2026.

AI workspaces, food systems, membership operations, performance products, and editorial commerce — running software, not prototypes.

WHY IT MATTERS

Range and build speed without prototype theatre. The systems are tested, used, and owned.

02

15 years across engineering and design.

Product strategy, interaction design, frontend, backend, infrastructure, and production operations held in one practice.

WHY IT MATTERS

A decision can travel from interface to infrastructure without losing its intent in a handoff.

03

Fortune 100 work, delivered in production.

Shipped inside real stakeholder, security, reliability, governance, and scale constraints.

WHY IT MATTERS

The practice holds when the stakes are higher than a portfolio launch and failure has consequences.

04

Award-winning design and photography.

Photography published in Vogue, Architectural Digest and Bon Appétit; design work awarded by Graphic Design USA.

WHY IT MATTERS

Taste becomes a product capability: hierarchy, restraint, and the confidence to cut what does not belong.

The rules, the red lines, the thing that isn’t working yet — hfs2s turns it into a working app.

Built in a private workspace, tested in a real browser, and ready to share. Private beta — a few new builds at a time.

START BUILDING ON HFS2SOPENS HFS2S.APP