[{"data":1,"prerenderedAt":183},["ShallowReactive",2],{"index":3,"/articles/opus-4-8-fr":38,"/articles/opus-4-8-fr-surround":157},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":5,"title":7,"description":8,"informations":9,"_id":32,"_type":33,"_source":34,"_file":35,"_stem":36,"_extension":37},"/","",false,"Pierre Graef - Data Engineer","Pierre Graef — Data Engineer specializing in ETL pipelines, cloud integration, and scalable data architectures. Proficient in Python, SQL, Spark, and Airflow.",{"name":10,"job":11,"availability":12,"email":13,"link":14,"profile":18,"skills":20,"description":21,"experience":22},"Pierre Graef","Data Engineer",true,"graef.pierre@gmail.com",{"x":5,"linkedin":15,"instagram":5,"github":16,"kaggle":17},"https://www.linkedin.com/in/pierre-graef","https://github.com/PierreGR7","https://www.kaggle.com/pierregraef",{"url":19},"/img/profil.png","Python | SQL | Spark | Airflow","I am a Data Engineer specializing in data architecture, ETL pipelines, and cloud integration. Proficient in Python, SQL, Spark, Airflow, I design scalable data systems, optimize workflows, and build insightful dashboards with Power BI. With international experience, I transform complex datasets into actionable business solutions.",[23,27],{"company":24,"role":11,"period":25,"location":26},"CeA","2024 – Present","Strasbourg, France",{"company":28,"role":29,"period":30,"location":31},"Munich Re","Intern Data Analyst",2024,"Munich, Germany","content:index.yml","yaml","content","index.yml","index","yml",{"_path":39,"_dir":40,"_draft":6,"_partial":6,"_locale":5,"title":41,"description":42,"authors":43,"image":46,"date":48,"lang":49,"translationPath":50,"body":51,"_type":152,"_id":153,"_source":34,"_file":154,"_stem":155,"_extension":156},"/articles/opus-4-8-fr","articles","Opus 4.8 — Savoir ce qu'il ne sait pas","Un court avis sur ce qui change vraiment avec Opus 4.8 — moins de conclusions forcées, plus d'honnêteté sur ses propres limites.",[44],{"name":10,"to":15,"avatar":45},{"src":19},{"src":47},"/img/article_opus/cover.svg","2026-06-01T01:00:00.000Z","fr","/articles/opus-4-8",{"type":52,"children":53,"toc":146},"root",[54,62,83,90,95,107,113,118,130,136,141],{"type":55,"tag":56,"props":57,"children":58},"element","p",{},[59],{"type":60,"value":61},"text","J'utilise beaucoup de LLM comme outil quotidien pour mon travail sur la donnée. La plupart partagent le même défaut agaçant : quand ils n'ont pas de quoi répondre, ils répondent quand même. Ils arrondissent une pensée à moitié formée en une conclusion sûre d'elle, et on ne découvre l'erreur qu'après qu'elle nous a déjà coûté une heure.",{"type":55,"tag":56,"props":63,"children":64},{},[65,67,73,75,81],{"type":60,"value":66},"Ce qui ressort avec ",{"type":55,"tag":68,"props":69,"children":70},"strong",{},[71],{"type":60,"value":72},"Opus 4.8",{"type":60,"value":74},", c'est le réflexe inverse. Quand le problème est réellement sous-spécifié, il a tendance à ",{"type":55,"tag":76,"props":77,"children":78},"em",{},[79],{"type":60,"value":80},"le dire",{"type":60,"value":82}," plutôt qu'à masquer le trou.",{"type":55,"tag":84,"props":85,"children":87},"h2",{"id":86},"ne-pas-forcer-une-conclusion",[88],{"type":60,"value":89},"Ne pas forcer une conclusion",{"type":55,"tag":56,"props":91,"children":92},{},[93],{"type":60,"value":94},"Posez une question ambiguë et les modèles précédents vous donnaient quand même une réponse nette et tranchée — le genre qui se lit bien et s'effondre au contact du réel. Opus 4.8 accepte plus volontiers de s'arrêter à « voici ce que je peux dire, voici ce que je ne peux pas, et voici ce qui changerait la réponse ».",{"type":55,"tag":56,"props":96,"children":97},{},[98,100,105],{"type":60,"value":99},"Ça paraît anodin. En pratique, c'est la différence entre un outil qui ",{"type":55,"tag":76,"props":101,"children":102},{},[103],{"type":60,"value":104},"a l'air",{"type":60,"value":106}," utile et un outil qui l'est vraiment. Un « je n'ai pas assez d'éléments pour trancher » clair vaut mieux qu'un virage assuré dans le mur.",{"type":55,"tag":84,"props":108,"children":110},{"id":109},"plus-lucide-sur-ses-propres-manques",[111],{"type":60,"value":112},"Plus lucide sur ses propres manques",{"type":55,"tag":56,"props":114,"children":115},{},[116],{"type":60,"value":117},"L'autre évolution, c'est la conscience de ses erreurs. Il signale plus vite l'étape bancale de son raisonnement, marque une hypothèse comme une hypothèse, et pointe la partie de sa réponse la plus susceptible d'être fausse — au lieu de tout présenter avec la même certitude plate.",{"type":55,"tag":56,"props":119,"children":120},{},[121,123,128],{"type":60,"value":122},"Il n'est pas parfait sur ce point. Il dérape encore, affirme encore parfois des choses qu'il ne devrait pas. Mais la ",{"type":55,"tag":76,"props":124,"children":125},{},[126],{"type":60,"value":127},"direction",{"type":60,"value":129}," est la bonne : moins de fausse assurance bien polie, plus d'incertitude honnête.",{"type":55,"tag":84,"props":131,"children":133},{"id":132},"pourquoi-ça-compte-pour-la-donnée",[134],{"type":60,"value":135},"Pourquoi ça compte pour la donnée",{"type":55,"tag":56,"props":137,"children":138},{},[139],{"type":60,"value":140},"Dans un pipeline, une réponse fausse mais sûre d'elle est la plus coûteuse — elle passe la revue, part en prod, et casse en aval. Un modèle qui expose ses propres doutes colle à la façon dont pensent déjà les bons ingénieurs : faire confiance, mais vérifier, et savoir quelles parties vérifier en premier.",{"type":55,"tag":56,"props":142,"children":143},{},[144],{"type":60,"value":145},"Donc pas de grand verdict ici — c'est de circonstance. Je ne prétendrai pas qu'Opus 4.8 a « réglé » la fiabilité. Je dirai seulement qu'il donne l'impression d'un modèle un peu plus à l'aise avec le fait de ne pas savoir, et c'est une qualité que je prends sans hésiter face à la fausse confiance.",{"title":5,"searchDepth":147,"depth":147,"links":148},2,[149,150,151],{"id":86,"depth":147,"text":89},{"id":109,"depth":147,"text":112},{"id":132,"depth":147,"text":135},"markdown","content:articles:opus-4-8-fr.md","articles/opus-4-8-fr.md","articles/opus-4-8-fr","md",[158,173],{"_path":159,"_dir":40,"_draft":6,"_partial":6,"_locale":5,"title":160,"description":161,"authors":162,"image":165,"date":167,"lang":168,"translationPath":169,"_type":152,"_id":170,"_source":34,"_file":171,"_stem":172,"_extension":156},"/articles/fabric-couts","Microsoft Fabric — Keeping Capacity Costs Under Control","Notes from the field on monitoring and cutting the Microsoft Fabric bill — the Metrics app, smoothing, throttling, and the levers that actually move the number.",[163],{"name":10,"to":15,"avatar":164},{"src":19},{"src":166},"/img/article_fabric/cover.svg","2026-06-16T01:00:00.000Z","en","/articles/fabric-couts-fr","content:articles:fabric-couts.md","articles/fabric-couts.md","articles/fabric-couts",{"_path":50,"_dir":40,"_draft":6,"_partial":6,"_locale":5,"title":174,"description":175,"authors":176,"image":179,"date":48,"lang":168,"translationPath":39,"_type":152,"_id":180,"_source":34,"_file":181,"_stem":182,"_extension":156},"Opus 4.8 — Knowing What It Doesn't Know","A short take on what actually feels different about Opus 4.8 — fewer forced conclusions, more honesty about its own gaps.",[177],{"name":10,"to":15,"avatar":178},{"src":19},{"src":47},"content:articles:opus-4-8.md","articles/opus-4-8.md","articles/opus-4-8",1781630439689]