My pronouns are he/him/../../../etc/passwd

And an answer from @LionsPhil@plush.city:

.. from / is just /, because UNIX just wanted to make a ../../../../ slide up to the root from a fairly arbitrary depth starting point possible apparently

How to load font the most efficient way in 2025 for nearly every cases.

The frauds are targeting older or less tech-savvy users. They are targeted because they're perceived as having more savings or assets; less likely to be digital natives and trend to trust authority figures or brands. [They have a hard time to] recognise safe vs. suspicious links: differentiate between ads and actual content; know how to verify sources and undertand terms like multi-factor authentication or phishing.

In 2021, there were more than 90,000 older victims of fraud, according to the FBI. It resulted in $1.7 bullion in losses.

On average, older people in the UK who have been scammed have lost nearly £4,000 each.

They are subject to the decision fatigue and if the app or website is already not easy, then scammer can rely on these factors.

UX has a role to play in order to prevent scams to remain unknown. The tips or patterns are already known. I note a few more though: use friction to protect, not hinder; embed contextual education. "What we can do as designers is build systems that make hesitation feel natural [...] and inject small moments of friction that nudge users to double-check before proceeding"

UX has however limitations: "To help those like her, ultimately, additional elements like support contact numbers, face-to-face courses on how to stay safe on your phone, and, of course, help from family members as required."

Is it maintained?

Understanding the O notation for software complexity.

BlueSky blocks the Mississippi because they added age verification.

It means the whole BlueSky network is blocked. So there is no decentralization. One authority rules the network.

cité dans le livre No Logo de Naomi Klein

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)

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 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.

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?

1. 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"
2. Realise when you're tired
3. Work incrementally: implement it with the minimum effort. Circle back round to improve the tests, docs, etc...
4. 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.
5. Start with draft documentation: avoid premature docs polishing. Capture why you did things a particular way. Provide basic usage instructions.
6. Release early, release often