Artificial Intelligence The standard line is that local AI costs you twice, the machine and then the watts, and that’s true. But there’s a third bill, the only one not denominated in euros: the bill for sovereignty, which you sign silently the moment you decide to “ride it out on APIs” for two years while waiting for prices to fall. On top of that, the French watt is among the cleanest on the continent, and the memory spike you’re advised to wait out isn’t weather but a perfectly rational eviction, with no reason to correct itself on its own. A companion to tazmenworld’s buying guide, adding the line the spreadsheet forgets and a reminder that, in a world where memory goes first to wherever the margin is fattest, owning your own is already an act of resistance.
Artificial Intelligence Everyone now repeats that you should design loops instead of prompting your agents, and at its core that’s true: the loop is the real shift in AI. But these pitches consistently leave out two costs, the tokens that compound with every iteration and the heavier one, sovereignty, because the funnel always ends at a proprietary product to which you hand your keys, your data, and the power to act in your name. This article lays out plainly what a loop actually is, says when it’s a trap rather than a gain, and shows how to rebuild it entirely on your own, on your own infrastructure. Because the only question worth asking isn’t which product saves you the most time, but who owns the loop.
Artificial Intelligence On June 16, at its Compile conference, Cursor unveiled Origin, a Git forge designed no longer for humans but for the swarms of agents that push code around the clock. The press saw a GitHub competitor; the real story is the concentration that closes in when a single player brings together the compute, the model, the IDE, the forge, and your working data, a structural risk that would be identical with any other giant. Faced with this single point of control, self-hosting stops being a power user’s affectation and becomes a strategic position, provided you admit one thing: it will no longer be enough to store your repositories, you will have to run your own agent orchestrators or be sovereign but cripplingly slow. The real exit brick, then, is not just Git for the code, it is MCP for the agent, the pairing that lets an open editor restore the same power without handing everything to the dominant owner. My bet for the next three years: not a tipping point but a polarization, in which standardization remains our best way out.
Artificial Intelligence On June 12, SpaceX pulled off the largest IPO in history. Four days later it bought Cursor for $60 billion, then unveiled Origin, a Git forge built for agents. The press boiled it down to the purchase of an IDE and missed the point: one man is buying, layer by layer, the right to decide what counts as true, first in code, soon in knowledge itself. The real bottleneck is no longer producing code, it’s arbitrating what deserves to be merged, and for training agents that validation layer is worth more than all of GitHub’s public corpus combined. Yet there’s a crack in the narrative of inevitability: the keystone, Anthropic, is the one piece Musk cannot buy, even as he already supplies part of its oxygen. The real question is no longer to understand his plan, but to decide how much longer we keep renting him the future.
Artificial Intelligence US export controls were meant to strangle Chinese AI; instead they taught it frugality, and frugality became its pricing weapon. DeepSeek, Qwen, and the swarm of open-weight models now deliver good enough at a fraction of the Western price, which is all it takes to tip the overwhelming majority of use cases. But the market hasn’t tipped where people think: the absolute frontier stays American, and the real moat, distribution, already has the hyperscalers reselling the Chinese commodity on their own compute. For Europe, defaulting to the Hangzhou API means swapping one suzerain for another, when the only real exit, self-hosting open weights, is no free lunch. What remains to be seen is whether the continent will build the conditions, regulatory and industrial, that make this reflex something more than the gesture of an enlightened minority.
Artificial Intelligence On June 8, 2026, Apple unveiled the third generation of its Foundation Models, with one of the most ingenious on-device architectures on the market: AFM 3 Core Advanced stores twenty billion parameters in flash memory and activates only a few of them, routing its experts by prompt rather than by token. Yet the feat is nothing spontaneous, since it is the industrial extension of the 2023 paper “LLM in a flash” that Apple’s marketing would rather leave unmentioned. But behind the on-device brilliance sits a heavier surrender: all five models are co-designed with Google, pre-trained on its TPUs, and the most capable of them runs on NVIDIA GPUs in Google Cloud. The company that had made vertical integration and “designed by Apple” its creed now rents its cutting-edge horsepower from a competitor, precisely where it had promised the most independence. And all the while, the Digital Markets Act keeps Siri AI off Europeans’ iPhones and iPads with no timeline, a fitting illustration of a continent that excels at regulating a match it no longer plays.
Artificial Intelligence There are two ways to read the announcement of dynamic workflows in Claude Code, published on May 28. The first, the one everyone will repeat, fits in the tagline: work you used to plan in quarters now wraps up in a matter of days. The second hides in a quiet note, repeated twice in the […]
Artificial Intelligence Clients ask me to bolt an AI chatbot onto their sites all the time, and those sites run on everything: Shopify, WordPress, Drupal, sometimes abandoned custom builds. But “which plugin?” is never the right question: an AI chatbot is two layers people almost always conflate, the widget delivery and the brain that answers. The entire decision sorts onto a single scale, from locked-in turnkey where you control nothing, all the way to a pipeline you fully own. For a single client, turnkey is plenty; for an agency banking reusable knowledge across a whole fleet, owning the brain becomes an asset. Here’s the framework I use to decide, CMS by CMS, with Shopify leading the way.
Artificial Intelligence I get asked constantly to bolt an AI chatbot onto client sites, and those sites run on everything: Shopify, WordPress, Drupal, sometimes some abandoned custom build. But “which plugin?” is never the right question. An AI chatbot is really two layers that almost everyone lumps together: the delivery of the widget and the brain that does the answering. The entire decision sits on a single scale, running from the locked-down turnkey solution where you control nothing, all the way to a pipeline you own outright. For a single client, turnkey is more than enough; for an agency looking to build up reusable knowledge across a whole fleet of sites, owning the brain becomes a real asset. Here’s the framework I use to settle it, CMS by CMS, starting with Shopify.
Artificial Intelligence A RAG PoC indexing 84,000 chunks, roughly 500 MB of vectors, fits without flinching in the RAM of an M1 MacBook; and yet French SMEs are still being sold a four-service stack (Pinecone + Elasticsearch + Postgres + LangChain) that costs between €150 and €400 a month in cloud infrastructure and mobilizes three distinct technical skill sets. DuckDB, the embedded analytical library maintained since 2019 by Amsterdam’s CWI, solves the equation with a single dependency: native vector search (the vss extension), BM25 full-text search (the fts extension), standard structured SQL filters, and hybrid re-ranking in one eight-line query, all of it inside a local .duckdb file. The bottom line: a factor of 10 on infrastructure cost, a factor of 10 on latency, a factor of 5 on time to production, and not a single embedding leaving your infrastructure to end up in an American datacenter. The four-service stack taught today in 90% of RAG tutorials doesn’t exist to solve a technical problem: it exists to sell recurring SaaS, to justify DevOps engagements, and to inflate project budgets on use cases that don’t warrant it. The real value of a senior engineer in 2026 is measured by the number of lines of infrastructure he knows how to remove to solve the exact same problem, not by the number of Kubernetes microservices he knows how to stack.