Most people can do that (become a software engineer) but NOT EVERYONE can become a good one. To be a good software engineer, the most important thing is that you try to understand things how it works, you really really try hard to understand HOW IT WORKS, MAKE IT WORK — XT at Google

The author feelds a disconnect with web developers who knows only JS frameworks to build a website as SPA...

One dev thought it would be a good idea to put everything into the cloud without estimating the bill :-D

Pain in C++

• tools and compiler/platform differences
• ergonomics and (thread) safety
• community

Why Rust?

• fun & cool: better for a hobby project. It is a need.
• Great tooling
• Options are easier to use than C++'s pointers
• use system over #include
• simpler dependency management
• killer feature is Send and Sync, statically enforcing rules around threading.

Ship of Theseus strategy for the rewrite: component by component. The fish app should work exactly the same.

So if you are trying to draw any conclusions from this, consider the context: A group of people working on a thing in their free time, diverting some effort to work on something else, and deciding that after the work is finished it actually isn’t.

Gripes with Rust

• portability between OS: it allows to miss systems and ignoring version differences
• string translation and localization: format! are checked at compile-time
• building to other targets: "it is often better to use if cfg!(...) instead of #[cfg(...)] because code behind the latter is eliminated very early, so it may be entirely wrong and only shows up when building on the affected system.

They also report mistakes they made.

There are good with quick-wins of the port to Rust. There is also some sad ones: CMake is not removed yet. Cargo is missing some features to install third dependencies (.fish scripts, 130 pages of documentation, the web-config tool and the man page generator).
Cygwin is not a supported platform.

About microdata:

Labelling things properly is still a powerful act, especially when it involves repetition and relationship-building.

What the post is missing is: how building these connections are useful? Ok it's great for AI models that are parsing the site...

Getting started with Microdata

Validate microdata markup

Try with https://alandalton.github.io/Authors-Apart/ for example

The specification of microdata

Theory about worker productivity

an organization doing work is just an incredibly complex, dynamic, distributed, parallel process.

The work capacity of an organization scales, at most, linearly as new members are added.

The ceaseless pursuit of force multipliers is the only possible route to superlinear productivity improvements as an organization grows.

Contention costs grow superlinearly as new members are added.

Staffing highly sequential efforts as if they were entirely parallel leads to catastrophe.

Coherence costs grow quadratically as new members are added. [...] The total time spent communicating will grow quadratically as the work capacity of the organization grows linearly.

Principles:

• Keep the work parallel, the groups small, and the resources local
• Prioritize the development of force multipliers
• If possible, factor work products into independent modules; if not, grow slowly and optimize.
• Scale organizational efforts across a portfolio of synergistic products
• Keep responsibility assignment matrices small, sparse, and local
• Prioritize asynchronous information distribution over synchronous
• Build humane organizations

A rating UI pattern with smileys: only built with HTML and css.

Une pétition en ligne sur le site de l'assemblée nationale pour arrêter les communications sur X

Different thoughts about how we handle faillible and infaillible functions

Similarly as in functional programming where functions and closures are „just values“, here results are „just values“. This opens up some new possibilities.

So how to handle infallible functions that returns an expected error (Can not divide by 0) and infaillible functions (that execute 1 + 2): there is no way to distinguish them with Result only... Or maybe Result<Result<T, InfallibleError> FallibleError>

Conclusion:

Honestly, I don’t know if there’s any. I just hope to illustrate some reasons why I personally don’t like the Ok-wrapping in as analytical way as possible. I hope we can at least learn to agree to disagree on this point and respect that each one has their reasons for the preferences.

Manquements de la France concernant l'application du RGPD sur son territoire

Le système de dépôt d'une plainte pour violation du RGPD est defficient, comme leur gestion par la CNIL. Le Conseil d'État ne permet pas d'agit contre les manquements de la CNIL, et la CNIL peut être supposé de connivence avec les Reponsables de Traitement qu'elle est supposée sanctionner

1.8 millions de personnes par mois sur les services de Framasoft.

La nouvelle récapitule les statistiques des différents services Framdate, Framapad, Framalistes et Framagroupes, Framaforms, Framacalc, Framateams, Framagit, Framacarte, Framatalk, Framindmap,Framavox, Framagenda, Framaspace, PeerTube, Mobilizon, Framadrive, Framapiaf,

Trouver du logiciel, outil ou matériel libre

Best ratio ever !