One of the best applications of modern LLM-based AI is surfacing answers from the chaos of the internet. Its success can be partly attributed to our failure to build systems that organize information well in the first place.

Remember Semantic Web? The web was supposed to evolve into semantically structured, linked, machine-readable data that would enable amazing opportunities. That never happened.

The knowledge of the Internet were structured with rich semantic linking, then very primitive algorithms could parse them.

C’est la part des richesses appor­tée à chacun qu’il faut sauve­gar­der, pas le travail.

Le problème n’est pas que l’au­to­ma­ti­sa­tion retire du travail, ni même qu’on manque de richesses. Le problème c’est que l’au­to­ma­ti­sa­tion du travail modi­fie la répar­ti­tion des richesses (vers une plus grande concen­tra­tion).

Le problème n’est pas que l’au­to­ma­ti­sa­tion retire du travail, ni même qu’on manque de richesses. Le problème c’est que l’au­to­ma­ti­sa­tion du travail modi­fie la répar­ti­tion des richesses (vers une plus grande concen­tra­tion).

La société actuelle tend rester elle-même au lieu de s'adapter à cette automatisation des tâches qui libère du travail.

While copying the code, the right abstraction reveals itself.

If you start too early, you might end up with a bad abstraction that doesn’t fit the problem. You know it’s wrong because it feels clunky. Some typical symptoms include:

Removing a wrong abstraction is hard work.

Clean up afterwards :)

I totally agree.

1. When there is more than one text directionality
2. When the respective expression would be shorter than the non-logical equivalent.

The second point is healthy for every project.

En prenant pour exemple, https://www.smithsonianmag.com/smart-news/google-just-released-an-ai-tool-that-helps-historians-fill-in-missing-words-in-ancient-roman-inscriptions-180987046/

Le problème de présenter un nouvel outil sans faire aucune remise en contexte, c'est que cela donne l'impression d'un pas de géant dans le domaine impulsé par une entreprise qui n'a rien à voir avec ce domaine (Google) et qui débarquerait d'un coup avec une solution magique

On peut s'amuser à faire un peu de rétro-engineering sur la façon dont cet outil de Google fonctionne. En fait, il s'agit essentiellement d'une grosse base de données, que l'IA rend capable d'émettre des hypothèses plus rapidement.

Based on my interviews, it became clear that the students’ goal was less about reducing overall effort than it was about reducing the maximum cognitive strain required to produce prose.

[...] the Brain-only group suggests that writing without assistance most likely induced greater internally driven processing…their brains likely engaged in more internal brainstorming and semantic retrieval.

There is indeed some concerns cited by the MIT paper: reduce students' ability to retain and recall information; bypass the process of synthesizing information from memory, promote a form of metacognitive laziness and avoid the intellectual effort.

What bad patterns are encouraged by design in Rust?

• complicated types
• complicated macro
• premature optimizations with lifetimes among others

Strip away the branding and it’s embarrassingly simple. Agile is:

• Just enough structure to let teams deliver good software quickly
• A way to shorten feedback loops so you stop building the wrong thing
• A way to change direction without needing a three-month steering committee

When it works:

• Developers talking—constantly, and not just during standups
• Pair programming when it helps, not when the process says so
• Teams who own the product, including how it behaves in production
• Enough time to write proper tests and refactor without begging
• Everyone knowing what the goal is and why it matters
• A calm, steady pace—not a death march disguised as a “sprint”
• Monitoring and alerting built into the work, not bolted on later

But for now, just know this: if Agile feels exhausting, it’s not Agile. It’s cosplay.

(via https://lehollandaisvolant.net/?id=20250625054126)

C’est une leçon à retenir : innover pour innover, ça ne sert à rien. Tout retourner une façon de faire simplement pour laisser sa marque, c’est idiot et contreproductif une partie du temps (maintenant allez faire comprendre ça aux exécutifs qui se succèdent dans une entreprise et font précisément tous ça).

Johannes Link dernier explique qu’il ne s’agit pas tellement de se demander si l’IA générale arrivera ou pas, mais bien de s’interroger sur l’altruisme des milliardaires de la Tech et sur la confiance qu’on peut leur accorder. Pour ma part, je ne pense pas que nous obtiendrons une réponse intégrale non censurée, car il y a une quasi certitude qu’elle ne soit pas en faveur des milliardaires.

Oui: laisser le contrôle aux utilisateurs. Un four peut éviter les modes de cuisson "poulet", "poisson", "grâtin". En revanche, laisser les capacités de l'appareil apparente: "chaleur tournante", "grill", etc...

For reasons we'll get into later, Tailwind decided to burst on to the scene and become the default styling solution for all modern web development despite taking each and every one of these problems, exacerbating them, and applying them to places that didn't have them before

Good things for Tailwind:

This is a good thing, an unironic win for Tailwind. More than anything else, this is what a large codebase with multiple frontend devs needs: a rigid set of global constants that everyone is strongly incentivized to use.

I don't care about celebrating my birthday anymore but instead I care spending time with friends. They are always here for me. Always trying to help me...passing fun times together and being amazing people. My birthday wouldn't be the same without them. They mean a lot to me.

About using C code:

• there obviously the potential bugs and vulnerabilities in the C code itself and in the code wrapping the C code.
• specific C toolchains, which makes things hard when you do cross compilation.
• you (sometimes) need to deploy the dynamically-linked C library (OpenSSL). It prevents you from using secure FROM scratch container images.
• can't compile it for WebAssembly.
• maintenance! it's hard to review a 2000 line implementation of an encryption algorithm

Pure Rust cryptography is usually around 10-25% slower than an ultra optimized C or assembly code.