Nice and very approachable introduction to the use of elliptic curves for cryptography. I think I finally understood properly how those work. :-)
Very nice introduction to animations with CSS. Per usual for me coming from a QML background it often sounds more involved than it should be but overall nice facilities are now provided straight from the browser.
FR: Pour une fois un pas positif que la création de cette mission. Cela va dans le bon sens en espérant que cela soit respecté par ailleurs.
EN: For once a step in the right direction the creation of this mission. It goes in the right direction indeed but let's hope it'll be respected.
FR: Un article de plus sur le "vendor lock-in" ridicule que nous vivons avec certains appareils (et oui, de nos jours un tracteur est juste un autre appareil avec du code embarqué). Ou pourquoi le droit à la réparation devient une liberté essentielle à défendre.
EN: One more article on the preposterous vendor lock-in we experience with some devices (and yes, nowadays a tractor is yet another device with embedded code). Or why right to repair becomes an important freedom to defend.
Interesting exploration for a low level bug in the TCP stack. A proof that it's not always the network being at fault. ;-)
Very interesting new supply chain attack. Shows one of the big downsides of the very convenient packaging tools everyone uses lately. Interestingly in that particular case it seems less risky only with the publicly available components, it's in the context of private repositories that the risk arises. Root cause seems to be the lack of control on how those tools resolve between private and public repositories.
Lots of good advice on how mentoring can be done. There are enough of them that you can pick and choose what makes sense for your own context. I like this kind of toolbox approaches.
Interesting ideas on how mentorship can be organized in a company. This is obviously examples coming from a specific context but still, the whole time bound and matchmaking approach is a good food for thought. It sounds a bit too mechanical and systematic for my taste but I guess it makes sense in their context. A few good extra resources provided as well.
Very interesting approach using code of conducts to fill the gaps of the pure license approach limitations. Indeed focusing on licenses only lead to the Open Source movement which is so much business oriented that ethics is completely overcome (there's so much you can do with licenses after all). This proposals using code of conducts (internal + external) is thus interesting to make proper commons. The question of how much of a deterrent and defensible from free loaders this could be is still open though.
Interesting take on why the Open Source movement is a zombie movement and why Free Software failed at the political level. This explains why we see a rise in the "Post-Open Source" term. This leads to potential ways out. It's a bit too much on the heavy marxist reading to my taste but otherwise it contains good criticism
Long and comprehensive description of how a tiny studio manages to work complete offgrid while traveling. Interesting tips to cherry-pick from.
FR: Après tout, jusqu'où un employeur devrait aller pour financer la mise en place du télétravail? Cet article en français donne une bonne idée des coûts et vraiment cela ne semble pas aussi coûteux pour l'employeur que ce que l'on pourrait supposer grâce aux économies sur le fait que l'employé ne soit pas dans un bureau.
EN: After all how far should the employer pay for remote working setup? This article in French gives a good idea of the costs incurred and really it doesn't seem as expensive to the employer as one could imagine due to how much is spared by not having the employees in an office in the first place.
Overall good piece about how to make quality software. That being said the whole section about "Hire the Best Engineers You Can" should be read with caution... it clearly starts from the "10x coder" fallacy, it's not true and suddenly completely ignores the project context.
Good exploration of what "engineer" and "engineering" means. Also helps to overcome what software people like us assume is done by the "real engineers" while in fact sometimes they can be as sloppy than us.