How I work

Method

I use AI every day, at every stage of a project. It helps me research, structure, write code and review faster. The need, the choices and the release remain my job.

Sheet M.1

My tools

Cédric
  • I define the need and choose the approach
  • I provide the context
  • I approve, integrate and deploy
  • I maintain
Claude
  • Development and code
  • Implementation
  • Engineering
ChatGPT
  • Structuring and architecture
  • Roadmap and product thinking
  • Organisation
  • Regulatory and legal research, not legal advice
Codex
  • Engineering and code on some projects
  • Technical review on some projects
Gemini
  • Research, information, analysis and exploration
Cédricneed · contextDevelopmentClaudeReviewChatGPT or CodexTestslint · types · testsCédricsign-off · releaseneeds work: back to development
Sheet M.2

How my method evolved

  1. Dec. 2025First exchanges

    I start coding with Claude Code on the ND Technology website. Ask, correct, try again.

  2. Apr. 2026Handoff notes

    I write handoff notes to keep context from one session to the next: where the project stands, what is left, known pitfalls.

  3. Aug. 2026The plan first

    I approve the plan before any code, then move in phases: each phase is tested before the next one.

  4. Sept. 2026Review

    One AI writes the code, another reviews it in the pull request, the tests pass, then I approve.

  5. Oct. 2026Several AIs, one project

    On SILVORYX, each AI has its own role and branch, and the big decisions are written down before coding.

Sheet M.3

Three principles

  1. Nothing goes to production without my approval.
  2. Important steps are reviewed and tested.
  3. Original projects and sensitive data stay protected.
Sheet M.4

Infrastructure

I use two hosting models depending on the project: my own server behind Cloudflare Tunnel for my companies, and VPS servers I administer for the companies I work with.
VisitorHTTPSCloudflareDNS · TLS · cachetunnelMY UBUNTU SERVER · NO INBOUND PORT OPENcloudflaredsystemd · outboundNginxlocal onlyDOCKER CONTAINERSGroupAcademySoftwareHubBlogAIInvestCMSUmamiPostgreSQLinternal networkBackupsdaily dumps · media · restore
My server
Ubuntu Server 24.04, Docker Compose, local-only Nginx, a cloudflared tunnel, PostgreSQL on an internal network, Umami, Nextcloud. It hosts TICAMAC Group, ND Technology and this portfolio.
Client servers
Ubuntu 24.04, Nginx, PocketBase as a service, security headers. They host the websites and intranets of the companies I work with.
Delivery
GitHub Actions, pre-deployment checks, a backup before each release, health checks, release notes.
Backups
Daily backups and restore scripts kept with the code.
Sheet M.5

Quality and visibility

  • Tests: 48 Playwright tests on ND Technology and automated security tests on the TICAMAC Group CMS.
  • Acceptance testing: test plans, defect lists and role-by-role checks on the intranets.
  • Releases: release notes and explained fixes.
  • SEO: server-rendered pages, metadata, sitemaps, structured data, IndexNow, Google Search Console, Bing Webmaster Tools and Google Business Profile.
  • Analytics: Umami, which I host myself, cookieless.
Sheet M.6

And this portfolio?

I designed and directed this portfolio, and had it implemented with Claude Code, in the same AI-assisted development workflow I use for my other projects. The screenshots date from 6 October 2026, and older versions of my sites were relaunched from my archives.