To meet the demands of the European Commission's Digital Markets Act—slated to be enforced in March 2024—Microsoft must make its apps easier to uninstall, its default settings easier to change, and its attempts at steering people toward its services easier to avoid.

It includes Bing, default apps, Edge, etc...

Any > 40-year old developers out there that'd like to share their perspective? How did you grow (technically, managing, etc...)? Picked up fields over others (embeded systems over web app, for instance)?

Responses:

• I push others to do better without them noticing it
• Technical skills become obsolete over time but human skills stay relevant. People, values and norms change so you have to relearn them too.
• Keep learning, write a lot and communicate more.
• I took every advice on the Internet and did the opposite: playing the pendulum between team lead and dev; more and more a specialist in nothing; being able to talk to stakeholders and convert their input into software is by far my most valued skill; being a former manager means I generally understands my boss pretty well.
• I do more mentoring than I used to. I learned more about working in teams.
• I learn that less code is much, much better than more.
• I don't write many queries any more but I do write PowerShell and Typescript. I don't manage a server, it's hundreds. [...] I've taken on more senior roles by thinking beyond just databases.
• The more paradigms and patterns you know, the better you’ll be at expressing yourself in your language of choice. Learn as many languages as possible. Don’t grow too comfortable; challenge yourself regularly.

Currently at: https://elk.zone/mastodon.social/@nicklockwood/111280337863596402

Un état des lieux des différentes alternatives libres soutenues par Framasoft depuis des années.

If you have a personal website: how did it change your life?

Starting with the right HTML tags and using semantic HTML is a first easy step compared to retrofitting accessibility.

It related to landmarks, menus, checkboxes, buttons, headings, bold and italic texts,

Old school GIFs put on website of the 2000

Make it accessible #idea #project

Maybe some tools to remove these watermarks will be developed soon.

59 % des moins de 25 ans et 58 % des 25–34 ans sont persuadés que l’argent rend libre et contribue fortement au bonheur. Une proportion plus élevée que les autres tranches d’âge, à l’image des 50–59 ans qui sont 40 % à le penser.

Ce qui rend heureux c'est ce que tu n'as pas...

"Okay, here's the scenario. You are a crew member on a starship."
"Cool."
"Space travel is slow, you'll be stuck with your crewmates a long time."
"So we must get along."
"Yes. Communicate, listen, share limited resources."
"I can do that. What's the starship called?"
"Earth."

A list of libraries meant to build web apps or the environment around (logging, etc...)

Two good rules of thumbs. I often use them in JS and Vue hints about avoiding v-if in v-for directives.

A framework to build applications with privacy, safety, and user experience in mind.

It is developed and released by the Cult of the Dead Cow. The core is written in Rust.

A related article on the topic: https://www.engadget.com/americas-original-hacking-supergroup-creates-a-free-framework-to-improve-app-security-190043865.html

2,529 APIs are listed at the time of consulting

The author proposes a serie of question instead of sentences.

This website is a single HTML file. It simply uses the #anchor suffix (from 1992) and the :target CSS selector to show and hide pages/content.

This setup1 is databaseless, javascriptless, and buildshit-free, so you can edit your website with a text editor and upload it somewhere2 like a normal person.

Instead, it could be better to use:

• community pattern: everyone else is doing it. Everyone sees it they know exactly how and why it is there.
• readability pattern: created for the sake of making more readable code. The only true goal is writing code that anyone can reason quickly about.
• performance pattern: squeeze the code for maximum performance, and it can degrade readability.
• guardrail pattern: it exists to avoid known foot guns such as magic number

Often people see "best practices" as community, readability, or guardrail patterns. It is also time as professional that we use a richer vocabulary.

Recommended rust crates and resources can be found at the end of the guide

There is an on going race between the AI that catches up the latest technology innovation and the innovation that blocks AI to grow :)
In our case, the artists can use the Nightshade to make noise to the AI input.

More about this technique: https://arxiv.org/pdf/2310.13828.pdfttps://arxiv.org/pdf/2310.13828.pdf

Alors on attend la suite et on verra ce qui tient de ce discours, une fois l'affaire tassée.

Parce que bon, si la fonction publique est tenue à la plus grande exem­pla­rité du fait des pouvoirs qu’elle détient; les ministres devraient en être le parfait exemple....

How to better organise files. I am aware of the PARA method, but this one also seems useful.

An argumentation for rust

An experience with Axum.

The good old paper and a pen still work well. I am also so messy with my lists that I can write them on any old paper sheet or piece of.

It is valuable to offload what is in your mind, and see the current progress.

Create your own free website.
Unlimited creativity, zero ads.

This is a super simple service for generating different HTTP codes.
It's useful for testing how your own scripts deal with varying responses.

Custom response headers can be set, as the HTTP status code.

A mission to accomplish: Working with the guidelines established by the manifesto and the social etiquette to progressively transform the culture of the internet and beyond.

There are three commitments to it:

• The commitment to social responsibility and partisanship
• The commitment to collective well-being and personal growth
• The commitment to rehumanizing social relations and reversing the process of social alienation

The 4 examples are from the WAI, Deque, U.S. Web Design System et Tommy Feldt.

• use lang for the language of the page, then the other parts of the page with a different language
• support different writing direction. Logical CSS properties help.
• handle text expansion with adaptive layouts. Avoid to truncate the text.
• apply a minimum width to avoid text shrinking in other languages. Also think about the height.
• readable typography is important
• make sure every user-facing string is translated such as alt-text, title or desc nodes in SVG.
• different languages have different word order, so avoid string templates
• ensure consistency of microcopy

  Microcopy is all the little bits of text that appear throughout the site: the nav links, the sidebar headings, the form field labels, stuff like that. When microcopy is written and used consistently, the site layout becomes much more predictable, and users won't have to guess

It means the atoms and some molecules in atomic design.