{
  "version": "1.0",
  "schema": "https://entitymap.org/spec/v1.0",
  "publisher": {
    "name": "NoBullshit Tech-Lead",
    "url": "https://www.getnobullshit.com"
  },
  "generated": "2026-10-30T18:20:51Z",
  "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://www.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://www.getnobullshit.com/fr/",
          "pageTitle": "NoBullshit Tech-Lead : 60 principes pour Tech-Lead et CTO",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/en/",
          "pageTitle": "NoBullshit Tech-Lead: 60 principles for tech leads and CTOs",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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://www.getnobullshit.com/fr/a-propos",
          "pageTitle": "À propos — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/en/about",
          "pageTitle": "About — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/a-propos",
          "pageTitle": "À propos — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/en/about",
          "pageTitle": "About — François-Guillaume Ribreau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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://www.getnobullshit.com/fr/le-livre",
          "pageTitle": "Le livre — 240 pages, 60 principes | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/en/the-book",
          "pageTitle": "The book — 240 pages, 60 principles | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/",
          "pageTitle": "NoBullshit Tech-Lead : 60 principes pour Tech-Lead et CTO",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/en/",
          "pageTitle": "NoBullshit Tech-Lead: 60 principles for tech leads and CTOs",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/ressources",
      "relations": [
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_arreter_le_gavage_des_developpeurs_ce_sont_des_ingenieurs",
          "targetName": "Arrêter le gavage des développeurs ce sont des ingénieurs"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_articuler_sa_vision_grace_a_soc_ssot",
          "targetName": "Articuler sa vision grâce à SoC & SSoT"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_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"
        },
        {
          "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_chaque_jour_sattaquer_a_la_cause_des_causes",
          "targetName": "Chaque jour s'attaquer à la cause des causes"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_chercher_les_bons_profils_la_ou_ils_sont",
          "targetName": "Chercher les bons profils là où ils sont"
        },
        {
          "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_documentation_technique_generee_ou_rien",
          "targetName": "Documentation technique générée ou rien"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_documenter_le_rationnel",
          "targetName": "Documenter le rationnel"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_emmener_le_plus_rapidement_les_developpeurs_vers_la_production",
          "targetName": "Emmener le plus rapidement les développeurs vers la production"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_experience_competences",
          "targetName": "Comportement > Compétences > Expérience"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_faire_dune_pierre_trois_coups",
          "targetName": "Faire d'une pierre trois coups"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_favoriser_approche_library_first",
          "targetName": "Favoriser l'approche library-first"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_go_for_the_edge",
          "targetName": "Go for the edge"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_insuffler_la_culture_cible_et_la_voir_grandir",
          "targetName": "Insuffler la culture cible et la voir grandir"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_inutile_de_creer_des_conventions_sans_automatisation",
          "targetName": "Inutile de créer des conventions sans automatisation"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_juniors_un_peu_mais_pas_trop",
          "targetName": "Juniors, un peu mais pas trop"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_la_maturite_des_equipes_et_la_discipline_est_un_processus_sache_ou_tu_es",
          "targetName": "La maturité des équipes et la discipline est un processus, sache où tu es"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_le_bon_role_au_bon_niveau",
          "targetName": "Le bon rôle au bon niveau"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_le_nommage_doit_etre_ennuyeux",
          "targetName": "Le nommage doit être ennuyeux"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_le_package_daccueil_pour_les_nouveaux_arrivants",
          "targetName": "Le package d'accueil pour les nouveaux arrivants"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_le_ratio_production_consommation",
          "targetName": "Le ratio production/consommation"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_lentrepreneuriat_nest_pas_un_sprint_mais_un_marathon",
          "targetName": "L'entrepreneuriat n'est pas un sprint mais un marathon"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_lentreprise_est_une_plateforme_sur_laquelle_reposent_les_equipes",
          "targetName": "L'entreprise est une plateforme sur laquelle reposent les équipes"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_lentreprise_nest_quun_des_clients_de_son_produit",
          "targetName": "L'entreprise n'est qu'un des clients de son produit"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_les_1_a_1_comme_outil_managerial",
          "targetName": "Les 1 à 1 comme outil managérial"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_les_bouchons_sont_un_ennemi",
          "targetName": "Les bouchons sont un ennemi"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_les_equipes_pointent_sur_la_production_des_autres",
          "targetName": "Les équipes pointent sur la production des autres"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_les_interfaces_graphiques_en_tant_que_machines_detats_finis",
          "targetName": "Les interfaces graphiques en tant que machines d'états finis"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_les_trolls_un_indicateur_de_letat_de_sante_de_la_culture_interne",
          "targetName": "Les trolls, un indicateur de l’état de santé de la culture interne"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_maintenir_lequilibre_entre_vision_produit_et_technique",
          "targetName": "Maintenir l'équilibre entre vision produit et technique"
        },
        {
          "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_montre_moi_ton_code_je_te_dirai_qui_tu_es",
          "targetName": "Montre-moi ton code, je te dirai qui tu es"
        },
        {
          "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_noubliez_pas_de_gagner_de_largent",
          "targetName": "N’oubliez pas de gagner de l’argent"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_orienter_le_futur_structurellement",
          "targetName": "Orienter le futur structurellement"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_partir_du_constat_que_ca_va_merder_tot_ou_tard",
          "targetName": "Partir du constat que ça va merder tôt ou tard"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_pas_de_monitoring_sans_lalerting",
          "targetName": "Pas de monitoring sans l'alerting"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_plus_nest_pas_mieux",
          "targetName": "Plus n'est pas mieux"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_poser_un_cadre_mais_pas_de_limites",
          "targetName": "Poser un cadre mais pas de limites"
        },
        {
          "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"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_prendre_conscience_de_la_dette_subie_et_dompter_la_dette_choisie",
          "targetName": "Prendre conscience de la dette subie et dompter la dette choisie"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_prequalifier_en_une_question",
          "targetName": "Préqualifier en une question"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_quand_monter_en_competence_quand_partir_sur_ses_competences_existantes_pour_faire_du_run",
          "targetName": "Quand monter en compétence"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_rendre_le_pouvoir_aux_metier",
          "targetName": "Rendre le pouvoir aux métiers"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_rester_coherent_dans_lerreur",
          "targetName": "Rester cohérent dans l'erreur"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_separer_les_interets",
          "targetName": "Séparer les intérêts"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_si_il_y_a_besoin_dune_formation_cest_mal_pense",
          "targetName": "Si il y a besoin d’une formation : c’est mal pensé"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_si_tu_as_un_environnement_uat_tas_rate_ton_produit",
          "targetName": "Si tu as un environnement UAT, t'as raté ton produit"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_sortir_des_competences_developper_un_metier_2",
          "targetName": "Sortir des compétences, développer un métier"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_source_de_verite_unique",
          "targetName": "Source de vérité unique"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_surveiller_du_point_de_vue_utilisateur",
          "targetName": "Surveiller du point de vue utilisateur"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_tout_limiter_dans_lespace_et_dans_le_temps",
          "targetName": "Tout limiter dans l'espace et dans le temps"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_toutes_les_constantes_doivent_etre_configurables",
          "targetName": "Toutes les constantes doivent être configurables"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_utiliser_le_map_reduce_humain_avec_parcimonie",
          "targetName": "Utiliser le map/reduce humain avec parcimonie"
        },
        {
          "predicate": "INCLUDES",
          "targetId": "e_principle_votre_marque_est_votre_design_system",
          "targetName": "Votre marque est votre design system"
        }
      ],
      "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://www.getnobullshit.com/fr/ressources",
          "pageTitle": "Ressources — les 60 principes | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/en/resources",
          "pageTitle": "Resources — the 60 principles | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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://www.getnobullshit.com/fr/guides/devenir-tech-lead",
          "pageTitle": "Devenir Tech-Lead : guide de la transition | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/guides/responsabilites-tech-lead",
          "pageTitle": "Responsabilités d’un Tech-Lead : le guide concret",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/en/guides/tech-lead-responsibilities",
          "pageTitle": "Tech Lead responsibilities: a practical guide",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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://www.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-30T18:20:51Z",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_arreter_le_gavage_des_developpeurs_ce_sont_des_ingenieurs",
      "@type": "Methodology",
      "name": "Arrêter le gavage des développeurs ce sont des ingénieurs",
      "alternateName": "Stop force-feeding developers, they’re engineers",
      "description": "Les développeurs sont des ingénieurs, experts techniques et métier. Travailler au contact des utilisateurs retire des intermédiaires et des pertes d’information.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/arreter-le-gavage-des-developpeurs-ce-sont-des-ingenieurs",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_arreter_le_gavage_des_developpeurs_ce_sont_des_ingenieurs__fr_19",
          "text": "Les développeurs sont des ingénieurs, experts techniques et métier. Travailler au contact des utilisateurs retire des intermédiaires et des pertes d’information.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/arreter-le-gavage-des-developpeurs-ce-sont-des-ingenieurs",
          "pageTitle": "Arrêter le gavage des développeurs ce sont des ingénieurs",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_arreter_le_gavage_des_developpeurs_ce_sont_des_ingenieurs__en_20",
          "text": "Developers are engineers, with technical and business expertise. Working directly with users removes intermediaries and cuts information loss.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/arreter-le-gavage-des-developpeurs-ce-sont-des-ingenieurs",
          "pageTitle": "Stop force-feeding developers, they’re engineers",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_articuler_sa_vision_grace_a_soc_ssot",
      "@type": "Methodology",
      "name": "Articuler sa vision grâce à SoC & SSoT",
      "alternateName": "Articulate your vision through SoC & SSoT",
      "description": "Une source de vérité par donnée, une responsabilité par composant : deux idées pour garder le cap technique, chaque choix structurant étant écrit avec son contexte.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/articuler-sa-vision-grace-a-soc-ssot",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_articuler_sa_vision_grace_a_soc_ssot__fr_21",
          "text": "Une source de vérité par donnée, une responsabilité par composant : deux idées pour garder le cap technique, chaque choix structurant étant écrit avec son contexte.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/articuler-sa-vision-grace-a-soc-ssot",
          "pageTitle": "Articuler sa vision grâce à SoC & SSoT | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_articuler_sa_vision_grace_a_soc_ssot__en_22",
          "text": "One source of truth per piece of data, one responsibility per component: two ideas to hold the technical course, with each structuring choice written down.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/articuler-sa-vision-grace-a-soc-ssot",
          "pageTitle": "Articulate your vision through SoC & SSoT | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_assurer_la_mise_a_lechelle_des_equipes_en_suivant_la_loi_de_conway_inversee",
      "@type": "Methodology",
      "name": "Assurer la mise à l'échelle des équipes en suivant la loi de Conway inversée",
      "alternateName": "Scale teams by following the inverse Conway’s law",
      "description": "L’architecture d’un système reflète l’organisation qui le produit. Pour passer à l’échelle, on découpe les équipes selon l’architecture que l’on vise.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/assurer-la-mise-a-lechelle-des-equipes-en-suivant-la-loi-de-conway-inversee",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_assurer_la_mise_a_lechelle_des_equipes_en_suivant_la_loi_de_conway_inversee__fr_23",
          "text": "L’architecture d’un système reflète l’organisation qui le produit. Pour passer à l’échelle, on découpe les équipes selon l’architecture que l’on vise.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/assurer-la-mise-a-lechelle-des-equipes-en-suivant-la-loi-de-conway-inversee",
          "pageTitle": "Loi de Conway inversée et mise à l'échelle des équipes",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_assurer_la_mise_a_lechelle_des_equipes_en_suivant_la_loi_de_conway_inversee__en_24",
          "text": "A system’s architecture mirrors the organization that builds it. To scale, split the teams along the architecture you are aiming for.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/assurer-la-mise-a-lechelle-des-equipes-en-suivant-la-loi-de-conway-inversee",
          "pageTitle": "Scale teams by following the inverse Conway’s law",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_25",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_assurer_la_transformation_numerique_en_defragmentant__en_26",
          "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://www.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-30T18:20:51Z",
          "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://www.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_27",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_cest_le_code_qui_fait_foi__en_28",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_chaque_jour_sattaquer_a_la_cause_des_causes",
      "@type": "Methodology",
      "name": "Chaque jour s'attaquer à la cause des causes",
      "alternateName": "Tackle the cause of causes every single day",
      "description": "Remonter un problème récurrent jusqu’à sa cause plutôt que de le contourner une fois de plus : un geste à reprendre chaque jour dans son équipe.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/chaque-jour-sattaquer-a-la-cause-des-causes",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_chaque_jour_sattaquer_a_la_cause_des_causes__fr_29",
          "text": "Remonter un problème récurrent jusqu’à sa cause plutôt que de le contourner une fois de plus : un geste à reprendre chaque jour dans son équipe.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/chaque-jour-sattaquer-a-la-cause-des-causes",
          "pageTitle": "Chaque jour s'attaquer à la cause des causes | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_chaque_jour_sattaquer_a_la_cause_des_causes__en_30",
          "text": "Trace a recurring problem back to its cause instead of working around it once more: a habit to repeat every day in your team.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/chaque-jour-sattaquer-a-la-cause-des-causes",
          "pageTitle": "Tackle the cause of causes every single day | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_chercher_les_bons_profils_la_ou_ils_sont",
      "@type": "Methodology",
      "name": "Chercher les bons profils là où ils sont",
      "alternateName": "Look for the right profiles where they are",
      "description": "Un principe de recrutement : aller chercher les bons profils là où ils se trouvent.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/chercher-les-bons-profils-la-ou-ils-sont",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_chercher_les_bons_profils_la_ou_ils_sont__fr_31",
          "text": "Un principe de recrutement : aller chercher les bons profils là où ils se trouvent.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/chercher-les-bons-profils-la-ou-ils-sont",
          "pageTitle": "Chercher les bons profils là où ils sont | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_chercher_les_bons_profils_la_ou_ils_sont__en_32",
          "text": "A hiring principle: look for the right profiles where they actually are.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/chercher-les-bons-profils-la-ou-ils-sont",
          "pageTitle": "Look for the right profiles where they are | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_33",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_choix_technologique_x_ou_y__en_34",
          "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://www.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-30T18:20:51Z",
          "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://www.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_35",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_considerer_le_si_comme_un_ocean__en_36",
          "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://www.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-30T18:20:51Z",
          "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://www.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_37",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_contraindre_dabord_relacher_plus_tard__en_38",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_documentation_technique_generee_ou_rien",
      "@type": "Methodology",
      "name": "Documentation technique générée ou rien",
      "alternateName": "Generated technical documentation or nothing",
      "description": "La documentation technique est générée, ou elle n’existe pas. Même logique que la règle Unix : écrire des programmes qui écrivent des programmes.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/documentation-technique-generee-ou-rien",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_documentation_technique_generee_ou_rien__fr_39",
          "text": "La documentation technique est générée, ou elle n’existe pas. Même logique que la règle Unix : écrire des programmes qui écrivent des programmes.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/documentation-technique-generee-ou-rien",
          "pageTitle": "Documentation technique générée ou rien | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_documentation_technique_generee_ou_rien__en_40",
          "text": "Technical documentation is generated, or it does not exist. Same logic as the Unix rule: write programs that write programs rather than producing everything by hand.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/documentation-technique-generee-ou-rien",
          "pageTitle": "Generated technical documentation or nothing | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_41",
          "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://www.getnobullshit.com/fr/tech-lead/documenter-le-rationnel",
          "pageTitle": "Documenter le rationnel | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_documenter_le_rationnel__en_42",
          "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://www.getnobullshit.com/en/tech-lead/documenter-le-rationnel",
          "pageTitle": "Document the rationale | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_emmener_le_plus_rapidement_les_developpeurs_vers_la_production",
      "@type": "Methodology",
      "name": "Emmener le plus rapidement les développeurs vers la production",
      "alternateName": "Get developers to production as fast as possible",
      "description": "Raccourcir le chemin du code à la production : déploiement automatisé, environnements simples, peu d’étapes manuelles. Un travail en cours n’a aucune valeur.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/emmener-le-plus-rapidement-les-developpeurs-vers-la-production",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_emmener_le_plus_rapidement_les_developpeurs_vers_la_production__fr_43",
          "text": "Raccourcir le chemin du code à la production : déploiement automatisé, environnements simples, peu d’étapes manuelles. Un travail en cours n’a aucune valeur.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/emmener-le-plus-rapidement-les-developpeurs-vers-la-production",
          "pageTitle": "Amener vite les développeurs en production | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_emmener_le_plus_rapidement_les_developpeurs_vers_la_production__en_44",
          "text": "Shorten the path between code and production: automated deployment, simple environments, few manual steps. Work in progress has no value until it ships.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/emmener-le-plus-rapidement-les-developpeurs-vers-la-production",
          "pageTitle": "Get developers to production as fast as possible",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_experience_competences",
      "@type": "Methodology",
      "name": "Comportement > Compétences > Expérience",
      "alternateName": "Behavior > Skills > Experience",
      "description": "Au recrutement, on regarde d’abord le comportement, puis les compétences, puis l’expérience. Un ordre de lecture des profils.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/experience-competences",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_experience_competences__fr_45",
          "text": "Au recrutement, on regarde d’abord le comportement, puis les compétences, puis l’expérience. Un ordre de lecture des profils.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/experience-competences",
          "pageTitle": "Comportement > Compétences > Expérience | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_experience_competences__en_46",
          "text": "When hiring, look at behavior first, then skills, then experience. A reading order for profiles.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/experience-competences",
          "pageTitle": "Behavior > Skills > Experience | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_47",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_faire_dune_pierre_trois_coups__en_48",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_favoriser_approche_library_first",
      "@type": "Methodology",
      "name": "Favoriser l'approche library-first",
      "alternateName": "Favor a library-first approach",
      "description": "Partir d’une bibliothèque réutilisable, puis bâtir l’application autour : la réutilisation et des interfaces propres passent en premier.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/favoriser-approche-library-first",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_favoriser_approche_library_first__fr_49",
          "text": "Partir d’une bibliothèque réutilisable, puis bâtir l’application autour : la réutilisation et des interfaces propres passent en premier.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/favoriser-approche-library-first",
          "pageTitle": "Favoriser l'approche library-first | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_favoriser_approche_library_first__en_50",
          "text": "Start from a reusable library, then build the application around it: reuse and clean interfaces come first.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/favoriser-approche-library-first",
          "pageTitle": "Favor a library-first approach | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_go_for_the_edge",
      "@type": "Methodology",
      "name": "Go for the edge",
      "alternateName": "Go for the edge",
      "description": "Un principe de recrutement du livre, résumé par la formule « go for the edge ».",
      "url": "https://www.getnobullshit.com/fr/tech-lead/go-for-the-edge",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_go_for_the_edge__fr_51",
          "text": "Un principe de recrutement du livre, résumé par la formule « go for the edge ».",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/go-for-the-edge",
          "pageTitle": "Go for the edge | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_go_for_the_edge__en_52",
          "text": "A hiring principle from the book, summed up by the phrase “go for the edge”.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/go-for-the-edge",
          "pageTitle": "Go for the edge | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_insuffler_la_culture_cible_et_la_voir_grandir",
      "@type": "Methodology",
      "name": "Insuffler la culture cible et la voir grandir",
      "alternateName": "Instill the target culture and watch it grow",
      "description": "Recruter, c’est aussi transmettre la culture visée et la voir grandir. Le Tech-Lead et l’Engineering Manager la portent, chacun avec ses outils.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/insuffler-la-culture-cible-et-la-voir-grandir",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_insuffler_la_culture_cible_et_la_voir_grandir__fr_53",
          "text": "Recruter, c’est aussi transmettre la culture visée et la voir grandir. Le Tech-Lead et l’Engineering Manager la portent, chacun avec ses outils.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/insuffler-la-culture-cible-et-la-voir-grandir",
          "pageTitle": "Insuffler la culture cible et la voir grandir | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_insuffler_la_culture_cible_et_la_voir_grandir__en_54",
          "text": "Hiring also means passing on the target culture and watching it grow. The Tech-Lead and the Engineering Manager both carry it, each with their own tools.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/insuffler-la-culture-cible-et-la-voir-grandir",
          "pageTitle": "Instill the target culture and watch it grow | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_inutile_de_creer_des_conventions_sans_automatisation",
      "@type": "Methodology",
      "name": "Inutile de créer des conventions sans automatisation",
      "alternateName": "No point creating conventions without automation",
      "description": "Une convention non vérifiée automatiquement finit ignorée. Mieux vaut une règle contrôlée par la CI : des mécanismes plutôt que des intentions.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/inutile-de-creer-des-conventions-sans-automatisation",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_inutile_de_creer_des_conventions_sans_automatisation__fr_55",
          "text": "Une convention non vérifiée automatiquement finit ignorée. Mieux vaut une règle contrôlée par la CI : des mécanismes plutôt que des intentions.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/inutile-de-creer-des-conventions-sans-automatisation",
          "pageTitle": "Inutile de créer des conventions sans automatisation",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_inutile_de_creer_des_conventions_sans_automatisation__en_56",
          "text": "A convention that is not checked automatically ends up ignored. Turn the spoken rule into one the CI enforces: mechanisms rather than intentions.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/inutile-de-creer-des-conventions-sans-automatisation",
          "pageTitle": "No point creating conventions without automation",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_juniors_un_peu_mais_pas_trop",
      "@type": "Methodology",
      "name": "Juniors, un peu mais pas trop",
      "alternateName": "Juniors, a few but not too many",
      "description": "Une question de composition d’équipe : des juniors, mais en nombre mesuré.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/juniors-un-peu-mais-pas-trop",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_juniors_un_peu_mais_pas_trop__fr_57",
          "text": "Une question de composition d’équipe : des juniors, mais en nombre mesuré.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/juniors-un-peu-mais-pas-trop",
          "pageTitle": "Juniors, un peu mais pas trop | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_juniors_un_peu_mais_pas_trop__en_58",
          "text": "A team-composition question: some juniors, but in measured numbers.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/juniors-un-peu-mais-pas-trop",
          "pageTitle": "Juniors, a few but not too many | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_la_maturite_des_equipes_et_la_discipline_est_un_processus_sache_ou_tu_es",
      "@type": "Methodology",
      "name": "La maturité des équipes et la discipline est un processus, sache où tu es",
      "alternateName": "Team maturity and discipline is a process — know where you stand",
      "description": "La maturité d’une équipe et sa discipline se construisent par étapes. Le principe invite à savoir où l’on en est.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/la-maturite-des-equipes-et-la-discipline-est-un-processus-sache-ou-tu-es",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_la_maturite_des_equipes_et_la_discipline_est_un_processus_sache_ou_tu_es__fr_59",
          "text": "La maturité d’une équipe et sa discipline se construisent par étapes. Le principe invite à savoir où l’on en est.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/la-maturite-des-equipes-et-la-discipline-est-un-processus-sache-ou-tu-es",
          "pageTitle": "Maturité et discipline des équipes : sache où tu en es",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_la_maturite_des_equipes_et_la_discipline_est_un_processus_sache_ou_tu_es__en_60",
          "text": "A team’s maturity and discipline are built step by step. The principle asks you to know where you stand.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/la-maturite-des-equipes-et-la-discipline-est-un-processus-sache-ou-tu-es",
          "pageTitle": "Team maturity and discipline: know where you stand",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_le_bon_role_au_bon_niveau",
      "@type": "Methodology",
      "name": "Le bon rôle au bon niveau",
      "alternateName": "The right role at the right level",
      "description": "Chaque rôle a son niveau : le Tech-Lead regarde le système, l’Engineering Manager regarde les personnes.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/le-bon-role-au-bon-niveau",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_le_bon_role_au_bon_niveau__fr_61",
          "text": "Chaque rôle a son niveau : le Tech-Lead regarde le système, l’Engineering Manager regarde les personnes.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/le-bon-role-au-bon-niveau",
          "pageTitle": "Le bon rôle au bon niveau | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_le_bon_role_au_bon_niveau__en_62",
          "text": "Each role has its own level: the Tech-Lead looks at the system, the Engineering Manager looks at people.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/le-bon-role-au-bon-niveau",
          "pageTitle": "The right role at the right level | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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 : un nom descriptif, sans ambiguïté, qui se comprend seul. Un nouvel arrivant le saisit-il ?",
      "url": "https://www.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_63",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_le_nommage_doit_etre_ennuyeux__en_64",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_le_package_daccueil_pour_les_nouveaux_arrivants",
      "@type": "Methodology",
      "name": "Le package d'accueil pour les nouveaux arrivants",
      "alternateName": "The onboarding package for newcomers",
      "description": "Préparer l’accueil d’un nouvel arrivant : environnement, premier ticket, et éléments concrets pour qu’il se sente attendu dès le premier jour.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/le-package-daccueil-pour-les-nouveaux-arrivants",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_le_package_daccueil_pour_les_nouveaux_arrivants__fr_65",
          "text": "Préparer l’accueil d’un nouvel arrivant : environnement, premier ticket, et éléments concrets pour qu’il se sente attendu dès le premier jour.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/le-package-daccueil-pour-les-nouveaux-arrivants",
          "pageTitle": "Le package d'accueil pour les nouveaux arrivants",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_le_package_daccueil_pour_les_nouveaux_arrivants__en_66",
          "text": "Prepare a newcomer’s arrival: environment, first ticket, and concrete touches so they feel expected from day one.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/le-package-daccueil-pour-les-nouveaux-arrivants",
          "pageTitle": "The onboarding package for newcomers | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_67",
          "text": "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.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/le-ratio-production-consommation",
          "pageTitle": "Le ratio production/consommation | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_le_ratio_production_consommation__en_68",
          "text": "The production/consumption ratio compares what you produce with what you consume, at work and in life. A principle that invites introspection.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/le-ratio-production-consommation",
          "pageTitle": "The production/consumption ratio | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_lentrepreneuriat_nest_pas_un_sprint_mais_un_marathon",
      "@type": "Methodology",
      "name": "L'entrepreneuriat n'est pas un sprint mais un marathon",
      "alternateName": "Entrepreneurship is a marathon, not a sprint",
      "description": "L’entrepreneuriat se joue sur la durée. Le rôle se tient sur des années : on le gère comme un marathon, sans s’épuiser.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/lentrepreneuriat-nest-pas-un-sprint-mais-un-marathon",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_lentrepreneuriat_nest_pas_un_sprint_mais_un_marathon__fr_69",
          "text": "L’entrepreneuriat se joue sur la durée. Le rôle se tient sur des années : on le gère comme un marathon, sans s’épuiser.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/lentrepreneuriat-nest-pas-un-sprint-mais-un-marathon",
          "pageTitle": "L'entrepreneuriat n'est pas un sprint mais un marathon",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_lentrepreneuriat_nest_pas_un_sprint_mais_un_marathon__en_70",
          "text": "Entrepreneurship plays out over time. The role lasts years: manage it like a marathon, without burning out.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/lentrepreneuriat-nest-pas-un-sprint-mais-un-marathon",
          "pageTitle": "Entrepreneurship is a marathon, not a sprint | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_lentreprise_est_une_plateforme_sur_laquelle_reposent_les_equipes",
      "@type": "Methodology",
      "name": "L'entreprise est une plateforme sur laquelle reposent les équipes",
      "alternateName": "The company is a platform the teams stand on",
      "description": "L’entreprise joue le rôle d’une plateforme sur laquelle reposent les équipes. Un principe d’organisation voisin de la loi de Conway inversée.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/lentreprise-est-une-plateforme-sur-laquelle-reposent-les-equipes",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_lentreprise_est_une_plateforme_sur_laquelle_reposent_les_equipes__fr_71",
          "text": "L’entreprise joue le rôle d’une plateforme sur laquelle reposent les équipes. Un principe d’organisation voisin de la loi de Conway inversée.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/lentreprise-est-une-plateforme-sur-laquelle-reposent-les-equipes",
          "pageTitle": "L'entreprise, une plateforme pour ses équipes | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_lentreprise_est_une_plateforme_sur_laquelle_reposent_les_equipes__en_72",
          "text": "The company acts as a platform the teams stand on. An organizational principle close to the inverse Conway’s law.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/lentreprise-est-une-plateforme-sur-laquelle-reposent-les-equipes",
          "pageTitle": "The company is a platform the teams stand on | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_lentreprise_nest_quun_des_clients_de_son_produit",
      "@type": "Methodology",
      "name": "L'entreprise n'est qu'un des clients de son produit",
      "alternateName": "The company is only one of its product’s customers",
      "description": "L’entreprise n’est qu’un client parmi d’autres de son produit. Le principe aide à trier les demandes, dont les développements spécifiques à un seul client.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/lentreprise-nest-quun-des-clients-de-son-produit",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_lentreprise_nest_quun_des_clients_de_son_produit__fr_73",
          "text": "L’entreprise n’est qu’un client parmi d’autres de son produit. Le principe aide à trier les demandes, dont les développements spécifiques à un seul client.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/lentreprise-nest-quun-des-clients-de-son-produit",
          "pageTitle": "L'entreprise n'est qu'un des clients de son produit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_lentreprise_nest_quun_des_clients_de_son_produit__en_74",
          "text": "The company is only one customer among others of its product. The principle helps sort requests, including client-specific developments.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/lentreprise-nest-quun-des-clients-de-son-produit",
          "pageTitle": "The company is only one of its product’s customers",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_les_1_a_1_comme_outil_managerial",
      "@type": "Methodology",
      "name": "Les 1 à 1 comme outil managérial",
      "alternateName": "1-on-1s as a management tool",
      "description": "Les entretiens individuels servent à faire progresser chacun dans l’équipe. Un outil de management que le Tech-Lead évite de laisser sauter.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/les-1-a-1-comme-outil-managerial",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_les_1_a_1_comme_outil_managerial__fr_75",
          "text": "Les entretiens individuels servent à faire progresser chacun dans l’équipe. Un outil de management que le Tech-Lead évite de laisser sauter.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/les-1-a-1-comme-outil-managerial",
          "pageTitle": "Les 1 à 1 comme outil managérial | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_les_1_a_1_comme_outil_managerial__en_76",
          "text": "One-on-ones help each person in the team grow. A management tool the Tech-Lead avoids letting slip.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/les-1-a-1-comme-outil-managerial",
          "pageTitle": "1-on-1s as a management tool | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_les_bouchons_sont_un_ennemi",
      "@type": "Methodology",
      "name": "Les bouchons sont un ennemi",
      "alternateName": "Bottlenecks are the enemy",
      "description": "Un goulot freine toute l’équipe, y compris quand c’est vous. Une validation qui attend toujours la même personne en est un.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/les-bouchons-sont-un-ennemi",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_les_bouchons_sont_un_ennemi__fr_77",
          "text": "Un goulot freine toute l’équipe, y compris quand c’est vous. Une validation qui attend toujours la même personne en est un.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/les-bouchons-sont-un-ennemi",
          "pageTitle": "Les bouchons sont un ennemi | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_les_bouchons_sont_un_ennemi__en_78",
          "text": "A bottleneck slows the whole team, even when it is you. A sign-off that always waits for the same person is one.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/les-bouchons-sont-un-ennemi",
          "pageTitle": "Bottlenecks are the enemy | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_les_equipes_pointent_sur_la_production_des_autres",
      "@type": "Methodology",
      "name": "Les équipes pointent sur la production des autres",
      "alternateName": "Teams are on call for each other’s production",
      "description": "Quand une équipe branche ses dépendances sur l’environnement de préproduction d’une autre, elle crée un couplage organisationnel à éviter.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/les-equipes-pointent-sur-la-production-des-autres",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_les_equipes_pointent_sur_la_production_des_autres__fr_79",
          "text": "Quand une équipe branche ses dépendances sur l’environnement de préproduction d’une autre, elle crée un couplage organisationnel à éviter.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/les-equipes-pointent-sur-la-production-des-autres",
          "pageTitle": "Les équipes pointent sur la production des autres",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_les_equipes_pointent_sur_la_production_des_autres__en_80",
          "text": "When one team points its dependencies at another team’s pre-production environment, it creates organizational coupling worth avoiding.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/les-equipes-pointent-sur-la-production-des-autres",
          "pageTitle": "Teams are on call for each other’s production | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_les_interfaces_graphiques_en_tant_que_machines_detats_finis",
      "@type": "Methodology",
      "name": "Les interfaces graphiques en tant que machines d'états finis",
      "alternateName": "Graphical user interfaces as finite-state machines",
      "description": "Modéliser une interface graphique comme une machine à états finis, avec un état explicite, par exemple porté par l’URL.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/les-interfaces-graphiques-en-tant-que-machines-detats-finis",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_les_interfaces_graphiques_en_tant_que_machines_detats_finis__fr_81",
          "text": "Modéliser une interface graphique comme une machine à états finis, avec un état explicite, par exemple porté par l’URL.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/les-interfaces-graphiques-en-tant-que-machines-detats-finis",
          "pageTitle": "Les interfaces graphiques en tant que machines d'états finis",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_les_interfaces_graphiques_en_tant_que_machines_detats_finis__en_82",
          "text": "Model a graphical interface as a finite-state machine with an explicit state, for example carried by the URL.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/les-interfaces-graphiques-en-tant-que-machines-detats-finis",
          "pageTitle": "Graphical user interfaces as finite-state machines",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_les_trolls_un_indicateur_de_letat_de_sante_de_la_culture_interne",
      "@type": "Methodology",
      "name": "Les trolls, un indicateur de l’état de santé de la culture interne",
      "alternateName": "Trolls, an indicator of internal culture health",
      "description": "Les trolls sont un indicateur de l’état de santé de la culture interne. Le principe invite à les lire comme un signal.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/les-trolls-un-indicateur-de-letat-de-sante-de-la-culture-interne",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_les_trolls_un_indicateur_de_letat_de_sante_de_la_culture_interne__fr_83",
          "text": "Les trolls sont un indicateur de l’état de santé de la culture interne. Le principe invite à les lire comme un signal.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/les-trolls-un-indicateur-de-letat-de-sante-de-la-culture-interne",
          "pageTitle": "Les trolls, indicateur de santé de la culture interne",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_les_trolls_un_indicateur_de_letat_de_sante_de_la_culture_interne__en_84",
          "text": "Trolls are an indicator of the health of the internal culture. The principle invites you to read them as a signal.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/les-trolls-un-indicateur-de-letat-de-sante-de-la-culture-interne",
          "pageTitle": "Trolls, an indicator of internal culture health | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_maintenir_lequilibre_entre_vision_produit_et_technique",
      "@type": "Methodology",
      "name": "Maintenir l'équilibre entre vision produit et technique",
      "alternateName": "Keep the balance between product and technical vision",
      "description": "Garder l’équilibre entre vision produit et vision technique est un travail continu : le Tech-Lead traduit contraintes techniques en délais, risques et coûts.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/maintenir-lequilibre-entre-vision-produit-et-technique",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_maintenir_lequilibre_entre_vision_produit_et_technique__fr_85",
          "text": "Garder l’équilibre entre vision produit et vision technique est un travail continu : le Tech-Lead traduit contraintes techniques en délais, risques et coûts.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/maintenir-lequilibre-entre-vision-produit-et-technique",
          "pageTitle": "Maintenir l'équilibre entre vision produit et technique",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_maintenir_lequilibre_entre_vision_produit_et_technique__en_86",
          "text": "Keeping product vision and technical vision in balance is ongoing work: the Tech-Lead translates technical constraints into time, risk and cost.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/maintenir-lequilibre-entre-vision-produit-et-technique",
          "pageTitle": "Keep the balance between product and technical vision",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_87",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_mettre_le_plus_de_contraintes_en_amont__en_88",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_montre_moi_ton_code_je_te_dirai_qui_tu_es",
      "@type": "Methodology",
      "name": "Montre-moi ton code, je te dirai qui tu es",
      "alternateName": "Show me your code, I’ll tell you who you are",
      "description": "Lire du code réel écrit par le candidat en dit plus long qu’un exercice au tableau.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/montre-moi-ton-code-je-te-dirai-qui-tu-es",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_montre_moi_ton_code_je_te_dirai_qui_tu_es__fr_89",
          "text": "Lire du code réel écrit par le candidat en dit plus long qu’un exercice au tableau.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/montre-moi-ton-code-je-te-dirai-qui-tu-es",
          "pageTitle": "Montre-moi ton code, je te dirai qui tu es | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_montre_moi_ton_code_je_te_dirai_qui_tu_es__en_90",
          "text": "Reading real code written by the candidate says more than a whiteboard exercise.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/montre-moi-ton-code-je-te-dirai-qui-tu-es",
          "pageTitle": "Show me your code, I’ll tell you who you are | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_91",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_ne_mets_pas_tes_noix_dans_letau__en_92",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_noubliez_pas_de_gagner_de_largent",
      "@type": "Methodology",
      "name": "N’oubliez pas de gagner de l’argent",
      "alternateName": "Don’t forget to make money",
      "description": "L’entreprise doit gagner de l’argent : une architecture élégante qui retarde la mise sur le marché n’aide personne.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/noubliez-pas-de-gagner-de-largent",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_noubliez_pas_de_gagner_de_largent__fr_93",
          "text": "L’entreprise doit gagner de l’argent : une architecture élégante qui retarde la mise sur le marché n’aide personne.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/noubliez-pas-de-gagner-de-largent",
          "pageTitle": "N’oubliez pas de gagner de l’argent | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_noubliez_pas_de_gagner_de_largent__en_94",
          "text": "The company has to make money: an elegant architecture that delays going to market helps no one.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/noubliez-pas-de-gagner-de-largent",
          "pageTitle": "Don’t forget to make money | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_orienter_le_futur_structurellement",
      "@type": "Methodology",
      "name": "Orienter le futur structurellement",
      "alternateName": "Steer the future structurally",
      "description": "Faire en sorte que la structure du code oriente les évolutions futures dans la bonne direction, notamment en pilotant la dette technique.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/orienter-le-futur-structurellement",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_orienter_le_futur_structurellement__fr_95",
          "text": "Faire en sorte que la structure du code oriente les évolutions futures dans la bonne direction, notamment en pilotant la dette technique.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/orienter-le-futur-structurellement",
          "pageTitle": "Orienter le futur structurellement | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_orienter_le_futur_structurellement__en_96",
          "text": "Make the structure of the code steer future changes in the right direction, notably by managing technical debt.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/orienter-le-futur-structurellement",
          "pageTitle": "Steer the future structurally | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_partir_du_constat_que_ca_va_merder_tot_ou_tard",
      "@type": "Methodology",
      "name": "Partir du constat que ça va merder tôt ou tard",
      "alternateName": "Start from the assumption that it will break sooner or later",
      "description": "Tout système finit par tomber en panne. La question est de savoir si l’équipe l’apprend par une alerte ou par un client mécontent.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/partir-du-constat-que-ca-va-merder-tot-ou-tard",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_partir_du_constat_que_ca_va_merder_tot_ou_tard__fr_97",
          "text": "Tout système finit par tomber en panne. La question est de savoir si l’équipe l’apprend par une alerte ou par un client mécontent.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/partir-du-constat-que-ca-va-merder-tot-ou-tard",
          "pageTitle": "Partir du constat que ça va merder tôt ou tard | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_partir_du_constat_que_ca_va_merder_tot_ou_tard__en_98",
          "text": "Every system eventually fails. The question is whether the team finds out from an alert or from an unhappy customer.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/partir-du-constat-que-ca-va-merder-tot-ou-tard",
          "pageTitle": "Start from the assumption that it will break sooner or later",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_pas_de_monitoring_sans_lalerting",
      "@type": "Methodology",
      "name": "Pas de monitoring sans l'alerting",
      "alternateName": "No monitoring without alerting",
      "description": "Le monitoring mesure l’état du système, l’alerting prévient quand ça dérape. Isolés l’un de l’autre, ils ne servent à rien.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/pas-de-monitoring-sans-lalerting",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_pas_de_monitoring_sans_lalerting__fr_99",
          "text": "Le monitoring mesure l’état du système, l’alerting prévient quand ça dérape. Isolés l’un de l’autre, ils ne servent à rien.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/pas-de-monitoring-sans-lalerting",
          "pageTitle": "Pas de monitoring sans l'alerting | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_pas_de_monitoring_sans_lalerting__en_100",
          "text": "Monitoring measures the state of the system, alerting warns you when it goes wrong. Taken separately, neither is of any use.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/pas-de-monitoring-sans-lalerting",
          "pageTitle": "No monitoring without alerting | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_plus_nest_pas_mieux",
      "@type": "Methodology",
      "name": "Plus n'est pas mieux",
      "alternateName": "More is not better",
      "description": "Ajouter des personnes n’accélère pas forcément un projet. Retours de la communauté : petites équipes, Skype face à WhatsApp, loi d’Amdahl.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/plus-nest-pas-mieux",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_plus_nest_pas_mieux__fr_101",
          "text": "Ajouter des personnes n’accélère pas forcément un projet. Retours de la communauté : petites équipes, Skype face à WhatsApp, loi d’Amdahl.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/plus-nest-pas-mieux",
          "pageTitle": "Plus n'est pas mieux | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_plus_nest_pas_mieux__en_102",
          "text": "Adding people does not necessarily speed a project up. Community feedback: small teams, Skype versus WhatsApp, Amdahl’s law.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/plus-nest-pas-mieux",
          "pageTitle": "More is not better | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_poser_un_cadre_mais_pas_de_limites",
      "@type": "Methodology",
      "name": "Poser un cadre mais pas de limites",
      "alternateName": "Set a frame but no limits",
      "description": "Un cadre clair donne de la liberté, des zones floues créent des conflits. Poser le cadre, c’est dire ce que chacun décide seul et à plusieurs.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/poser-un-cadre-mais-pas-de-limites",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_poser_un_cadre_mais_pas_de_limites__fr_103",
          "text": "Un cadre clair donne de la liberté, des zones floues créent des conflits. Poser le cadre, c’est dire ce que chacun décide seul et à plusieurs.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/poser-un-cadre-mais-pas-de-limites",
          "pageTitle": "Poser un cadre mais pas de limites | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_poser_un_cadre_mais_pas_de_limites__en_104",
          "text": "A clear frame gives freedom, blurry areas create conflict. Setting the frame means saying what each person decides alone and what is decided together.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/poser-un-cadre-mais-pas-de-limites",
          "pageTitle": "Set a frame but no limits | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_105",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_preferer_le_declaratif_sur_limperatif__en_106",
          "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://www.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-30T18:20:51Z",
          "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://www.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_107",
          "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://www.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-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_preferer_lexplicite_a_limplicite__en_108",
          "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://www.getnobullshit.com/en/tech-lead/preferer-lexplicite-a-limplicite",
          "pageTitle": "Prefer explicit over implicit | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_prendre_conscience_de_la_dette_subie_et_dompter_la_dette_choisie",
      "@type": "Methodology",
      "name": "Prendre conscience de la dette subie et dompter la dette choisie",
      "alternateName": "Acknowledge inherited debt and tame chosen debt",
      "description": "La dette technique est le coût futur des raccourcis d’aujourd’hui. Subie, on la rend visible ; choisie, on l’écrit, la date et la rembourse.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/prendre-conscience-de-la-dette-subie-et-dompter-la-dette-choisie",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_prendre_conscience_de_la_dette_subie_et_dompter_la_dette_choisie__fr_109",
          "text": "La dette technique est le coût futur des raccourcis d’aujourd’hui. Subie, on la rend visible ; choisie, on l’écrit, la date et la rembourse.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/prendre-conscience-de-la-dette-subie-et-dompter-la-dette-choisie",
          "pageTitle": "Dette subie, dette choisie : la voir et la dompter",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_prendre_conscience_de_la_dette_subie_et_dompter_la_dette_choisie__en_110",
          "text": "Technical debt is the future cost of today’s shortcuts. Inherited, make it visible; chosen, write it down, date it and pay it back.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/prendre-conscience-de-la-dette-subie-et-dompter-la-dette-choisie",
          "pageTitle": "Acknowledge inherited debt and tame chosen debt | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_prequalifier_en_une_question",
      "@type": "Methodology",
      "name": "Préqualifier en une question",
      "alternateName": "Pre-qualify in a single question",
      "description": "Un principe de recrutement : préqualifier en une seule question.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/prequalifier-en-une-question",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_prequalifier_en_une_question__fr_111",
          "text": "Un principe de recrutement : préqualifier en une seule question.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/prequalifier-en-une-question",
          "pageTitle": "Préqualifier en une question | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_prequalifier_en_une_question__en_112",
          "text": "A hiring principle: pre-qualify with a single question.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/prequalifier-en-une-question",
          "pageTitle": "Pre-qualify in a single question | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_quand_monter_en_competence_quand_partir_sur_ses_competences_existantes_pour_faire_du_run",
      "@type": "Methodology",
      "name": "Quand monter en compétence",
      "alternateName": "When to level up your skills",
      "description": "Choisir entre monter en compétence et partir sur ses compétences existantes pour faire du run.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/quand-monter-en-competence-quand-partir-sur-ses-competences-existantes-pour-faire-du-run",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_quand_monter_en_competence_quand_partir_sur_ses_competences_existantes_pour_faire_du_run__fr_113",
          "text": "Choisir entre monter en compétence et partir sur ses compétences existantes pour faire du run.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/quand-monter-en-competence-quand-partir-sur-ses-competences-existantes-pour-faire-du-run",
          "pageTitle": "Quand monter en compétence | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_quand_monter_en_competence_quand_partir_sur_ses_competences_existantes_pour_faire_du_run__en_114",
          "text": "Choose between building new skills and relying on the ones you already have to run things.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/quand-monter-en-competence-quand-partir-sur-ses-competences-existantes-pour-faire-du-run",
          "pageTitle": "When to level up your skills | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_rendre_le_pouvoir_aux_metier",
      "@type": "Methodology",
      "name": "Rendre le pouvoir aux métiers",
      "alternateName": "Give the power back to the business",
      "description": "Donner aux métiers la main sur ce qui les concerne (configuration, règles, contenus) libère l’équipe technique.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/rendre-le-pouvoir-aux-metier",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_rendre_le_pouvoir_aux_metier__fr_115",
          "text": "Donner aux métiers la main sur ce qui les concerne (configuration, règles, contenus) libère l’équipe technique.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/rendre-le-pouvoir-aux-metier",
          "pageTitle": "Rendre le pouvoir aux métiers | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_rendre_le_pouvoir_aux_metier__en_116",
          "text": "Giving the business control over what concerns them (configuration, rules, content) frees the technical team.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/rendre-le-pouvoir-aux-metier",
          "pageTitle": "Give the power back to the business | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_rester_coherent_dans_lerreur",
      "@type": "Methodology",
      "name": "Rester cohérent dans l'erreur",
      "alternateName": "Stay consistent even in error",
      "description": "Un principe de développement : rester cohérent, même quand on se trompe.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/rester-coherent-dans-lerreur",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_rester_coherent_dans_lerreur__fr_117",
          "text": "Un principe de développement : rester cohérent, même quand on se trompe.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/rester-coherent-dans-lerreur",
          "pageTitle": "Rester cohérent dans l'erreur | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_rester_coherent_dans_lerreur__en_118",
          "text": "A development principle: stay consistent, even when you are wrong.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/rester-coherent-dans-lerreur",
          "pageTitle": "Stay consistent even in error | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_separer_les_interets",
      "@type": "Methodology",
      "name": "Séparer les intérêts",
      "alternateName": "Separate concerns",
      "description": "Chaque module porte une seule responsabilité et n’empiète pas sur les autres : c’est la séparation des préoccupations (SoC).",
      "url": "https://www.getnobullshit.com/fr/tech-lead/separer-les-interets",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_separer_les_interets__fr_119",
          "text": "Chaque module porte une seule responsabilité et n’empiète pas sur les autres : c’est la séparation des préoccupations (SoC).",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/separer-les-interets",
          "pageTitle": "Séparer les intérêts | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_separer_les_interets__en_120",
          "text": "Each module carries a single responsibility and does not encroach on the others: this is separation of concerns (SoC).",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/separer-les-interets",
          "pageTitle": "Separate concerns | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_si_il_y_a_besoin_dune_formation_cest_mal_pense",
      "@type": "Methodology",
      "name": "Si il y a besoin d’une formation : c’est mal pensé",
      "alternateName": "If it needs training: it’s badly designed",
      "description": "Un logiciel qui demande une formation pour être utilisé est souvent mal pensé : c’est la conception qu’il faut interroger.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/si-il-y-a-besoin-dune-formation-cest-mal-pense",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_si_il_y_a_besoin_dune_formation_cest_mal_pense__fr_121",
          "text": "Un logiciel qui demande une formation pour être utilisé est souvent mal pensé : c’est la conception qu’il faut interroger.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/si-il-y-a-besoin-dune-formation-cest-mal-pense",
          "pageTitle": "Si il y a besoin d’une formation : c’est mal pensé",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_si_il_y_a_besoin_dune_formation_cest_mal_pense__en_122",
          "text": "Software that needs training to be used is often badly designed: it is the design that deserves questioning.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/si-il-y-a-besoin-dune-formation-cest-mal-pense",
          "pageTitle": "If it needs training: it’s badly designed | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_si_tu_as_un_environnement_uat_tas_rate_ton_produit",
      "@type": "Methodology",
      "name": "Si tu as un environnement UAT, t'as raté ton produit",
      "alternateName": "If you have a UAT environment, you’ve failed your product",
      "description": "Selon ce principe, avoir besoin d’un environnement de recette utilisateur (UAT) signale souvent un produit mal pensé.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/si-tu-as-un-environnement-uat-tas-rate-ton-produit",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_si_tu_as_un_environnement_uat_tas_rate_ton_produit__fr_123",
          "text": "Selon ce principe, avoir besoin d’un environnement de recette utilisateur (UAT) signale souvent un produit mal pensé.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/si-tu-as-un-environnement-uat-tas-rate-ton-produit",
          "pageTitle": "Si tu as un environnement UAT, t'as raté ton produit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_si_tu_as_un_environnement_uat_tas_rate_ton_produit__en_124",
          "text": "According to this principle, needing a user acceptance testing (UAT) environment often signals a badly designed product.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/si-tu-as-un-environnement-uat-tas-rate-ton-produit",
          "pageTitle": "If you have a UAT environment, you’ve failed your product",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_sortir_des_competences_developper_un_metier_2",
      "@type": "Methodology",
      "name": "Sortir des compétences, développer un métier",
      "alternateName": "Move beyond skills, build a craft",
      "description": "Aller au-delà des compétences techniques pour développer un métier, par exemple en formant les développeurs à l’UX.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/sortir-des-competences-developper-un-metier-2",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_sortir_des_competences_developper_un_metier_2__fr_125",
          "text": "Aller au-delà des compétences techniques pour développer un métier, par exemple en formant les développeurs à l’UX.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/sortir-des-competences-developper-un-metier-2",
          "pageTitle": "Sortir des compétences, développer un métier | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_sortir_des_competences_developper_un_metier_2__en_126",
          "text": "Go beyond technical skills to build a craft, for example by training developers in UX.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/sortir-des-competences-developper-un-metier-2",
          "pageTitle": "Move beyond skills, build a craft | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_source_de_verite_unique",
      "@type": "Methodology",
      "name": "Source de vérité unique",
      "alternateName": "Single source of truth",
      "description": "Une seule donnée fait foi (SSoT). Dupliquée dans plusieurs systèmes, l’information finit par diverger.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/source-de-verite-unique",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_source_de_verite_unique__fr_127",
          "text": "Une seule donnée fait foi (SSoT). Dupliquée dans plusieurs systèmes, l’information finit par diverger.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/source-de-verite-unique",
          "pageTitle": "Source de vérité unique | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_source_de_verite_unique__en_128",
          "text": "A single piece of data is authoritative (SSoT). Duplicated across several systems, information ends up diverging.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/source-de-verite-unique",
          "pageTitle": "Single source of truth | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_surveiller_du_point_de_vue_utilisateur",
      "@type": "Methodology",
      "name": "Surveiller du point de vue utilisateur",
      "alternateName": "Monitor from the user’s point of view",
      "description": "Mesurer ce que vit l’utilisateur, au-delà de la charge CPU : par exemple avec du monitoring synthétique qui rejoue un parcours.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/surveiller-du-point-de-vue-utilisateur",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_surveiller_du_point_de_vue_utilisateur__fr_129",
          "text": "Mesurer ce que vit l’utilisateur, au-delà de la charge CPU : par exemple avec du monitoring synthétique qui rejoue un parcours.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/surveiller-du-point-de-vue-utilisateur",
          "pageTitle": "Surveiller du point de vue utilisateur | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_surveiller_du_point_de_vue_utilisateur__en_130",
          "text": "Measure what the user experiences, beyond CPU load: for example with synthetic monitoring that replays a user journey.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/surveiller-du-point-de-vue-utilisateur",
          "pageTitle": "Monitor from the user’s point of view | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_tout_limiter_dans_lespace_et_dans_le_temps",
      "@type": "Methodology",
      "name": "Tout limiter dans l'espace et dans le temps",
      "alternateName": "Limit everything in space and time",
      "description": "Limiter la taille des changements et la durée des chantiers garde le flux de livraison fluide.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/tout-limiter-dans-lespace-et-dans-le-temps",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_tout_limiter_dans_lespace_et_dans_le_temps__fr_131",
          "text": "Limiter la taille des changements et la durée des chantiers garde le flux de livraison fluide.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/tout-limiter-dans-lespace-et-dans-le-temps",
          "pageTitle": "Tout limiter dans l'espace et dans le temps | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_tout_limiter_dans_lespace_et_dans_le_temps__en_132",
          "text": "Limiting the size of changes and the length of projects keeps the delivery flow smooth.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/tout-limiter-dans-lespace-et-dans-le-temps",
          "pageTitle": "Limit everything in space and time | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_toutes_les_constantes_doivent_etre_configurables",
      "@type": "Methodology",
      "name": "Toutes les constantes doivent être configurables",
      "alternateName": "Every constant must be configurable",
      "description": "Aucune constante ne reste figée dans le code : toutes doivent pouvoir se configurer.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/toutes-les-constantes-doivent-etre-configurables",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_toutes_les_constantes_doivent_etre_configurables__fr_133",
          "text": "Aucune constante ne reste figée dans le code : toutes doivent pouvoir se configurer.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/toutes-les-constantes-doivent-etre-configurables",
          "pageTitle": "Toutes les constantes doivent être configurables",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_toutes_les_constantes_doivent_etre_configurables__en_134",
          "text": "No constant stays frozen in the code: every one of them must be configurable.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/toutes-les-constantes-doivent-etre-configurables",
          "pageTitle": "Every constant must be configurable | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_utiliser_le_map_reduce_humain_avec_parcimonie",
      "@type": "Methodology",
      "name": "Utiliser le map/reduce humain avec parcimonie",
      "alternateName": "Use human map/reduce sparingly",
      "description": "Répartir un travail entre plusieurs personnes (map) puis consolider (reduce) fonctionne, mais la coordination coûte cher.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/utiliser-le-map-reduce-humain-avec-parcimonie",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_utiliser_le_map_reduce_humain_avec_parcimonie__fr_135",
          "text": "Répartir un travail entre plusieurs personnes (map) puis consolider (reduce) fonctionne, mais la coordination coûte cher.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/utiliser-le-map-reduce-humain-avec-parcimonie",
          "pageTitle": "Utiliser le map/reduce humain avec parcimonie | NoBullshit",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_utiliser_le_map_reduce_humain_avec_parcimonie__en_136",
          "text": "Spreading work across several people (map) then consolidating it (reduce) works, but coordination is expensive.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/utiliser-le-map-reduce-humain-avec-parcimonie",
          "pageTitle": "Use human map/reduce sparingly | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    },
    {
      "entityId": "e_principle_votre_marque_est_votre_design_system",
      "@type": "Methodology",
      "name": "Votre marque est votre design system",
      "alternateName": "Your brand is your design system",
      "description": "Un principe produit : la marque et le design system ne font qu’un.",
      "url": "https://www.getnobullshit.com/fr/tech-lead/votre-marque-est-votre-design-system",
      "relations": [
        {
          "predicate": "PART_OF",
          "targetId": "e_book",
          "targetName": "NoBullshit Tech-Lead"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_principle_votre_marque_est_votre_design_system__fr_137",
          "text": "Un principe produit : la marque et le design system ne font qu’un.",
          "sourceUrl": "https://www.getnobullshit.com/fr/tech-lead/votre-marque-est-votre-design-system",
          "pageTitle": "Votre marque est votre design system | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_principle_votre_marque_est_votre_design_system__en_138",
          "text": "A product principle: the brand and the design system are one and the same.",
          "sourceUrl": "https://www.getnobullshit.com/en/tech-lead/votre-marque-est-votre-design-system",
          "pageTitle": "Your brand is your design system | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#ssot",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_source_de_verite_unique",
          "targetName": "Source de vérité unique"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_ssot__fr_139",
          "text": "Une seule donnée fait foi. On évite de dupliquer l’information dans plusieurs systèmes qui finissent par diverger.",
          "sourceUrl": "https://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_ssot__en_140",
          "text": "One piece of data is authoritative. We avoid duplicating information across systems that eventually diverge.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#soc",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_separer_les_interets",
          "targetName": "Séparer les intérêts"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_soc__fr_141",
          "text": "Séparer les responsabilités : chaque module fait une chose et la fait bien, sans empiéter sur les autres.",
          "sourceUrl": "https://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_soc__en_142",
          "text": "Separating responsibilities: each module does one thing well, without stepping on the others.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#dette-technique",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_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_143",
          "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://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_dette_technique__en_144",
          "text": "The future cost of shortcuts taken today. Distinguish suffered debt (you absorb it) from chosen debt (you steer it).",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#library-first",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_favoriser_approche_library_first",
          "targetName": "Favoriser l'approche library-first"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_library_first__fr_145",
          "text": "Concevoir d’abord une bibliothèque réutilisable, puis l’application autour. On favorise la réutilisation et les interfaces propres.",
          "sourceUrl": "https://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_library_first__en_146",
          "text": "Design a reusable library first, then the application around it. Favors reuse and clean interfaces.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#map-reduce-humain",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_utiliser_le_map_reduce_humain_avec_parcimonie",
          "targetName": "Utiliser le map/reduce humain avec parcimonie"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_map_reduce_humain__fr_147",
          "text": "Distribuer un travail entre plusieurs personnes (map) puis consolider (reduce). Puissant, mais coûteux en coordination : à utiliser avec parcimonie.",
          "sourceUrl": "https://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_map_reduce_humain__en_148",
          "text": "Distribute work across people (map) then consolidate (reduce). Powerful but costly in coordination: use sparingly.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#go-for-the-edge",
      "relations": [],
      "hasChunks": [
        {
          "chunkId": "e_term_go_for_the_edge__fr_149",
          "text": "Traiter les cas limites tôt. Ce sont eux qui révèlent les vrais problèmes de conception.",
          "sourceUrl": "https://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_go_for_the_edge__en_150",
          "text": "Tackle edge cases early. They reveal the real design problems.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#loi-de-conway",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_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_151",
          "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://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_loi_de_conway__en_152",
          "text": "A system’s architecture mirrors the organization that builds it. Inverting it means structuring teams to get the architecture you want.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#uat",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_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_153",
          "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://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_uat__en_154",
          "text": "User acceptance environment. In the book: if you need one, it’s often a sign of a poorly designed product.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.getnobullshit.com/fr/glossaire#monitoring-alerting",
      "relations": [
        {
          "predicate": "DESCRIBED_BY",
          "targetId": "e_principle_pas_de_monitoring_sans_lalerting",
          "targetName": "Pas de monitoring sans l'alerting"
        }
      ],
      "hasChunks": [
        {
          "chunkId": "e_term_monitoring_alerting__fr_155",
          "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://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_monitoring_alerting__en_156",
          "text": "Measure the system’s state (monitoring) and get notified when it goes wrong (alerting). One without the other is useless.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "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://www.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_157",
          "text": "Décrire le résultat voulu (déclaratif) plutôt que la suite d’étapes (impératif). Plus lisible, plus robuste.",
          "sourceUrl": "https://www.getnobullshit.com/fr/glossaire",
          "pageTitle": "Glossaire | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        },
        {
          "chunkId": "e_term_declaratif_vs_imperatif__en_158",
          "text": "Describe the desired result (declarative) rather than the sequence of steps (imperative). More readable, more robust.",
          "sourceUrl": "https://www.getnobullshit.com/en/glossary",
          "pageTitle": "Glossary | NoBullshit Tech-Lead",
          "publisher": "NoBullshit Tech-Lead",
          "retrieved": "2026-10-30T18:20:51Z",
          "contentType": "definition"
        }
      ]
    }
  ]
}