Un plan nataliste qui ne concentre ses efforts que sur la fertilité, comme si la baisse des naissances en France n’était pas aussi dû aux conditions de vie des familles.

Les systèmes de vérification d'âge sont facilement contournable.

À noter que ces formes d'abus sont maintenant catégorisés comme "terrorisme" afin que les moyens déployés soient conséquents. Cette amalgame renforce la dérive des outils de lutte contre le terrorisme (et de surveillance) à finalement tout les problèmes sociétaux.

Les dispositifs applicables en matière de terrorisme seront appliqués, à la fois s’agissant des subventions et s’agissant des référencements de ces sites qui peuvent inciter à la haine et à la violence

Fin janvier, la porte-parole de la Fédération nationale Solidarité femmes, Camille Lextray, avait évoqué des « tentatives de saturation du 3919 », avec « des appels coordonnés », « des appels de plus en plus virulents » ainsi que des « attaques envers les écoutantes ».

Des définitions avec des exemples de locales.

i18n: The design and development of a product that is enabled for target audiences that vary in culture, region, or language.
i10n: The tailoring of a system to the individual cultural expectations of a specific target market or group of individuals.
Locale: an identifier for a set of international preferences
international

Ainsi que les RFCs les définissant, avec notamment l'exemple de l'en-tête HTTP "Content-Language", "Accept-Language".
Les locales sont aussi utilisées via l'attribut lang, la spécificité de translate, dir, hreflang en HTML; et les possiblités d'usages en CSS via les sélecteurs

Why did such an experienced leader make such an terrible mistake?

The promises made didn't hold the reality delivered.

• switching to Perl would unlock the architecture we need, rebuilding from scratch would accelerate hiring and quality)
• velocity collapsed as the team relearned and rebuilt everything, burn rate jumped from 200K to 500K per month

One strategy: how you evaluated other language candidates?

Every technical debate is really two conversations: the visible and marketed one and the (stronger private) invisible one.

The real question is: can you afford to let it make your decisions?

Because the invisible conversation has a price tag. Industry research suggests that technology stack decisions account for 40-60% of total development costs over a product’s lifecycle. Research by Stripe found that developers spend 42% of their time on technical debt.

An better question is "what is this language going to cost us?" in velocity, technical debt, hiring difficulty, operational complexity.

spf13 published a framework to estimate it: https://spf13.com/p/the-9-factors/

L'interface web de Pandoc pour convertir des documents

Avec la fin du support de Windows 10, Linux atteint 5% d'utilisations selon StatCounter. À l'opposé, Windows a perdu environ 10% comparé à janvier 2022.

L’autre moteur de Linux, comme en France, est sa compatibilité de plus en plus avancée avec les jeux vidéo, lui permettant même de battre Windows sur certains benchmarks en performance.

A crude look at technology hype cycles. The critics are valid.
Containers, Kubernetes, the "Cloud", Anything at all "as a Service", the the Blockchain – anything, everything, based on it and now, arguably the biggest and worst of all, "generative AI"

A deep dive into ASCII rendering.

It seems great but I don't have time for it.

First off, it takes time to grow a design system's coverage. Design systems exist to provide common solutions that are versatile enough to be applied in multiple contexts. To do that successfully, we first need to fully understand those contexts - and that means diverging before we converge.

Ultimately, design systems are not replacing nothing. They’re replacing context-specific (if inefficiently created) solutions.

It doesn’t make sense for product teams to adopt design system components and patterns unless it matches or exceeds the quality of those that they’re already using.

relevant questions about to include anti-patterns in the documentation. Note these questions are also pertinent .

• How much is the component or pattern being used?
• How often are people looking for it in our design system?
• Is there an opportunity to make it less bad?

Including bad practice in design systems gives us an opportunity to call it out: it's the perfect place for alignment of our understanding or opinion of what constitutes bad practice.

I don’t subscribe to the idea of purely “descriptive” design systems - ones that simply systematise existing UI, regardless of its usability and quality. Design systems have a responsibility to mitigate - and certainly to not proliferate - bad practice.However, design systems must also acknowledge the reality of the context in which they sit. If problematic components and patterns are being widely used, then our design systems can play an important role in discouraging further uptake, raising awareness of their issues, and offering risk-mitigation advice and alternatives to consider. As with most design system concerns, there’s no blanket solution here. But I hope these considerations will help you the next time you’re faced with this question.

Why don’t we approach guidance and documentation as modular parts of our systems, the way we do with everything else?

For example: “Buy this book” not “Buy This Book”.

This is important in button documentation, guidance on links, content A-Z styleguide, developer documentation in GitHub, Storybook or design libraries in Figma or Sketch. Design systems seek to increase efficiency via common solutions that can be maintained centrally and reused in multiple places. We can do that for documentation too.

We can create the guidance in one of those places and link to it. This is more maintainable, but forces people to go to another place to get all the information they need to complete their task.

Documentation has variants too: in the design libraries, we may simply tell people to write calls to action in sentence case, but in the content styleguide, we may want to explain that sentence case is proven to be more readable most of the time. So already we have 2 variants: rule and rule with rationale. As more tools are used for different purposes, the documentation get more variants.

It's common to have multiple documentation tool, so we need a way to plugin our common documentation to every one of them. So the author is working on such tool that can deliver specific documentation variants.

"Vibe coding" is a trendy expression for "Automated coding".

Automated programming especially allows me to quickly build the tools I need so fast that every blacksmith that ever existed on this earth would envy me deeply.

With the automated coding, "we can finally get rid of all that middle work. That adapting layer of garbage we blindly accepted during these years. A huge amount of frameworks and libraries and tooling that has completely polluted software engineering, especially in web, mobile and desktop development."

The frameworks claim to solve three problems: simplification, automation and labour cost. "You unlock a feature that has nothing to do with engineering: you no longer need to hire a software engineer. You hire a React Developer.

Software engineering is back in a sense again: We have the chance again to get rid of useless complexity and keep working on the true and welcome complexity of our ideas, our features, our products. The complexity that matters. The complexity that is actually yours.

Automation and boilerplating have never been so cheap to overcome. I’ve been basically never writing twice the same line of code. I’m instantly building small tools I need, purpose built, exactly shaped around the problem at hand. I don’t need any fancy monorepo manager. A simple Makefile covers 100% of my needs for 99% of my use cases.

Bash, makefiles, ...

Think about it

Un retour des posts publié entre 1996 et 1998. Le web a tellement évolué depuis!

Publié le 17 juillet 1998.

A l'époque, la France limitait le chiffrement avec une clé de 40 bits, là où l'EFF avait cassé un chiffrement 56 bits avec une machine de 250 000$. Donc ce prototype de l'EFF cassait la clé de 40 bits en 3 secondes.

L'auteur recommandait

Bref, il est temps que les gouvernements se décident à autoriser un cryptage un rien plus costaud. Un cryptage à l’aide de clefs de 64 bits est déjà largement plus puissant. Évidement, cela ne résoudra pas le problème de l’état qui veut avoir un oeil sur tout.
Mais sérieusement, est-ce que les criminels en tout genre vont s’amuser à crypter en utilisant des outils légaux ? Non, ces mêmes criminels utilisent des clefs de 1024 bits ou même de 2048 bits (PGP est capable de coder avec une telle puissance et il est très simple à mettre en œuvre)."
Donc, le seul qui est gêné dans l’histoire c’est l’honnête citoyen qui désire simplement éviter que son patron, son provider, une tierce personne aille mettre un nez dans ses affaires