If you've tried to follow any AI coding discussion in the last six months, you've probably felt like everyone suddenly started speaking a dialect you never signed up to learn. "Vibe coding." "Agentic workflows." "Context windows." "Prompt engineering." The jargon is multiplying faster than JavaScript frameworks, and that's saying something. Matt Pocock — who you might know from his TypeScript educ
My Hugo blog was downloading 3.6 MB of JavaScript and 40 KB of external CSS on every page load. For a static blog with mostly text and a few diagrams, that was absurd. Here is how I fixed it. HTML: 86 KB JavaScript: 3.6 MB (Mermaid + KaTeX) CSS: 40 KB (KaTeX stylesheets) Problem: render-blocking scripts loaded on every page for math and diagrams Adding minifyOutput = true to hugo.toml shrunk HTML
GitHub Copilot just got a lot more complicated — and not in a good way. If you tried to sign up for Copilot Pro recently and hit a wall, that's not a bug. GitHub quietly paused new sign-ups for Copilot Pro, Pro+, and Student plans starting in late April 2026. No end date announced. No workaround offered. Just a message and a door that won't open. That alone would be worth covering. But they made t
Anthropic now ships at least three different memory models inside the Claude product family, and they don't behave the same way. Claude.ai has a chat memory feature for Pro, Max, Team, and Enterprise users that summarizes prior conversations and injects that summary into new chats. Claude Code has CLAUDE.md files plus a separate "auto memory" directory the model writes to itself, both loaded at se
Optimisation HLS pour DOMTOM Ce dépôt documente une approche orientée ingénierie réseau pour optimiser la distribution HLS (HTTP Live Streaming) dans les territoires DOMTOM. L’objectif est d’améliorer la stabilité de lecture, la latence effective et la robustesse face aux variations de gigue, tout en respectant les contraintes de décodage client, de parsing de manifestes, et de routage ISP. Pers
Contournement du flux vidéo FAI DOMTOM — FAQ Développeur (réseau, protocoles, parsing) Point de vue : cette FAQ est rédigée du point de vue d’un ingénieur logiciel/réseau traitant la couche transport, le routage ISP, la signalisation de session et la reconstruction applicative (parsing, dé-multiplexage, adaptation de manifestes), spécifiquement dans des contextes DOM-TOM où les chemins d’achemi