Argument against Github that are mostly arguments against monopolies.

Simple JSON files can be used to generate a functional website :D

Why?

• We don't need one until we do

  • you almost never create an object fully formed with all the behavior it is ever going to need
  • when it is complex enough, it costs too much time to replace it with something that has equivalent functionality

• the state machine is a fluffy bunny

  • there is the belief that state machines are more complex than they actually are
  • it is therefore nothing but pragmatism that makes us consider a “full-blown” state machine overkill.

BUT most state machines you’re likely to need in your day-to-day development have nothing in common with their computing theory counterparts

• Adding a state machine library has a learning curve. It is rather small.

So moving to a state machine:

• Integration is painless but moving all the code around to be inline with state machine is a big pain
• Using it from the start is a breeze, as such as future changes.
• We’re now able to easily introduce more states to give our users extra information as well as allow us to track things to a finer grain.
• Return values from state transitions are 100% consistent. There are no strange objects, arrays, nil, boolean depending of the developers.
• It is easy to log
• Refactoring lead to greater code quality with state machines

We seem to shy away from state machines due to misunderstanding of their complexity and/or an inability to quantify the benefits

It’s a strange feeling to know that Google, OpenAI and Microsoft will make a lot of money with these new chat bots. But they won’t link to your sites anymore.

But it is what it is. If you don’t want that, you probably shouldn’t put a website in public. 🤔

Pour ça, il faut être impliqué dans les phases d'exploration produit. Il faut prendre du temps pour parler aux utilisateurs. Si votre produit est utilisé sur des chantiers, allez sur les chantiers, s'il est utilisé par le support client, regardez les l'utiliser. Ne reposez jamais sur un proxy de vos utilisateurs, commerciaux et autres parties prenantes internes à votre entreprise, sinon vous allez créer un outil pour ces personnes, pas un produit pour vos clients !

Fait important à retenir, vous n'êtes pas payé pour dire que quelque chose n'est pas faisable, mais pour faire en sorte que ça le soit.
Vous êtes là pour apporter des alternatives sur la table. Et pour cela il faut être actif, comprendre précisément le problème à résoudre, d'où la participation aux interviews utilisateurs, l'analyse quantitative, etc.

How much uptime guarantees should be needed?

Les classiques mais effficaces.

Je penses dériver du sujet et ajouter une touche particulière. par exemple, le système de gestion des stocks peut être spécialisé sur ... du composte, des pièce 3D, öa plateforme de covoiturage peut avoir un système de calcul des émissions de CO2 évolué, etc...

How to hope for great AI if they are built by societies similar to Facebook?

What is the expected legacy of the Internet and the Web?

By opening it all up: APIs, clients, protocols, and algorithms.

Proposition:

Any system with 1 million+ user should be required to issue users with personal API keys by law.

For libertarian:

For a really competitive, innovative, dynamic marketplace, you need adversarial interoperability: that’s when you create a new product or service that plugs into the existing ones without the permission of the companies that make them. Think of third-party printer ink, alternative app stores, or independent repair shops using compatible parts from rival manufacturers to fix your car, phone, or tractor.

I disagree with most of its arguments, but in the same time I agree that browsers are so big complex systems.

TL;DR; the added value of Twitter (reliability of the sources) is now lost.

Un réflexion du début des ordinateurs et des systèmes d'exploitation au cloud.

: « L’homme, dans la sourde crainte qui est la sienne d’être demeuré entre deux eaux, est « plus malade, plus incertain, plus changeant, plus inconsistant que n’importe quel animal, il n’y a aucun doute – il est l’animal malade ». » - Nietzsche

Critique d'une mesure dérisoire, et pourquoi elle a été prise.

IndexedDB can be used to store a lot of data. It has some caveats though.

Storage:
About deletion, use soft delete to smoothen the synchronization if a user deletes a record and another one update it.

About record collection, use unique IDs (UUID v4) or property related ids with (UUID v5).

About ordering, it is easier to use fractional indices! Read more on https://www.figma.com/blog/realtime-editing-of-ordered-sequences/, or https://www.steveruiz.me/posts/reordering-fractional-indices, or use a dedicated library.

Sync is made with pull and push
Update:

• Send atomic changes from a client is the more convenient way. We can send only the model’s ID and its updated fields.
• send operations instead of changed data,

Conflict resolution:

• In some cases, last-write wins at the record field level will be enough
• in others, we strongly need a full-fledged CRDT.

Comment gérer un flux RSS particulier

Rust can be used to write all kinds of software (vertically scalable) and the development of software artifacts can be parallelized (horizontally scalable).

while it excels in the lowest half of the stack, it’s pretty ok everywhere else too.

The rust golden rule:

how function signatures are mandatory and authoritative and explicitly define the interface both for the callers of the function and for the function’s body. more

The second feature of Rust is its module system. It's first class support of the concept of libraries.

The third is cargo with its rigid specification for what a package of rust code.

The symptoms of pop culture:

• A “disdain for history”. Pop cultures believe history doesn’t have anything to teach them.
• Newer is automatically better. Pop cultures are built on the assumption that anything new or different is superior to established. Or, in other words, older is inherently inferior.
• What’s next is going to be superior to what’s now. Pop cultures exist in perpetual anticipation of the next trend. Their disbelief of history appears to outsiders as a belief in progress.
• The “Pop” in “Pop Culture” stands for “popularity”. If it’s popular then it must be right.

These traits are deeply irrational but they are the tech industry’s default mode of operation.

We care about the number of concepts that changed in a particular PR.

The smaller the PR the more likely it will be to get merged quickly

Rules:

1. Don't waste your reviewer's time by showing them all your failed experiments in your Git history.
2. Maintain a Git history closest to the true essence of the work done, creating many small PRs that each make one releasable change to the codebase and keeping the number of commits as low as possible.

What I can improve is to remove (fixup or squash) all these tries/little fixes that I add in the commit history.