Les personnes qui insistent pour nous dégafamiser et nous linuxiser à l'os ONT RAISON.
Non elles ne sont pas "maladroites" ou "trop insistantes", ou "elles desservent leur cause" ou je ne sais quoi encore, on les déteste parce qu'elle nous mettent le nez dans notre propre caca. Et que changer implique de renoncer à notre petit confort.
Et c'est pareil pour les végans.

"Tu devrais installer Linux" est effectivement la meilleure réponse à "J'ai un problème avec mon Windows" même si ça ne nous fait pas plaisir et que ça ne va pas dépanner notre Windows.

Excellente utilisation de Mastodon : Ca se débat gentiment, ça se commente, ça se conseille, ça se fourgue des recettes, ça geeke dans tous les coins, l'ambiance est bonne, je suis extrêmement satisfaite.

First things first, you’ll need an account on crates.io to acquire an API token. To do so, visit the home page and log in via a GitHub account (required for now).

Free software is too dependent on MicrosoftHub but for Rust libraries, it is worse, a MicrosoftHub account is mandatory: "log in via a GitHub account (required for now)" I believe it is the only big programming language in that case?

(via https://mastodon.gougere.fr/@bortzmeyer/114008682103118141)

What cost AI per token in electricity and water?

TL;DR; concurrencer les GAFAM c'est

• Open source: Mistral, Mappy, Mastodon, ...
• relocaliser sans centralisation, sinon il y a bien le risque de recréer des GAFAMs

My dream was to be a web developer who creates simple, elegant, and fast products, but I’m starting to lose hope. First of all, I can’t keep up with the endless stream of new technologies. Secondly, simple and fast products are not in high demand, making it an already niche area.

Avoid, at all costs, arriving at a scenario where the ground-up rewrite starts to look attractive

Aim to be 90% done in 50% of the available time

Think about pathological data

Edge cases are our entire job.

There is usually a simpler way to write it

Write code to be testable

It is insufficient for code to be provably correct; it should be obviously, visibly, trivially correct

Documentation matters

Good documentation is more than just nice to have—it's a powerful way to spread knowledge. For development teams, clear documentation keeps everyone aligned, helps make decisions visible, and ensures no one has to reinvent the wheel when new people join. For users, it saves time. Poor documentation, on the other hand, leads to confusion, support tickets, and more work for everyone involved.

... all common and good tips. They are generics and I don't find anything actionable though.

Try writing a tax code in chat messages. You can’t. [...] That’s why we use documents

You program by writing documents instead of chatting.

Suite à la prise de fonction du président des État-Unis, Sebsauvage effectue un rappel de ce premier mois.

I agree

If one project using open source technology is successful, then the open source projets will benefit from it.

By default, if you are building with Nuxt, I want you to succeed. If you are a third-party provider with a great Nuxt module or integration, I want you to succeed.

Because

1. open source is a community project
2. compensation doesn't follow value
3. success is contagious

Can one have a project with a relational database that is deployed early and often, and not have thousands of SQL migration scripts? Seems like it’s difficult to have both. Maybe there’s some way to “roll up” old migration scripts into one nice SQL schema. I guess running them all on a new database and exporting the schema will do that. 🤔

Prisma provides a "baseline" to reset merge all migration scripts. There are always many migrations though.

I realized that one of the best things about open source software is that you can solve a problem once and then you can slap an open source license on that solution and you will never have to solve that problem ever again, no matter who’s employing you in the future.

I like to say that my interest in open source is actually really selfish. I figured something out. I never want to have to do this work ever again.

I like to say that my interest in open source is actually really selfish. I figured something out. I never want to have to do this work ever again.

Instead of a "take", use

• Opinion
• View
• Perspective
• Thought
• Judgment
• Stance
• Belief
• Attitude
• Position
• Interpretation
• Reaction

But, when a developer experience feature is baked into the browser, I start to get uncomfortable. I know I can be a bit of a curmudgeon about this stuff, but that isn’t my default setting. That comes from lots of experience of lots of different codebases in my years as a CSS consultant. I’m a stickler for learning from mistakes.