When the test fails it also should provide enough information to understand which behaviour failed, where it failed, and (at least superficially) why it failed

👍‍ with 5 arguments provided

Comparison with other ORM

1. Ask for help if you get stuck for more than an hour... I don't think it applies to every cases though
2. Docs? What are they? Write some along your coding session for yourself: yes!
3. Product thinking: User-oriented thinking
4. Hunt for a mentor
5. Work of art
6. Being less stupid: instead of being smart, try to make one less stupid decision every day.
7. Multiple approcahes: always try to come up with multiple solutions after going though a ticket, then pick the solution that suits well in the delivery time
8. Keep the team in the loop: always over-communicate
9. Product Job Mentality: think first, don’t start working unless the requirements are 100% understood; Never work on a feature for more than 2 weeks without validating it with users.
10. Do code reviews

How about we treat every young man who
wants to buy a gun like every woman who wants
to get an abortion
mandatory 48-hr waiting
period, parental permission, a note from his
doctor proving he understands what he's about
to do. a video he has to watch about the effects
of gun violence, and an ultrasound wand up the
ass (just because). Let's close down all but one
gun shop in every state and make him travel
hundreds of miles, take time off work, and stay
overnight in a strange town to get a gun. Make
him walk through a gauntlet of people holding
photos of loved ones who were shot to death,
people who call him a murderer and beg him not
to buy a gun.
It makes more sense to do this with young men
and guns than with women and health care,
right? I mean, no woman getting an abortion
has killed a room full of people in seconds,
right

Oh yeah, fair point

• React is a UI library.
• React component libraries are always for UI
• Components will update, whether you want them to or not
• useEffect is a major to control the rerendering

1. Automatic blocking of autoplay videos
2. Speedier website browsing
3. Lighter on system resources
4. Mobile extensions (some of them)
5. Equally easy sync across all devices
6. Deeper safeguards for privacy
7. Reader mode
8. Open-source code

SQL table expressions are somewhat similar to functions in a regular programming language — they reduce the overall complexity.
You can write an unreadable sheet of code, or you can break the code into understandable individual functions and compose a program out of them.
You can build a tower of nested subqueries, or you can extract them into CTEs and reference from the main query.

There is a myth that “CTEs are slow”. It came from old versions of PostgreSQL (11 and earlier), which always materialized CTE — calculated the full result of a table expression and stored it until the end of the query.

Ok. There are some rules:

• CTE runs on every request
• CTE splits the query code into multiple chunks
• instead of subquery, always use CTE for clarity

D’après Roland Gori, psychologue et psychanalyste, là où, historiquement, l’ébranlement fondamental était porté par une parole révélée ou encore une hypothèse qui appuyait un projet politique, aujourd’hui le constat de l’ébranlement puissant et total que nous allons connaître – et avons commencé à vivre – ne se double ni d’un unique et clair programme politique, ni d’une croyance en un salut providentiel. En d’autres termes, nous savons que l’effondrement a lieu, mais nous ne savons quoi en faire. En cela, de mobilisateur, il peut devenir paralysant, en témoigne le peu d’impact que peuvent avoir les sorties des derniers rapports du GIEC.

Graduating from school and after one year of full-time work, should I keep going and what do I want to do with my professional life ?
This is what the author is asking himself.

CI looks like build systems. If you push a CI system or a build systems too far, they seem to be the same as what they are doing.
The thing that bugs me about modern CI systems is that I inevitably feel like I'm reinventing a build system and fragmenting build system logic.

So going beyond the section title: CI systems aren't too complex: they shouldn't need to exist. Your CI functionality should be an extension of the build system.

CI offerings like GitHub Actions and GitLab Pipelines are more products than platforms because they tightly couple an opinionated configuration mechanism (YAML files) and web UI (and corresponding APIs) on top of a theoretically generic remote execute as a service offering.

I'm convinced that building what I'd like to see is not a question of if it can be done but whether we should and who will do it.

