196 private links
Qui sont les assistés? Cela semble aberrant.
Un raté pour les virements instantanés de Boursorama et leur réponse est injustifiable.
j'ai des complications avec LCL et tout cela me pousse à utiliser des banques totalement numérique.
A dependency in software can be summarized to a checksum, a location, a name and a version.
The checksum checks the integrity, the location defines how to retrieve the dependency, the name identify the dependency and the version its substitutability (major with breaking changes, minor if it has new features or bug fixes).
Les milliardaires possèdent de plus en plus de médias
De fait, le tarif réglementé sur l’électricité va baisser de 14 % au 1er février 2025 pour les particuliers. Relevée à son niveau d’avant-crise, la taxe sur l’électricité remontera à 33,70 euros par mégawattheure pour les ménages français, contre 22 euros actuellement.
Autre changement à prendre compte, celui du prix du gaz de chauffage, dont le tarif de l’accise passe pour 2025 à 17,16 € par MWh. Contre 16,37 €/MWh en 2024 et 8,37 €/MWh en 2023.
Utiliser des portes dérobées est à double tranchant: un attaquant peut aussi les exploiter. Pour un de ces raisons, les experts en cybersécurité déconseille les portes dérobées.
<datalist>
can be combined with more than raw text inputs!
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