{
  "version": "1.0",
  "schema": "https://entitymap.org/spec/v1.0",
  "publisher": {
    "name": "NoBullshit Tech-Lead",
    "url": "https://getnobullshit.com"
  },
  "generated": "2026-10-16T15:20:33Z",
  "profile": "core",
  "verificationStatus": "generator-draft",
  "entities": [
    {
      "entityId": "e_brand",
      "@type": "Organization",
      "name": "NoBullshit Tech-Lead",
      "alternateName": "NoBullshit",
      "description": "Marque éditoriale de FGRibreau SARL. Elle publie le livre NoBullshit Tech-Lead et, sur getnobullshit.com, ses 60 principes, des guides et un glossaire destinés aux développeurs, Tech-Leads, architectes et CTO.",
      "url": "https://getnobullshit.com",
      "hasChunks": [
        {
          "chunkId": "e_brand__fr_1",
          "text": "60 principes fondamentaux pour gérer sa dette technique, livrer sans stress, tenir la production et bâtir une organisation efficace — du développeur au CTO.",
          "sourceUrl": "https://getnobullshit.com/fr/",
          "pageTitle": "NoBullshit Tech-Lead : 60 principes pour Tech-Lead et CTO",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_brand__en_2",
          "text": "60 core principles to handle technical debt, ship without stress, keep production healthy and build an effective organization — from developer to CTO.",
          "sourceUrl": "https://getnobullshit.com/en/",
          "pageTitle": "NoBullshit Tech-Lead: 60 principles for tech leads and CTOs",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_author",
      "@type": "Person",
      "name": "François-Guillaume Ribreau",
      "description": "Full Stack CPTO et auteur du livre NoBullshit Tech-Lead. Il a passé quinze ans à architecturer, construire et réparer des systèmes d’information, de la startup au grand compte, et a fondé ou cofondé Cloud-IAM, Netir, Image-Charts et Redsmin.",
      "url": "https://getnobullshit.com/fr/a-propos",
      "sameAs": "https://fgribreau.com",
      "relations": [
        {
          "predicate": "AFFILIATED_WITH",
          "targetId": "e_brand",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_author__fr_3",
          "text": "Je transforme l’informatique en centre de profit. Quinze ans à architecturer, construire et réparer des systèmes d’information — de la startup au grand compte. Partout, les mêmes problèmes qui reviennent, et les mêmes principes pour les régler. NoBullshit Tech-Lead , c’est ce condensé.",
          "sourceUrl": "https://getnobullshit.com/fr/a-propos",
          "pageTitle": "À propos — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "evidence"
        },
        {
          "chunkId": "e_author__en_4",
          "text": "I turn IT into a profit center. Fifteen years architecting, building and fixing information systems — from the startup to the large enterprise. Everywhere, the same problems coming back, and the same principles to fix them. NoBullshit Tech-Lead is that distillation.",
          "sourceUrl": "https://getnobullshit.com/en/about",
          "pageTitle": "About — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "evidence"
        },
        {
          "chunkId": "e_author__fr_5",
          "text": "Je prends le rôle de CPTO pour des équipes tech — architecture, management, produit, prod —, je mène des audits techniques 360° et j’aide les dirigeants à trancher quand ça compte. Et je construis mes propres SaaS, de l’idée au premier euro de MRR : une douzaine de fois.",
          "sourceUrl": "https://getnobullshit.com/fr/a-propos",
          "pageTitle": "À propos — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "evidence"
        },
        {
          "chunkId": "e_author__en_6",
          "text": "I step in as CPTO for tech teams — architecture, management, product, production —, I run 360° technical audits, and I help leaders make the right call when it matters. And I build my own SaaS, from idea to first euro of MRR: a dozen times over.",
          "sourceUrl": "https://getnobullshit.com/en/about",
          "pageTitle": "About — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "evidence"
        }
      ]
    },
    {
      "entityId": "e_book",
      "@type": "nbtl:Book",
      "name": "NoBullshit Tech-Lead",
      "description": "Livre de 240 pages en français qui réunit 60 principes pour gérer la dette technique, livrer sans stress, tenir la production et bâtir une organisation efficace, du développeur au CTO. Chaque chapitre porte une idée, en trois pages au plus.",
      "url": "https://getnobullshit.com/fr/le-livre",
      "relations": [
        {
          "predicate": "AUTHORED_BY",
          "targetId": "e_author",
          "targetName": "François-Guillaume Ribreau"
        },
        {
          "predicate": "PRODUCED_BY",
          "targetId": "e_brand",
          "targetName": "NoBullshit Tech-Lead"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principles",
          "targetName": "Les 60 principes Tech-Lead & CTO"
        },
        {
          "predicate": "SUITED_FOR",
          "targetId": "e_role_tech_lead",
          "targetName": "Tech-Lead",
          "confidence": "declared"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_book__fr_7",
          "text": "60 principes fondamentaux, du développeur au CTO. Une idée par chapitre, 3 pages maximum, des illustrations qui restent.",
          "sourceUrl": "https://getnobullshit.com/fr/le-livre",
          "pageTitle": "Le livre — 240 pages, 60 principes | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_book__en_8",
          "text": "60 core principles, from developer to CTO. One idea per chapter, three pages max, illustrations that stick.",
          "sourceUrl": "https://getnobullshit.com/en/the-book",
          "pageTitle": "The book — 240 pages, 60 principles | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_book__fr_9",
          "text": "Ce livre recense les 60 principes essentiels applicables de la petite à la grande entreprise, du développeur au CTO en passant par le Tech-Lead et l’architecte pour répondre aux problèmes du quotidien.",
          "sourceUrl": "https://getnobullshit.com/fr/",
          "pageTitle": "NoBullshit Tech-Lead : 60 principes pour Tech-Lead et CTO",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_book__en_10",
          "text": "This book gathers the 60 essential principles that apply from the smallest startup to the largest enterprise, from developer to CTO — including tech leads and architects — to solve everyday problems.",
          "sourceUrl": "https://getnobullshit.com/en/",
          "pageTitle": "NoBullshit Tech-Lead: 60 principles for tech leads and CTOs",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principles",
      "@type": "Taxonomy",
      "name": "Les 60 principes Tech-Lead & CTO",
      "alternateName": "The 60 Tech-Lead & CTO principles",
      "description": "Les 60 principes du livre NoBullshit Tech-Lead, répartis en 9 catégories (Développement, Recrutement, Produit, Infrastructure, Organisation, Culture, Vision, Management, Vie personnelle). Chaque principe a sa page sur getnobullshit.com, avec les retours d’expérience de la communauté.",
      "url": "https://getnobullshit.com/fr/ressources",
      "relations": [
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_assurer_la_transformation_numerique_en_defragmentant",
          "targetName": "Assurer la transformation numérique en défragmentant"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_cest_le_code_qui_fait_foi",
          "targetName": "C'est le code qui fait foi"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_choix_technologique_x_ou_y",
          "targetName": "Choix technologique : X ou Y ?"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_considerer_le_si_comme_un_ocean",
          "targetName": "Considérer le SI comme un océan"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_contraindre_dabord_relacher_plus_tard",
          "targetName": "Contraindre d’abord, relâcher plus tard"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_documenter_le_rationnel",
          "targetName": "Documenter le rationnel"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_faire_dune_pierre_trois_coups",
          "targetName": "Faire d'une pierre trois coups"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_le_nommage_doit_etre_ennuyeux",
          "targetName": "Le nommage doit être ennuyeux"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_le_ratio_production_consommation",
          "targetName": "Le ratio production/consommation"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_mettre_le_plus_de_contraintes_en_amont",
          "targetName": "Mettre le plus de contraintes en amont"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_ne_mets_pas_tes_noix_dans_letau",
          "targetName": "Ne mets pas tes noix dans l'étau"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_preferer_le_declaratif_sur_limperatif",
          "targetName": "Préférer le déclaratif sur l'impératif"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_preferer_lexplicite_a_limplicite",
          "targetName": "Préférer l'explicite à l'implicite"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principles__fr_11",
          "text": "Tout le livre, gratuit, en entier. Pas de teasing, pas de mur. Classés par catégorie — du dev à la vie perso.",
          "sourceUrl": "https://getnobullshit.com/fr/ressources",
          "pageTitle": "Ressources — les 60 principes | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principles__en_12",
          "text": "The whole book, free, in full. No teasing, no paywall. Grouped by category — from dev to personal life.",
          "sourceUrl": "https://getnobullshit.com/en/resources",
          "pageTitle": "Resources — the 60 principles | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_role_tech_lead",
      "@type": "Concept",
      "name": "Tech-Lead",
      "alternateName": "Tech Lead",
      "description": "Rôle de l’ingénieur qui répond de la direction technique d’une équipe, c’est-à-dire de l’architecture, de la qualité, des choix techniques et de la livraison. On le devient quand on répond de ce que l’équipe livre, et plus seulement de son propre code.",
      "url": "https://getnobullshit.com/fr/guides/devenir-tech-lead",
      "hasChunks": [
        {
          "chunkId": "e_role_tech_lead__fr_13",
          "text": "On devient Tech-Lead le jour où l’on répond de ce que l’équipe livre, et plus seulement de son propre code. Le titre suit souvent après. Il faut déjà être crédible techniquement, puis apprendre trois métiers nouveaux : décider et écrire pourquoi, faire progresser les autres, parler produit et business.",
          "sourceUrl": "https://getnobullshit.com/fr/guides/devenir-tech-lead",
          "pageTitle": "Devenir Tech-Lead : guide de la transition | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_role_tech_lead__en_14",
          "text": "You become a Tech Lead the day you are accountable for what the team ships, and no longer only for your own code. The title often comes later. You need to be technically credible first, then learn three new jobs: making decisions and writing down why, helping others grow, and speaking product and business.",
          "sourceUrl": "https://getnobullshit.com/en/guides/becoming-a-tech-lead",
          "pageTitle": "How to become a Tech Lead: the transition guide",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_role_tech_lead__fr_15",
          "text": "Un Tech-Lead répond de cinq choses : la direction technique de l’équipe, la qualité de ce qui est livré, la capacité à livrer souvent sans stress, la fiabilité en production et la montée en compétence de l’équipe. Il ne fait pas tout lui-même. Il s’assure que c’est fait, rend les décisions explicites et retire ce qui bloque.",
          "sourceUrl": "https://getnobullshit.com/fr/guides/responsabilites-tech-lead",
          "pageTitle": "Responsabilités d’un Tech-Lead : le guide concret",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_role_tech_lead__en_16",
          "text": "A Tech Lead is accountable for five things: the team’s technical direction, the quality of what ships, the ability to ship often without stress, reliability in production, and the team’s growth. They do not do everything themselves. They make sure it gets done, make decisions explicit and remove what blocks the team.",
          "sourceUrl": "https://getnobullshit.com/en/guides/tech-lead-responsibilities",
          "pageTitle": "Tech Lead responsibilities: a practical guide",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_role_engineering_manager",
      "@type": "Concept",
      "name": "Engineering Manager",
      "description": "Rôle qui répond des personnes d’une équipe technique, du recrutement aux entretiens individuels, à l’évolution de carrière et à l’organisation. Dans une petite structure, la même personne le cumule souvent avec celui de Tech-Lead.",
      "url": "https://getnobullshit.com/fr/guides/tech-lead-vs-engineering-manager",
      "hasChunks": [
        {
          "chunkId": "e_role_engineering_manager__fr_17",
          "text": "Le Tech-Lead répond de la direction technique d’une équipe : architecture, qualité, choix techniques, livraison. L’Engineering Manager répond des personnes : recrutement, entretiens individuels, évolution de carrière, organisation. Dans une petite structure, une seule personne porte souvent les deux casquettes ; quand l’équipe grandit, les séparer évite que l’une des deux soit négligée.",
          "sourceUrl": "https://getnobullshit.com/fr/guides/tech-lead-vs-engineering-manager",
          "pageTitle": "Tech-Lead vs Engineering Manager : quelles différences ?",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_role_engineering_manager__en_18",
          "text": "The Tech Lead is accountable for a team’s technical direction: architecture, quality, technical choices, delivery. The Engineering Manager is accountable for the people: hiring, one-on-ones, career growth, organisation. In a small company one person often wears both hats; as the team grows, splitting them keeps either one from being neglected.",
          "sourceUrl": "https://getnobullshit.com/en/guides/tech-lead-vs-engineering-manager",
          "pageTitle": "Tech Lead vs Engineering Manager: what’s the difference?",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_assurer_la_transformation_numerique_en_defragmentant",
      "@type": "Methodology",
      "name": "Assurer la transformation numérique en défragmentant",
      "alternateName": "Drive digital transformation by defragmenting",
      "description": "Avec le temps, le SI d'une entreprise se fragmente et la même information se duplique partout. Cette fragmentation ralentit tout et allonge le time-to-market.",
      "url": "https://getnobullshit.com/fr/tech-lead/assurer-la-transformation-numerique-en-defragmentant",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_assurer_la_transformation_numerique_en_defragmentant__fr_19",
          "text": "Aujourd’hui, la valeur d’une entreprise ne se mesure plus à ses logiciels ou ses algorithmes mais à ses données. Au fil du temps, une entreprise avec un historique important aura un Système d'Informations (SI) fragmenté. Concrètement, si l’on réalise une photographie d'un SI d’une entreprise de plus de 10 ans d'existence, on constate qu’un même type d'information se retrouvera à plusieurs endroits. C’est ce que j'appelle la fragmentation. Qui dit fragmentation, dit perte de performance du SI, évolutions complexes, rallongement du time-to-market.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/assurer-la-transformation-numerique-en-defragmentant",
          "pageTitle": "Assurer la transformation numérique en défragmentant",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_assurer_la_transformation_numerique_en_defragmentant__en_20",
          "text": "Today the value of a company is measured by its data more than by its software or its algorithms. Over time, a company with a long history ends up with a fragmented information system, where the same type of information lives in several places. I call that fragmentation, and it brings a slower IS, harder changes and a longer time-to-market.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/assurer-la-transformation-numerique-en-defragmentant",
          "pageTitle": "Drive digital transformation by defragmenting | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_cest_le_code_qui_fait_foi",
      "@type": "Methodology",
      "name": "C'est le code qui fait foi",
      "alternateName": "The code is the source of truth",
      "description": "En production, c'est le code qui fonctionne et qui fait foi. Specs, User Stories et maquettes restent des intermédiaires ; seul le code est tangible et utile.",
      "url": "https://getnobullshit.com/fr/tech-lead/cest-le-code-qui-fait-foi",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_cest_le_code_qui_fait_foi__fr_21",
          "text": "Ce qui fonctionne en production c'est le code, ce ne sont pas les spécifications, les User Stories, les issues ou encore les maquettes, c’est donc bien le code qui fait foi. Le code est la seule matière tangible et utile, il est la finalité.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/cest-le-code-qui-fait-foi",
          "pageTitle": "C'est le code qui fait foi | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_cest_le_code_qui_fait_foi__en_22",
          "text": "What runs in production is the code itself, well ahead of the specifications, the user stories, the issues or the mockups. So the code is what holds the truth. It is the only tangible, useful material, and it is the end goal.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/cest-le-code-qui-fait-foi",
          "pageTitle": "The code is the source of truth | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_choix_technologique_x_ou_y",
      "@type": "Methodology",
      "name": "Choix technologique : X ou Y ?",
      "alternateName": "Technology choice: X or Y?",
      "description": "PostgreSQL ou MongoDB ? Java, JavaScript ou Rust ? Kubernetes ou PaaS ? Comment arbitrer un choix technologique qui engage l'avenir de l'entreprise.",
      "url": "https://getnobullshit.com/fr/tech-lead/choix-technologique-x-ou-y",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_choix_technologique_x_ou_y__fr_23",
          "text": "Au fil des années, j'ai vu pas mal de personnes dans des positions CTO ou de Lead venir me demander quelle technologie, langage de programmation ou framework utiliser. Est-ce qu'il vaut mieux partir sur PostgreSQL, MongoDB ou MariaDB ? Coder en Java, JavaScript ou Rust ? Est-ce que je mets mes applications sur du Kubernetes bare-metal ou alors sur une Platform as a Service (PaaS) ? Tant de choix qui vont avoir un impact sur le futur de l’entreprise.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/choix-technologique-x-ou-y",
          "pageTitle": "Choix technologique : X ou Y ? | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_choix_technologique_x_ou_y__en_24",
          "text": "Over the years, plenty of people in CTO or Lead roles have come to ask me which technology, language or framework to use. PostgreSQL, MongoDB or MariaDB? Java, JavaScript or Rust? Should I run my apps on bare-metal Kubernetes or on a Platform as a Service? So many choices that will shape the future of the company.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/choix-technologique-x-ou-y",
          "pageTitle": "Technology choice: X or Y? | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_considerer_le_si_comme_un_ocean",
      "@type": "Methodology",
      "name": "Considérer le SI comme un océan",
      "alternateName": "Think of the information system as an ocean",
      "description": "Les données ont une gravité et les applications gravitent autour. En surface, l'utilisateur final ; au fond, la donnée. Voyez votre SI comme un océan.",
      "url": "https://getnobullshit.com/fr/tech-lead/considerer-le-si-comme-un-ocean",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_considerer_le_si_comme_un_ocean__fr_25",
          "text": "Les données subissent la gravité1, la majorité des applications du SI gravitent autour. Ces applications se trouvent à mi-chemin entre la surface et le fond de l'océan. Tout ce qui touche l'utilisateur final est à la surface. Nos utilisateurs surfent sur notre SI grâce à des applications mobiles, des applications web, des sites webs et des clients lourds. Ils génèrent du mouvement et de l'information.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/considerer-le-si-comme-un-ocean",
          "pageTitle": "Considérer le SI comme un océan | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_considerer_le_si_comme_un_ocean__en_26",
          "text": "Data has gravity, and most of the applications in the information system orbit around it. These applications sit halfway between the surface and the bottom of the ocean. Everything that touches the end user is at the surface. Our users surf our IS through mobile apps, web apps, websites and desktop clients, generating movement and information.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/considerer-le-si-comme-un-ocean",
          "pageTitle": "Think of the information system as an ocean | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_contraindre_dabord_relacher_plus_tard",
      "@type": "Methodology",
      "name": "Contraindre d’abord, relâcher plus tard",
      "alternateName": "Constrain first, relax later",
      "description": "Plus les contraintes arrivent tôt dans un projet, mieux on garde le cap fixé. Contraindre d'abord puis relâcher plus tard découle directement de là.",
      "url": "https://getnobullshit.com/fr/tech-lead/contraindre-dabord-relacher-plus-tard",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_contraindre_dabord_relacher_plus_tard__fr_27",
          "text": "Nous avons vu précédemment que plus des contraintes étaient instaurées tôt dans un projet, plus nous étions en capacité de garder le cap prédéfini. Le principe de contraindre d'abord et relâcher plus tard est une conséquence de ce premier principe.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/contraindre-dabord-relacher-plus-tard",
          "pageTitle": "Contraindre d’abord, relâcher plus tard | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_contraindre_dabord_relacher_plus_tard__en_28",
          "text": "We saw earlier that the sooner constraints are set in a project, the better we can hold the course we defined. Constraining first and relaxing later follows directly from that first principle.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/contraindre-dabord-relacher-plus-tard",
          "pageTitle": "Constrain first, relax later | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_documenter_le_rationnel",
      "@type": "Methodology",
      "name": "Documenter le rationnel",
      "alternateName": "Document the rationale",
      "description": "Prises à l'oral, les décisions se déforment ou s'oublient avec le temps. Documenter le rationnel garde vivant le pourquoi des choix structurants.",
      "url": "https://getnobullshit.com/fr/tech-lead/documenter-le-rationnel",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_documenter_le_rationnel__fr_29",
          "text": "Les décisions sont prises de manière orale ? Au sein de l'équipe ? Tout au long du projet ? Il s'avère que nos souvenirs sur cette décision changent dans le temps voire, pire, disparaissent.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/documenter-le-rationnel",
          "pageTitle": "Documenter le rationnel | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_documenter_le_rationnel__en_30",
          "text": "Are decisions made out loud? Within the team? All the way through the project? It turns out our memory of a decision shifts over time, or worse, disappears.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/documenter-le-rationnel",
          "pageTitle": "Document the rationale | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_faire_dune_pierre_trois_coups",
      "@type": "Methodology",
      "name": "Faire d'une pierre trois coups",
      "alternateName": "Kill three birds with one stone",
      "description": "Comment accomplir autant sans se tuer à la tâche ? En visant trois effets utiles pour une même action. Voilà ce que j'appelle faire d'une pierre, trois coups.",
      "url": "https://getnobullshit.com/fr/tech-lead/faire-dune-pierre-trois-coups",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_faire_dune_pierre_trois_coups__fr_31",
          "text": "On me demande parfois comment je fais pour accomplir autant. Bien que je ne me considère pas comme quelqu’un d'extrêmement productif, j’ai tout de même observé que j’appliquais très souvent un principe que j'aime appeler “faire d'une pierre, trois coups”.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/faire-dune-pierre-trois-coups",
          "pageTitle": "Faire d'une pierre trois coups | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_faire_dune_pierre_trois_coups__en_32",
          "text": "People sometimes ask how I get so much done. I don't think of myself as especially productive, yet I've noticed I very often apply a principle I like to call “kill three birds with one stone”.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/faire-dune-pierre-trois-coups",
          "pageTitle": "Kill three birds with one stone | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_le_nommage_doit_etre_ennuyeux",
      "@type": "Methodology",
      "name": "Le nommage doit être ennuyeux",
      "alternateName": "Naming should be boring",
      "description": "Bien nommer est difficile, presque un art. Des règles existent pourtant : un nom descriptif, sans ambiguïté, qui se comprend seul. Un nouvel arrivant le saisit-il ?",
      "url": "https://getnobullshit.com/fr/tech-lead/le-nommage-doit-etre-ennuyeux",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_le_nommage_doit_etre_ennuyeux__fr_33",
          "text": "L'exercice de nommage est souvent difficile, il est même parfois perçu comme un art. Néanmoins, il existe quelques règles. Le nom idéal doit être le plus descriptif et transparent possible, être dénué d’ambiguïté, et se suffire à lui-même. Je me mets souvent dans la peau d'un nouvel arrivant. Comprendra-t-il ce terme ?",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/le-nommage-doit-etre-ennuyeux",
          "pageTitle": "Le nommage doit être ennuyeux | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_le_nommage_doit_etre_ennuyeux__en_34",
          "text": "Naming is often hard, and it's sometimes seen as an art. Still, a few rules exist. The ideal name is as descriptive and transparent as possible, carries no ambiguity, and stands on its own. I often put myself in a newcomer's shoes and ask: will they understand this term?",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/le-nommage-doit-etre-ennuyeux",
          "pageTitle": "Naming should be boring | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_le_ratio_production_consommation",
      "@type": "Methodology",
      "name": "Le ratio production/consommation",
      "alternateName": "The production/consumption ratio",
      "description": "Le ratio production/consommation compare ce que l'on produit et ce que l'on consomme, au travail comme dans la vie. Un principe qui invite à l'introspection.",
      "url": "https://getnobullshit.com/fr/tech-lead/le-ratio-production-consommation",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_le_ratio_production_consommation__fr_35",
          "text": "On s’est tous au moins une fois posé la question “Qu’est-ce que je fais ici, sur Terre ?”.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/le-ratio-production-consommation",
          "pageTitle": "Le ratio production/consommation | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_le_ratio_production_consommation__en_36",
          "text": "We've all asked ourselves at least once, “what am I doing here, on Earth?”",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/le-ratio-production-consommation",
          "pageTitle": "The production/consumption ratio | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_mettre_le_plus_de_contraintes_en_amont",
      "@type": "Methodology",
      "name": "Mettre le plus de contraintes en amont",
      "alternateName": "Put the most constraints upfront",
      "description": "Ajouter des tests, du multi-tenant ou de l'analyse statique sur un projet déjà avancé fait mal. D'où ce principe : mettre le plus de contraintes en amont.",
      "url": "https://getnobullshit.com/fr/tech-lead/mettre-le-plus-de-contraintes-en-amont",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_mettre_le_plus_de_contraintes_en_amont__fr_37",
          "text": "Avez-vous déjà mis en place des tests sur un projet qui n'en avait aucun ? Du multi-tenant sur un produit mono-tenant ? Un outil d'analyse statique de code sur un projet bien avancé ? C'est (très) douloureux, n'est-ce pas ?",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/mettre-le-plus-de-contraintes-en-amont",
          "pageTitle": "Mettre le plus de contraintes en amont | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_mettre_le_plus_de_contraintes_en_amont__en_38",
          "text": "Have you ever added tests to a project that had none? Multi-tenancy to a single-tenant product? A static analysis tool to a project well under way? It's (very) painful, isn't it?",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/mettre-le-plus-de-contraintes-en-amont",
          "pageTitle": "Put the most constraints upfront | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_ne_mets_pas_tes_noix_dans_letau",
      "@type": "Methodology",
      "name": "Ne mets pas tes noix dans l'étau",
      "alternateName": "Don’t put your nuts in the vise",
      "description": "Entre gens qui visent le même but, les conflits viennent d'un écart de contexte, qui installe friction et défiance. Comment enrayer ce cercle vicieux ?",
      "url": "https://getnobullshit.com/fr/tech-lead/ne-mets-pas-tes-noix-dans-letau",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_ne_mets_pas_tes_noix_dans_letau__fr_39",
          "text": "Au sein d’une entreprise ou dans la vie personnelle, les conflits entre personnes partageant les mêmes objectifs viennent d’une différence de contexte entre elles. Cette différence de contexte d'information peut entraîner une friction et un manque de confiance au sein de l’équipe, qui peut s’aggraver au fil du temps. Mais comment s’installe ce cercle vicieux ?",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/ne-mets-pas-tes-noix-dans-letau",
          "pageTitle": "Ne mets pas tes noix dans l'étau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_ne_mets_pas_tes_noix_dans_letau__en_40",
          "text": "Within a company or in your personal life, conflicts between people who share the same goals come from a difference in context between them. That gap in information can create friction and erode trust within the team, and it tends to get worse over time. So how does this vicious circle take hold?",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/ne-mets-pas-tes-noix-dans-letau",
          "pageTitle": "Don’t put your nuts in the vise | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_preferer_le_declaratif_sur_limperatif",
      "@type": "Methodology",
      "name": "Préférer le déclaratif sur l'impératif",
      "alternateName": "Prefer declarative over imperative",
      "description": "Au lieu de dicter chaque étape à la machine (impératif), déclarez le problème à résoudre. Le développeur énonce le quoi et la machine trouve le comment.",
      "url": "https://getnobullshit.com/fr/tech-lead/preferer-le-declaratif-sur-limperatif",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_preferer_le_declaratif_sur_limperatif__fr_41",
          "text": "Plutôt que d'indiquer à la machine avec une approche impérative les étapes successives à exécuter, il est préférable de déclarer, de formuler le problème à résoudre. Le développeur n'exprime donc plus le comment, il exprime le quoi. La responsabilité de la machine est d'interpréter l'énoncé du problème, puis de le résoudre de manière efficace.",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/preferer-le-declaratif-sur-limperatif",
          "pageTitle": "Préférer le déclaratif sur l'impératif | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_preferer_le_declaratif_sur_limperatif__en_42",
          "text": "Rather than telling the machine, in an imperative style, the successive steps to run, it's better to declare, to state the problem you want solved. The developer states the what and leaves the how to the machine. It falls to the machine to interpret the problem and then solve it efficiently.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/preferer-le-declaratif-sur-limperatif",
          "pageTitle": "Prefer declarative over imperative | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_preferer_lexplicite_a_limplicite",
      "@type": "Methodology",
      "name": "Préférer l'explicite à l'implicite",
      "alternateName": "Prefer explicit over implicit",
      "description": "Transmis à l'oral, les choix d'architecture restent implicites, cachés dans le système. Rendez-les explicites pour passer de la réaction à l'anticipation.",
      "url": "https://getnobullshit.com/fr/tech-lead/preferer-lexplicite-a-limplicite",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_preferer_lexplicite_a_limplicite__fr_43",
          "text": "Une culture de transmission orale des choix structurants de processus, d'architectures ou de configuration, sont autant de choix implicites, dissimulés sous diverses formes dans le système. Ce chapitre permet de passer de l'ère de la réaction à celle de l’anticipation !",
          "sourceUrl": "https://getnobullshit.com/fr/tech-lead/preferer-lexplicite-a-limplicite",
          "pageTitle": "Préférer l'explicite à l'implicite | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_preferer_lexplicite_a_limplicite__en_44",
          "text": "Passing on structural choices of process, architecture or configuration by word of mouth turns them into implicit choices, hidden in various forms across the system. This chapter is about moving from an age of reaction to an age of anticipation.",
          "sourceUrl": "https://getnobullshit.com/en/tech-lead/preferer-lexplicite-a-limplicite",
          "pageTitle": "Prefer explicit over implicit | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_term_ssot",
      "@type": "Concept",
      "name": "SSoT (source de vérité unique)",
      "alternateName": "SSoT (single source of truth)",
      "description": "Une seule donnée fait foi. On évite de dupliquer l’information dans plusieurs systèmes qui finissent par diverger.",
      "url": "https://getnobullshit.com/fr/glossaire#ssot",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/source-de-verite-unique",
          "targetName": "Source de vérité unique"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_ssot__fr_45",
          "text": "Une seule donnée fait foi. On évite de dupliquer l’information dans plusieurs systèmes qui finissent par diverger.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_ssot__en_46",
          "text": "One piece of data is authoritative. We avoid duplicating information across systems that eventually diverge.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ],
      "sameAs": "https://www.wikidata.org/wiki/Q7523885"
    },
    {
      "entityId": "e_term_soc",
      "@type": "Concept",
      "name": "SoC (Separation of Concerns)",
      "alternateName": "SoC (Separation of Concerns)",
      "description": "Séparer les responsabilités : chaque module fait une chose et la fait bien, sans empiéter sur les autres.",
      "url": "https://getnobullshit.com/fr/glossaire#soc",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/separer-les-interets",
          "targetName": "Séparer les intérêts"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_soc__fr_47",
          "text": "Séparer les responsabilités : chaque module fait une chose et la fait bien, sans empiéter sur les autres.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_soc__en_48",
          "text": "Separating responsibilities: each module does one thing well, without stepping on the others.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ],
      "sameAs": "https://www.wikidata.org/wiki/Q2465506"
    },
    {
      "entityId": "e_term_dette_technique",
      "@type": "Concept",
      "name": "Dette technique",
      "alternateName": "Technical debt",
      "description": "Le coût futur des raccourcis pris aujourd’hui. À distinguer entre dette subie (qu’on encaisse) et dette choisie (qu’on pilote).",
      "url": "https://getnobullshit.com/fr/glossaire#dette-technique",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/prendre-conscience-de-la-dette-subie-et-dompter-la-dette-choisie",
          "targetName": "Prendre conscience de la dette subie et dompter la dette choisie"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_dette_technique__fr_49",
          "text": "Le coût futur des raccourcis pris aujourd’hui. À distinguer entre dette subie (qu’on encaisse) et dette choisie (qu’on pilote).",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_dette_technique__en_50",
          "text": "The future cost of shortcuts taken today. Distinguish suffered debt (you absorb it) from chosen debt (you steer it).",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ],
      "sameAs": "https://www.wikidata.org/wiki/Q1532172"
    },
    {
      "entityId": "e_term_library_first",
      "@type": "Concept",
      "name": "Library-first",
      "alternateName": "Library-first",
      "description": "Concevoir d’abord une bibliothèque réutilisable, puis l’application autour. On favorise la réutilisation et les interfaces propres.",
      "url": "https://getnobullshit.com/fr/glossaire#library-first",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/favoriser-approche-library-first",
          "targetName": "Favoriser l'approche library-first"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_library_first__fr_51",
          "text": "Concevoir d’abord une bibliothèque réutilisable, puis l’application autour. On favorise la réutilisation et les interfaces propres.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_library_first__en_52",
          "text": "Design a reusable library first, then the application around it. Favors reuse and clean interfaces.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_term_map_reduce_humain",
      "@type": "Concept",
      "name": "Map/reduce humain",
      "alternateName": "Human map/reduce",
      "description": "Distribuer un travail entre plusieurs personnes (map) puis consolider (reduce). Puissant, mais coûteux en coordination : à utiliser avec parcimonie.",
      "url": "https://getnobullshit.com/fr/glossaire#map-reduce-humain",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/utiliser-le-map-reduce-humain-avec-parcimonie",
          "targetName": "Utiliser le map/reduce humain avec parcimonie"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_map_reduce_humain__fr_53",
          "text": "Distribuer un travail entre plusieurs personnes (map) puis consolider (reduce). Puissant, mais coûteux en coordination : à utiliser avec parcimonie.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_map_reduce_humain__en_54",
          "text": "Distribute work across people (map) then consolidate (reduce). Powerful but costly in coordination: use sparingly.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_term_go_for_the_edge",
      "@type": "Concept",
      "name": "Go for the edge",
      "alternateName": "Go for the edge",
      "description": "Traiter les cas limites tôt. Ce sont eux qui révèlent les vrais problèmes de conception.",
      "url": "https://getnobullshit.com/fr/glossaire#go-for-the-edge",
      "relations": [],
      "hasChunks": [
        {
          "chunkId": "e_term_go_for_the_edge__fr_55",
          "text": "Traiter les cas limites tôt. Ce sont eux qui révèlent les vrais problèmes de conception.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_go_for_the_edge__en_56",
          "text": "Tackle edge cases early. They reveal the real design problems.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_term_loi_de_conway",
      "@type": "Concept",
      "name": "Loi de Conway (inversée)",
      "alternateName": "Conway’s law (inverse)",
      "description": "L’architecture d’un système reflète l’organisation qui le produit. En l’inversant, on structure les équipes pour obtenir l’architecture voulue.",
      "url": "https://getnobullshit.com/fr/glossaire#loi-de-conway",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/assurer-la-mise-a-lechelle-des-equipes-en-suivant-la-loi-de-conway-inversee",
          "targetName": "Assurer la mise à l'échelle des équipes en suivant la loi de Conway inversée"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_loi_de_conway__fr_57",
          "text": "L’architecture d’un système reflète l’organisation qui le produit. En l’inversant, on structure les équipes pour obtenir l’architecture voulue.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_loi_de_conway__en_58",
          "text": "A system’s architecture mirrors the organization that builds it. Inverting it means structuring teams to get the architecture you want.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ],
      "sameAs": "https://www.wikidata.org/wiki/Q1518855"
    },
    {
      "entityId": "e_term_uat",
      "@type": "Concept",
      "name": "UAT (User Acceptance Testing)",
      "alternateName": "UAT (User Acceptance Testing)",
      "description": "Environnement de recette utilisateur. Dans le livre : s’il t’en faut un, c’est souvent le signe d’un produit mal pensé.",
      "url": "https://getnobullshit.com/fr/glossaire#uat",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/si-tu-as-un-environnement-uat-tas-rate-ton-produit",
          "targetName": "Si tu as un environnement UAT, t'as raté ton produit"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_uat__fr_59",
          "text": "Environnement de recette utilisateur. Dans le livre : s’il t’en faut un, c’est souvent le signe d’un produit mal pensé.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_uat__en_60",
          "text": "User acceptance environment. In the book: if you need one, it’s often a sign of a poorly designed product.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_term_monitoring_alerting",
      "@type": "Concept",
      "name": "Monitoring & alerting",
      "alternateName": "Monitoring & alerting",
      "description": "Mesurer l’état du système (monitoring) et être prévenu quand ça dérape (alerting). L’un sans l’autre ne sert à rien.",
      "url": "https://getnobullshit.com/fr/glossaire#monitoring-alerting",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetUri": "https://getnobullshit.com/fr/tech-lead/pas-de-monitoring-sans-lalerting",
          "targetName": "Pas de monitoring sans l'alerting"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_monitoring_alerting__fr_61",
          "text": "Mesurer l’état du système (monitoring) et être prévenu quand ça dérape (alerting). L’un sans l’autre ne sert à rien.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_monitoring_alerting__en_62",
          "text": "Measure the system’s state (monitoring) and get notified when it goes wrong (alerting). One without the other is useless.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_term_declaratif_vs_imperatif",
      "@type": "Concept",
      "name": "Déclaratif vs impératif",
      "alternateName": "Declarative vs imperative",
      "description": "Décrire le résultat voulu (déclaratif) plutôt que la suite d’étapes (impératif). Plus lisible, plus robuste.",
      "url": "https://getnobullshit.com/fr/glossaire#declaratif-vs-imperatif",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_preferer_le_declaratif_sur_limperatif",
          "targetName": "Préférer le déclaratif sur l'impératif"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_declaratif_vs_imperatif__fr_63",
          "text": "Décrire le résultat voulu (déclaratif) plutôt que la suite d’étapes (impératif). Plus lisible, plus robuste.",
          "sourceUrl": "https://getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_declaratif_vs_imperatif__en_64",
          "text": "Describe the desired result (declarative) rather than the sequence of steps (imperative). More readable, more robust.",
          "sourceUrl": "https://getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-16T15:20:33Z",
          "contentType": "definition"
        }
      ]
    }
  ]
}