Architecte du Réel

Memory

Without memory, no future. A system without memory repeats its mistakes. Documentation is an investment, not a constraint. ADR, C4 models, docs-as-code, post-mortems, runbooks. Technical, organizational and human memory — the heart of tomorrow.

« Memory is the heart of tomorrow. »

A system without memory repeats its mistakes. Memory — technical, organizational, human — is what distinguishes a mature system from a fragile one.

It does not improve, does not learn, condemned to eternally repeat the same errors. Documentation reduces diagnostic time, facilitates onboarding, preserves knowledge.

Methodology: Architecture Decision Records (ADR), C4 diagrams, docs-as-code with Markdown in the repo. Blameless post-mortems, tested runbooks, executable runbooks. Every PR includes documentation updates.

Three forms of memory

Technical memory

Logs, documentation, change history. A system's ability to tell its own story.

Structured logging, distributed tracing, temporal metrics. Every event is dated, contextualized, queryable.

ELK stack, Prometheus, Grafana. Log rotation with archiving. Immutable audit trail. Time-series database for metrics. Everything versioned, everything reproducible.

Organizational memory

Procedures, post-mortems, retrospectives. What the organization learns from its successes and failures.

Every incident becomes an improvement opportunity. Post-mortems are blameless, system-oriented, not individual-oriented.

Post-mortem template: timeline, detection, remediation, contributing factors, corrective actions. Monthly incident review. Searchable knowledge base accessible to all.

Human memory

Team experience, knowledge transfer. No system should depend on a single person.

Pair programming, mentoring, collaborative documentation. Knowledge must circulate, not remain siloed.

Structured onboarding: technical checklist, designated mentor, documented first tasks. Role rotation (bus factor). Continuous training budgeted.

Documentation as investment

Documentation is not a constraint, it is an investment. It reduces diagnostic time, facilitates onboarding, preserves critical knowledge.

Fundamental principle

« If it is not documented, it does not exist. »
A system that is understood is a system that is mastered.

Memory of completed missions

What has been built, measured and documented. Without memory, no future.

2022 — 2026

Web cybersecurity audits

Application security audit missions according to OWASP WSTG v4.2 and CVSS 3.1. OSINT reconnaissance, passive and active penetration testing, GDPR compliance. Deliverables: prioritized technical reports, executive summaries, prioritized remediation plans.

2000 — 2012

Portsdéfrance.com — Private cloud before its time

Web hosting platform based in London. 130+ websites, 500+ clients. Clustering and high availability. Nautical clients: 2 Vendée Globe, 3 Jules Verne, 3 Transat Jacques-Vabre, 2 Route du Rhum.

1997 — 2000

France Télécom — National Control Center

Management of 5,000+ workstations and 100+ servers across 6 sites. 24/7/365 on-call duty. Clusters, security, high availability. National critical infrastructure.

Reference documents

The 3 latest reports and investigations. See all factual documents →

Recommended practices