Les critiques:

En plus, cela fait tache d’huile. La DINUM fait sa Suite, mais on voit aussi les territoriales, la GIP, l’ANCT qui sont en train de créer des suites collaboratives.

L’État paie deux fois. Il subventionne la R&D des éditeurs privés avec France 2030 ou le Crédit Impôt Recherche. Puis il finance une équipe interne pour développer une solution concurrente. C’est un gaspillage de ressources.

C’est malgré tout une garantie de souveraineté de ne pas dépendre d’un vendeur. Et je vois mal des entreprises françaises concurrentes accepter qu’une seule d’entre elles remporte le marché à vie. Soyons honnêtes, aucune n’accepterait.

Visio et LaSuite ne sont pas conçus comme des offres commerciales : ce sont des communs numériques pour des besoins génériques, interministériels, avec des exigences de sécurité et d’interopérabilité particulières

Le partenariat privé est utile pour l'hébergement qualifié, la sécurité, l'intégration, l'accompagnement au changement, et le développement de fonctionnalités spécifiques.

Benefits: stability and failure.

t’s more of a target than a strict rule. Sometimes you have to pull overtime. Sometimes you should get out early.

And while this is certainly a positive thing in many ways, it puts us in a riskier position when it comes to communicating our work.

Why? Because the only thing more dangerous to a design system’s funding case than a lack of understanding of what it is, is a false understanding of what it is. Particularly when that false understanding is often built on a collection of common myths that have elbowed their way, without nuance, into the psyche of our organisations’ leaders. Myths like:

• 10x faster
• don't need a design system team
• design system eradicate duplication effort
• bake accessibility into components and the job is done

Here's the thing: 99% of companies don't need them. The top 1% have tens of millions of users and a large engineering team to match.

The fun thing about Postgres is there is already an extension for that: PostGIS, Full-text search, JSONB, TimescaleDB, pgvectorm, and many for AI

Each database add hidden costs: backup strategy, monitoring dashboards, seceurity patches, on-call runbooks, failover testing.

SLA math: Three systems at 99.9% uptime each = 99.7% combined

Le media couvre de Bordeaux et ses environs.

La grappe est un site collaboratif, et indépendant des partis politiques, organes de presse et syndicats, de Bordeaux & alentours.

Il fait partie du reseaumutu.info.

(via https://contre-attaque.net/2026/02/07/la-grappe-le-media-autonome-qui-secoue-bordeaux-et-sa-region/)

The breakpoint is used for mobile, but appears inconvenient for tablet or half-screen windows.

Solutions:

• having more breakpoints in between
• design with container queries in mind
• make the design dynamic at its core, meaning that it can change based on the number of items
• leverage well supported features like Grid and Flex

appearance: base-select, so it's too early yet.

<details>  
  <summary class="video-summary">
    <!-- Video Placeholder Image -->
    <img src="https://lab.n8d.studio/htwoo/htwoo-core/images/videos/big-bug-bunny.webp" class="video-thumbnail">
    <!-- Play Button -->
    <svg class="video-playicon" data-id="icon-play-filled" viewBox="0 0 32 32" data-icontype="filled"><path d="m11.167 5.608 16.278 8.47a2.169 2.169 0 0 1 .011 3.838l-.012.006-16.278 8.47a2.167 2.167 0 0 1-3.167-1.922V7.529a2.167 2.167 0 0 1 3.047-1.981l-.014-.005.134.065z"></path></svg>
  </summary>

  <!-- we'll get here... -->
</details>

When a visitor decides to watch the video and clicks on the thumbnail, the open attribute will be placed by the browser on the details attribute, which means the video summary can be hidden.

1. Event-Driven Architecture (EDA)

Problèmes résolu:

• timeout si un service est lent
• 1 service down = toute la chaîne bloquée
• temps de réponse imprévisible

Pièges à éviter:

1. Event explosion
2. Debugging de l'enfer
3. Eventual Consistency mal gérée
4. Cohérence transactionnelle

2. API-First & API Gateway pattern

API-First : Concevoir l'API avant d'implémenter le service
API Gateway : Point d'entrée unique qui orchestre, sécurisé, et monitore les APIs (et Backend for Frontend)

Pièges à éviter:

• moins de 5 api et un seul frontend
• communication interne uniquement
• latence critique

3. CQRS + Event Sourcing

Command Query Responsibility Segregation: séparer les modèles de lectures et d'écritures; deux bases de données différentes optimisées pour leur usage.
Event Sourcing : Au lieu de stocker l'état actuel, on stocke tous les événements L'état actuel est reconstruit en rejouant les événements.

Cas d'usage: Performance, audit et compliance, analytics temps réel

Pièges à éviter: complexitée surévaluée, eventual consistency, gestion de la mimgration de schéma

4. Saga Pattern

He creates beautiful illustrations. They are related to solarpunk.

For the last few years I witnessed many well-meaning writers and academics try to write about a better climate future - be it under a name of Solarpunk or any other - and struggle to find art illustrating their work.

The same content can create clarity for one person and confusion, stress, or exclusion for another, without changing a single word.

Accessibility is a must. Here are some examples

1. When color disappears completely

• Buttons that look clickable even without color
• Links that are underlined or styled consistently
• Hierarchy created through spacing, borders, size, and structure

2. When nice colors choices stop working

• Contrast that survives more than one type of vision
• Less reliance on subtle color differences
• Clear affordances that don’t depend on perfect perception

3. The most color blindness is ignored

• Meaning that survives without red or green
• Icons, labels, or position reinforcing importance
• Safer decisions and faster understanding

4. When text becomes slightly blurry

• Text that stays readable when slightly blurred
• Comfortable line height and spacing
• Zoom that doesn’t punish the layout

5. When you can only see a small part of the screen

• Clear headings that anchor the page#
• Logical reading order
• Visible focus states that guide navigation

7. When letters won't stay still (dyslexia)

• predictable layouts
• plain, calm language
• no uneccessary visual tricks

8. When language stops making sense

• plain language
• clear labels
• information that unfolds gradually, not all at once

1.There are three states of being. Not knowing, action and completion.00

2. Accept that everything is a draft. It helps to get it done.
3. There is no editing stage.
4. Pretending you know what you’re doing is almost the same as knowing what you are doing, so just 5. Accept that you know what you’re doing even if you don’t and do it.
5. Banish procrastination. If you wait more than a week to get an idea done, abandon it.
6. The point of being done is not to finish but to get other things done.
7. Once you’re done you can throw it away.
8. Laugh at perfection. It’s boring and keeps you from being done.
9. People without dirty hands are wrong. Doing something makes you right.
10. Failure counts as done. So do mistakes.
11. Destruction is a variant of done.
12. If you have an idea and publish it on the internet, that counts as a ghost of done.
13. Done is the engine of more.

There is also an illustration for it

1. unsystematic
2. valid
3. semantic
4. Accessible
5. Required-only
6. hyper-optimized