In my ideal world there exists a single remote code execution as a service platform purpose built for servicing both near real time and batch/delayed execution. It is probably tailored towards supporting software development, as those domain specific features set it apart from generic compute as a service tools like Kubernetes, Lambda, and others. But something more generic could potentially work.

Conclusion:

If I could snap my fingers and move industry's discrete build, CI, and maybe batch execute (e.g. data pipelines) ahead 10 years, I would:

1. Take Mozilla's Taskcluster and its best-in-class specialized remote execute as a service platform.
2. Add support for a real-time, synchronous execute API (like Bazel's remote execute API) to supplement the existing batch/asynchronous functionality.
3. Define Starlark dialects so you define CI/release like primitives in build tools like Bazel. (You could also do YAML here. But if your configuration files devolve into DSL, just use a real programming language already.)
4. Teach build tools like Bazel to work better when units of work that can take minutes or even hours to run (a synchronous/online driver model such as classically employed by build systems isn't appropriate for long-running test, release, or say data pipelines).
5. Throw a polished web UI for platform interaction, result reporting, etc on top.
6. Release it to the world.

I would also prefer an open web instead of limited super-apps.

What will happens when the web content will be published to these platforms only, as it is currently the case with the different channels ?

The more I follow the Deno project and its community, the more I think it would be easier to use Typescript and the environment of Deno to write scripts.

Python is not so much robust without types. The amount of time my script logic was correct, but I miss the type of some variable, causing a xx minute time of debugging. The type annotations are currently complex to use and overkill for scripts, where typescript shines.

Donc je résumes:

• quelques personnes ont des effets secondaires à cause du vaccin
• les gens se plaignent que c'est honteux de pousser la vaccination

le niveau de réflexion des commentaires m'affliges 😔

Le bénéfice/risque global est là: le vaccin est beaucoup plus bénéfique que néfaste, alors pourquoi discuter ?

Donc selon votre raisonnement, on aurais du éviter la vaccination, et laisser une grande partie de la population décéder ou se retrouver avec des séquelles à long terme ???

→ Remember: if your user is supposed to go somewhere, use an <a> element. If something with JavaScript needs to happen, use a <button> element.

I agree with that: link for navigation and button to trigger actions.

Instead, we can mix 3 or 4 designs together to create something unique. For example, maybe I’ll take the color scheme from one site, the general layout and spacing from another, and the typography styles from the third!

When I’ve mentioned this strategy to actual designers, they laugh and say that it’s what they all do. I think this is their version of the “joke” that programmers spend half their time googling things.

Note : en discutant de cet article, une personne m’a expliqué qu’elle a noté deux style de développement : des personnes développent “en pile”, en interompant ce qu’elles font pour traiter les nouvelles idées d’abord pour revenir ensuite là où elles en étaient, et d’autres “en file” ou elles terminent d’abord leur idée en cours avant d’entamer la suivante.

Je développe aussi "en file".

The very act of recording your actions and impressions is itself powerfully mnemonic, fixing the moment more durably in your memory so that it’s easier to recall in future, even if you never consult your notes. ‒ Cory Doctorow

Comme l’explique Fred Turner, professeur à Stanford et spécialiste de l’histoire de la Silicon Valley, « si on s’imagine comme un disrupteur, on n’a pas à s’imaginer comme un constructeur responsable. On n’a pas à s’imaginer comme un citoyen ». Cette disruption, produite par certains, ne doit pas effacer le travail de ceux que l’on pourrait qualifier de continuateurs. Leurs activités : enseigner dans une école, soigner à l’hôpital, travailler dans une usine, une boulangerie, un service de transport. Ce n’est pas spectaculaire. C’est souvent de la routine, des attentions simples, des actions précises, répétées. Pourtant, elles tiennent l’ensemble. Elles fabriquent une unité, une continuité.

It’s not the purpose of any business to give people jobs.

I think when we look back and the metaverse 100 years from now, it’ll be primarily seen as a mental health tool for human transition from being useful to being useless in the old world.

I am not sure about the last one, as the metaverse can provide an opposite effect: the real world is now pointless as everything will be better in the metaverse...