1. Clarity is job #1
2. Interfaces exist to enable interaction
3. Conserve attention at all costs
4. Keep users in control
5. Direct manipulation is best
6. One primary action per screen
7. Keep secondary actions secondary
8. Provide a natural next step
9. Appearance follows behavior
10. Consistency matters
11. Strong visual hierarchies work best
12. Smart organization reduces cognitive load
13. Highlight, don't determine, with color
14. Progressive disclosure
15. Help people inline
16. A crucial moment: the zero state
17. Great design is invisible
18. Build on other design disciplines
19. Interfaces exist to be used

Google course on error messages

The point is many actors can detect the flaw during the same week. A 90 days window to deliver a fix no longer holds

Every attempt to score open source is not accurate.

The most consequential mistake is treating the absence of a signal as a low value of that signal.

Missing FUNDING file

Easy to collect doesn't mean something

Stars on Github (ICU only 3.5k, 2.5k), CVE counts (compare the Linux kernel to

One number, many units

npm "download" is mostly a count of CIcache misses. Dependent counts are different between a string-padding helper on npm and a C compression library that is statically linked and distributed as vendor or a git submodule.

Github as the visible universe

Not everything is on GitHub. Contributors (so the bus factor count too)

Project identity is different on different platform

curl has many names across platforms.

Invisible funding

The most common funding arrangement for critical infrastructure is none of those. It’s a maintainer employed by Red Hat, Google, Intel, Canonical, or a hardware vendor, with the project as some or all of their job, and that arrangement leaves no trace in any file a crawler can fetch. The second most common is consulting and support contracts around the project, which is similarly invisible.

and it compounds because the project doesn't look like an npm package. "The quiet system library with one tired maintainer and no dashboard footprint is exactly what we built all of this tooling to find, and it remains the thing the tooling is structurally worst at seeing."

Somewhere out there, someone wrote a really good blog post today. You'll probably never find it. Google won't show it to you. Social media buried it under engagement bait.

Bubbles tries to surface it. Community voting applied to thousands of personal, independent blogs, with identity and discussion routed through the Fediverse.

Hacker News and Lobste.rs have community voting figured out, but non-tech content gets drowned by the tech majority. Kagi Small Web curates thousands of personal sites, but has no community-driven ranking. Blog directories help you find blogs, not today's best blog post. Social platforms own the conversation. Mastodon is decentralized and ad-free, but you only see what the people you follow share. RSS is great, but solitary. There's no collective signal telling you what's worth reading today.

L'espagne a tranché: l'homéopathie, c'est du flan

The migration to Codeberg is really easy.

The bar is lower than common thought: uninteresting topics is a relative subject. The author's rule is anything that they’ve said more than once in a conversation.
There is also another effect in play: readers don't usually give this feedback, so it's hard to know.

So: lower your bar for what’s worth writing about! My personal standard is anything that I’ve said more than once in a conversation.

How?

1. Write consistently: every week and briefly, every day.
2. Notice and pay attention to feedback

Come with a good title: one that makes a promise about what the reader will get from reading the post that is (1) exciting, and (2) accurate.

Find the right framing. Provide examples. Use microhumor if you want to go for this tone. Write like you talk.

Amos Bar-Joseph, PDG de Swan AI, s'est même vanté de sa facture Anthropic sur LinkedIn, y voyant la preuve qu'il bâtit une « entreprise autonome » qui grandit par l'intelligence et non par les effectifs.

La justification repose sur un calcul simple : un investissement massif aujourd'hui pour des économies permanentes demain. Les entreprises parient que le coût actuel, bien que supérieur aux salaires, est un ticket d'entrée pour se débarrasser à terme de la majorité des coûts liés à la main-d'œuvre.

2% for the Linux Kernel.
4% for the blockchain
12% to AI, ML and Data analytics

6 times more to AI, ML and data analytics than the kernel.

Per project type:
72% to OSS
17% to standard and specification
5% to community initiative
2% to open hardware
2% to open data
1% to open governance network
1% to peer network

The member of the Linux foundation changed and their priorities too.

Dedicated to colors. it's a "an ongoing exploration of digital color tools shaped by art theory, historical systems, and practical design work".

The website has many themes.

Another color palette generator

With 3 columns and CSS grid.

A small efficient website.

The header is different: it's a text. It's always the same and only the rest of the view changes.

After JSON-LD, the working group announced a CBOR-LD.

It follows the JSON-LD philosophy of connecting and structuring data, but for CBOR https://json-ld.org/.

A system is what a system produces, and generative AI produces dangerously flawed code, ignorable copy, and, primarily, an excuse that protects companies’ valuations during layoffs. Generative AI provides these things at tremendous cost to the environment, while smothering the web that I’ve spent twenty years building.

I don’t use these tools. Not for writing, not for code, not for design, not for images, not for note-taking — not in whole or in part.