Daily Shaarli
August 23, 2025
cité dans le livre No Logo de Naomi Klein
A way to visualize money flows. How much per hour!
Des trois acteurs en jeu, les investisseurs, les entreprises d’IA et les utilisateurs, les seuls à réaliser des profits sont les acteurs financiers dont les valorisations augmentent. C’est une situation de bulle typique : des plus-values élevées et des profits faibles.
The UnJS and nuxt team are always doing great things!
Les données piratées comprennent le « nom, prénom, adresses e-mail et postale, numéro de téléphone, numéro de carte de fidélité »
Avec les FAIs, toutes les données sont dans la nature maintenant.
L’enseigne nordiste avait déjà été victime d’une attaque similaire en novembre 2024.
Le marché de la voiture évolue. Ma prochaine voiture si nécessaire sera électrique.
Je constate depuis plusieurs années que des gens dévalorisent la voiture électrique, mais leurs arguments semblent peu réfléchis.
En comparaison, 93% des utilisateurs de voitures électriques sont satisfaits. https://www.avere-france.org/enquete-ipsos-avere-france-plus-de-9-utilisateurs-sur-10-de-vehicules-electriques-satisfaits/
To keep the code maintainable, keep the css specificity as low as possible.
BEM falls short: class names can get really long; reusability might not be prioritized; and things must be named.
Another case is to use utility classes (atomic css) to avoid css specificity.
A new approach is with cascade layers.
Anyways, Cascade Layers (@layers) groups styles and declares what order the groups should be, regardless of the specificity scores of those rules.
Each has a sweet spot:
- BEM for clear design system that needs to be consistent; team with different philosophies; styles are less likely to leak between components.
- utility classes: build fast, like prototypes or MVPs and component based JS framework
- cascade layers: legacy codebases where you need full specificity control; integrate third party libraries or styles from other sources; working on a large, complex application or projects with long-term maintenance
How they can work together?
The cascade layers can be seen as an orchestrator: one layer for components (BEM); one layer for utilities (utility classes)
Embracing slow means I’ve gone from hovering around three runs a week to at least five. Regularly hitting 60kms and still feeling like I could do more. By mixing hard work and snappy tempo runs with slow and steady, and doing it properly I am faster, healthier and more importantly happier than I have felt in years.
Instead of specifying Block or Element specific Modifiers, you create generic semantic classes that apply those repeatable styles to any element that needs them.
When I started creating Kelp, I went down the BEM path. I quickly switched to semantic CSS, and the file size decreased dramatically as a result.
After programming for years, I find creating a class system is better than BEM.
While the CSS specificity is low, everything else is kept simple.
Only up the specificity lightly, and note it; the minimum is another class, :where() or the HTML tag.
A single class ".override" can also be used; but "If you’re ever overriding an override, that’s a good place to stop and re-consider. "
A case in favor of materialized views: it avoids caches; off-by-one error and so on.
What are developer's blocks?
All these practices (documentation, tests, CI) are valuable, but sometimes they just mount up until you’re blocked.
Either you are new to the project and you just feel overwhelmed or you’ve been working on the project for a while, but you run out of stream and get stuck. it may be due to overwork or a lack of motivation.
How to unblock?
- Take time with learning. Sometimes, the docs or tests need to be read to get an idea of the externals. Eventually looking at the source code and building up a mental model of how it fall fits together. "If you think education is expensive, try ignorance"
- Realise when you're tired
- Work incrementally: implement it with the minimum effort. Circle back round to improve the tests, docs, etc...
- Write a prototype: Concern yourself only with the happy path. If you’re trying to learn about a dependency, it’s sometimes easier to write a quick prototype of using the dependency, possibly in an empty repository.
- Start with draft documentation: avoid premature docs polishing. Capture why you did things a particular way. Provide basic usage instructions.
- Release early, release often