Docker-compose is a tool that accepts a YAML file that specifies a cross container application and automates the creation and removal of all those containers without the need to write several docker commands for each one. It should be used for testing and development.

Kubernetes, on the other hand, is a platform for managing production-ready containerized workloads and services that allows for declarative setup as well as automation.

I will read more when I will need it :)

1. Partir d'une base légère
2. Éliminer les FROM, RUN et COPY
3. Placer les fichiers modifiés souvent à la fin du build de l'image si possible
4. Utiliser le .dockerignore
5. "tout ce qui n’est pas essentiel au fonctionnement de mon programme n’a pas sa place dans mon image."

Peut être utile un jour

Documentation that generates code that is then used in the project :)

Detect websites built with Vue or Nuxt and it displays related informations (plugins, modules, ...).

Project: https://github.com/nuxtlabs/vue-telescope-analyzer

Rather than interrogating a device directly, we ask the device vendor to do it for us.

I see so much problems coming 🍿
At the same time, I like the idea so much!

4 parties involved:

• an origin (service provider)
• a client (service consumer)
• an attester (proof the client is real, for example device vendors)
• an issuer: producer of the token called by the attester and choosed by the origin

The way it works is quite simple, you just have to copy and paste the content of your Dockerfile into the interface and the site gives you a list of recommendations to follow to improve your file.

This is the critical mental-model shift. CSS properties on their own are meaningless. It's up to the layout algorithm to define what they do, how they're used in the calculations.

Here's an example which blew my mind: Did you know that the width property is implemented differently depending on the layout algorithm?

I didn't know 😱

Inline space under images are due to the Flow layout and its inline elements. It adds extra-space to make sure that inline elements, such as <img />, don't negatively affect the legibility of the surrounding text.

There are a lot of layout algorithms in CSS, and they all have their own quirks and hidden mechanisms. When we focus on CSS properties, we're only seeing the tip of the iceberg. We never learn about really important concepts like stacking contexts or containing blocks or cascade origins!

Our intuition is the best tool we have. And when we start using CSS snippets without truly understanding them, it's only a matter of time until some hidden aspect of the layout algorithm throws a wrench into our gears, stopping us in our tracks.

Mais ce n’est pas avec ces compétences numériques qu’ils deviendront des citoyens informés et formés à l’histoire des technologies numériques, à sa culture, à ses nombreux enjeux économiques, sociaux, politiques. Ce n’est pas avec ces compétences numériques qu’ils pourront décider collectivement de leur futur et de la place qu’y prendront les technologies numériques.

Transmettre une culture numérique au lieu de simple connaissance.

Réfléchir au modèle sociotechnique et économique de Google. Par exemple:

L'objectif de l'école serait donc:

1. Passer des compétences d’usages consuméristes aux compétences de pratiques émancipatrices. 2. Passer des strictes compétences numériques à la vision plus large de la culture numérique.
2. Et enfin, adosser à cette culture numérique une réflexion critique du numérique.

This separation between unit and integration became vague nowadays.
Instead we can think in term of purity and extent.

Purity → "corresponds to the amount of generalized IO the test is doing and is correlated with desirable metrics, namely performance and resilience."
Extent → "corresponds to the amount of code the test exercises. Extent somewhat correlates with impurity, but generally does not directly affect performance."