The method to build software feature by iteration is a mistake long-term.

Carrying over this approach past the learning phase was a mistake.

It is possible to dramatically cut the amount of bugs you introduce in the first place, if you focus on optimizing that (and not just the iteration time)

One super power is bugs can be found while reading the code.

The key is careful, slow reading. What you actually are doing is building the mental model of a program inside your head.

If you are reviewing a PR, don’t review just the diff, review the entire subsystem.

Follow the control flow or stare at the state

RSS feeds can be broken because of

• expired SSL certificates
• timeouts caused by slow servers
• misconfigured firewalls
• servers going down
• change feed URLs
• feed parsing failures
• deleted feeds
• deleted websites

Thoughts on ratelimiting, which can be implemented in different ways depending of the needs.

Help to build microservices as WASM components in Rust.

It can be used to handle HTTP requests for example.

There is a demonstration: https://www.youtube.com/watch?v=UoRfr3Q2R8A

Une introduction à Nix afin de recréer des environnements.

On remarque que Nix évite toute la couche OS de Docker.

Si votre salaire ne suffit qu'à manger et dormir, ce n'est pas un travail, autrefois, on appelait cela de l'esclavage.

v👨‍💻 Le LIDAR est accessible dans l'éditeur ID. Pas vérifié dans #JOSM.

Donc les données d'OpenStreetMap sont enrichies par les . Ainsi il est possible de tracer, corriger ou compléter le tracé de pistes, chemins, cours d'eau qui sont masqués par la végétations. Génial !

C'est une technologie de télédétection par laser permettant, depuis un avion 🛩️, de créer une carte 3D très précise du terrain, même sous la végétation 🌳

(via https://sebsauvage.net/links/?Tt7tQw)

1. Remove social media apps (or completely mute them at the very least)
2. Opt-in instead of opt-out notifications
3. Managing sounds
4. Report telemarketers and robo-calls

They wouldn't use Google Search engine as default for 20 billions per year.

Their marketing values privacy, but this partnership is a on their commitment to privacy.

Take: If Apple really cared about privacy, not only should they choose a different search engine, they should block ads and trackers in Safari by default.

But they don't even if they can do it tomorrow.

Create a CA locally and use it to generate certificates. So it's perfect for local network requests (https, etc...)

One file per project.

Each entry starts with a timestamp and is succinct: one or two sentences. That's it.

About ?page=1 that can become /?page=1 OR 1=1

An extremely fast PHP linter, formatter, and static analyzer, written in Rust.

That's interesting

375 petabytes into an LTO cart.

Note the experiment was conducted on 156.6 kB and the cart can not be damaged or the whole data would be corrupted.
Another limitation is the rate: 156kB in 2.5 hours; so nearly 1kB per minute.

It is estimated that one kilometer of DNA can store 74.7 GB, way less than the LOT-9 capacity of around 18TB (45TB compressed).

So it remains a science project for now.

Instead of trying to ascertain the truth, editors assessed the credibility of sources, looking to signals like whether a publication had a fact-checking department, got cited by other reputable sources, and issued corrections when it got things wrong.

Wikipedia’s dispute resolution system does not actually resolve disputes. In fact, it seems to facilitate them continuing forever.

Wikipedia is a mirror of the world’s biases, not the source of them. We can’t write articles about what you don’t cover.

As volunteers, editors work on topics they think are important, and the encyclopedia’s emphases and omissions reflect their demographics.

Crucially, if you think something is wrong on Wikipedia, you can fix it yourself, though it will require making a case based on verifiability rather than ideological “balance.”

That is, Wikipedia’s first and best line of defense is to explain how Wikipedia works.

Nous étions plusieurs associations et militants antivalidistes à alerter sur le fait que dans tous les pays où la loi sur l'#Euthanasie
avait été promulguée, des lois réduisant les accès aux droits des personnes handicapées survenaient.

Actuellement, le gouvernement réfléchit à plafonner l'#AAH
et à en conditionner l'accès.
Actuellement le gouvernement compte réduire à peau de chagrin l'#ALD.

Voilà. C'est tout.

Merci à nos chers élus de ne rien avoir écouté. Même si ce gouvernement saute, le suivant aura ce genre d'idées.

Rule 1: Restrict all code to very simple control flow constructs

Rule 2: Give all loops a fixed upper bound.

Rule 3: Do not use dynamic memory allocation after initialization.

Rule 4: No function should be longer than what can be printed on a single sheet of paper in a standard format with one line per statement and one line per declaration. Typically, this means no more than about 60 lines of code per function.

Rule 5: The code's assertion density should average to minimally two assertions per function. Assertions must be used to check for anomalous conditions that should never happen in real-life executions. Assertions must be side-effect free and should be defined as Boolean tests. When an assertion fails, an explicit recovery action must be taken such as returning an error condition to the caller of the function that executes the failing assertion. Any assertion for which a static checking tool can prove that it can never fail or never hold violates this rule.

Rule 6: Declare all data objects at the smallest possible level of scope.

Rule 7: Each calling function must check the return value of nonvoid functions, and each called function must check the validity of all parameters provided by the caller

Rule 8: preprocessor must be limited to the inclusion of header files

Rule 9: The use of pointers must be restricted. Specifically, no more than one level of dereferencing should be used.

Rule 10: All code must be compiled, from the first day of development, with all compiler warnings enabled at the most pedantic setting available. All code must compile without warnings. All code must also be checked daily with at least one, but preferably more than one, strong static source code analyzer and should pass all analyses with zero warnings.