Le 8ème Principe “oublié” du “Local First”

Le mouvement du “Local First” a émergé des États-Unis avec une vision innovante pour le développement web, en particulier pour les Progressive Web Apps (PWA).

Cette approche consiste à développer les applications en utilisant d’abord les données localement et en les partageant aux autres utilisateurs via des mécanismes et protocoles de synchronisation. Elle repose sur 7 (sept) principes fondamentaux qui visent à transformer la manière dont nous concevons et utilisons les applications en ligne. Voici ces 7 principes, tels qu’énoncés par les chercheurs de Ink and Switch dans leur publication fondatrice (*).

Continuer à lire

Intervention de Cinchéo à “Tech4Climate?” – L’éco-conception logicielle : quelques constats et conseils pour démarrer

Le 9 juin 2022, j’étais invité à intervenir dans l’atelier “Les acteurs du numérique au service de la transition” de l’événement “Tech4Climate?” organisé par le groupe Constellation.

Pour celles et ceux qui n’ont pas eu la chance d’y assister, voici quelques photos et le résumé des messages que j’ai fait passer.

Continuer à lire

Food for thought about Software Eco-Design

Things are not simple when it comes to Software Eco-Design.

Eco-Design is about maximizing a software Efficiency function of Usage, which can be defined as a ratio :

Efficiency(U) = Utility(U) / Resources(U) (U = Usage, a parameter)

  • Utility is related to the amount of useful work you can do in a unit of time (the word useful is important, because it depends on the context and what you need to achieve).
  • Resources, for software is the amount of computation, data, I/O you use, which in turn, corresponds to an amount of energy (electricity) and hardware resources (servers, routers, wires, satellites, laptops, smartphones, …). The more software resources your application use, the more energy you will need, and the more powerful hardware you will use.
  • Usage (U), corresponds of how your software is used. Usage is about how often your users will connect to the app, how many, from which county, etc. It is a parameter of Efficiency, Utility, and Resources because software impacts heavily depend on how the users will use it. The same software used differently may use up different amount of resources or have different utilities. Most importantly, Efficiency, Utility, and Resources might not be a linear function. Think of Amazon for instance: the utility might vary largely depending on the number of users, and the resources on where those users are located on the planet.
  • Energy and hardware resources end up to be direct impacts on the planet, contributing to climate change or environment destruction (side note: the IT sector is expected to reach 10% of GES within 5 years, that is to say the equivalent of all personal vehicles worldwide).
Continuer à lire

MC2: a tool to remotely monitor computer resources

For more than a year now, EASYTEAM and Cinchéo have been working on a project that aims at creating new methods and tools to help IT departments to control the carbon footprint linked to digital services. It is a vast and complicated topic and a lot needs to be achieved. With MC2 (say M-C-square), we are contributing a small and modest part to the tooling ecosystem.

In this post, I will explain the principles of MC2 and how it works. The source code is fully available on Github: https://github.com/cincheo/mc2.

NOTE: MC2 it is still work in progress and is a small part of a wider R&D project involving EASYTEAM (Constellation group) and INRIA (Spirals team).

Continuer à lire

Back to the Future: let’s stop buying new Laptops and Smartphones ;)

When I was a teenager, I used to go to the center of Paris to buy specific parts to build my PC myself: sound cards, video cards, power blocks, hard drive, CPU, fans, memory, you name it. Not only it was fun and instructive, but it was also good for the planet.

Continuer à lire