Les liens de la mer numérique
Maintenant en redressement judiciaire (https://www.journaldunet.com/ebusiness/internet-mobile/1508391-sigfox-place-en-redressement-judiciaire/). Dommage car le service proposé semble incroyablement utile pour l'IoT. Et peu cher (à partir de 3€ par an), donc accessible.
TL;DR;
En attendant, l’autonomie c’est la première qualité que l’on recherche chez un stagiaire en développement.
mais
Encore une fois pas de stress, tu es là pour apprendre, alors apprends de tes erreurs.
Un stagiaire en dev web n’est pas obligé de facturer tout son temps au client, loin de là.
Il est avant tout là pour apprendre même s’il doit être un minimum productif.
Durant ce laps de temps, il est très important que le stagiaire progresse de manière rapide pour l’entreprise.
Du point du vue du stagiaire:
Qu'est-ce que je peux apporter à l'entreprise en tant que stagiaire ?
Damien de l’équipe WeLoveDevs te conseille la chose suivante
Si cela ne fonctionne pas avec les RHs, il faut passer par les managers et les devs dans les équipes. Cela fonctionne particulièrement dans les grosses boîtes. Ce sont les managers qui ouvrent les postes 90% du temps, pas les RHs.Sur le long terme, c’est le stagiaire développeur avec le meilleur mindset qui devient meilleur.
Aussi,
Pour former quelqu'un pendant 6 mois et le laisser partir, il faut une bonne raison.
et cela continue, ce n'est plus un TL;DR; là x)
floc has been blocked by a majority of services (framework such as sveltekit, ....). So Google comes back with a new one.
Topics looks better.
The operation appears simpler than FLoC. First, the browser collects the interests for the week. It stores the information locally for the last three weeks. It is not communicated to any server and is deleted after this period.
When the person visits a site, it can draw from the local pool. Only one interest per week, for a maximum of three. Via Topics, a site would not go any further.
A map of the lighthouses around the world 👍
INTRODUCTION
WALTER PLECKER WAS AN ASSHOLE.In the 1920s, he was registrar of Virginia’s Bureau of Vital Sta-
tistics, the state government office that controlled birth, death,
marriage, and divorce records (http://bkaprt.com/eia/o0-01/). As
a frothing-at-the-mouth white supremacist, Plecker was terri-
fied of interracial marriage. Its very existence, he insisted, was
the result of poor categorization: white people were marrying
non-white people only because the government hadn’t labeled
them “correctly.”Plecker decided that he could use bureaucracy to change this,
and he was right: all he had to do was relabel Virginia’s racial
categories, and racist laws took care of the rest. He reduced the
number of racial identity categories to just two, then altered and
enforced documentation to reflect his definitions.This meant that a very small and specific group of people
were labeled white, and everyone who fell outside of Plecker’s
narrow view were not—and their lives changed accordingly.
The government saw them differently, identified them dif-
ferently, treated them differently. They no longer had access
to the same public spaces, the same schools, the same ser-
vices and safety nets afforded to white people. Marriages were
invalidated. Children were separated from parents. Virginians
lost agency over who they were—all because Walter Plecker
changed a label.Changing a label is a design decision—one calculated, in this
case, to disenfranchise specific human beings.Now, most of us don’t have Walter Plecker’s job. We are,
instead, designers, developers, copywriters, strategists. We
work on the web, and we may not think our work carries that
same weight.I'm here to argue that it does. Whatever our role, we are
designers of information. Our choices alter the presentation
and flow of human knowledge. We control how people find,
understand, and use information in every facet of their lives.‘We must be very, very careful.
How designing information can change the lives and the world
TL;DR; Use hsl isntead of RGB to create a gradient. This will avoid a grey zone. But using hsl is not available in CSS for now, so we can use a linear-gradient from a multiple of colors instead. Each color have to be similar to its neighbors... and it works !
and here the tool: https://www.joshwcomeau.com/gradient-generator/
Critiquer Rust sous prétexte que c’est un langage complexe conduit à passer à côté de ce qui fait sa force : il est pensé pour être expressif, ce qui signifie qu’il y a beaucoup de fonctionnalités, et dans la majorité des cas c’est ce que vous attendez d’un langage de programmation.
L'article est bien complet !
Mon avis: utiliser Go pour le code qui doit être déployé demain, Rust pour le code qui devra rester en production tel quel pour les 5 prochaines années
—Grzegorz Nosek
peut-on encore légitimement parler « d’une langue française » ou doit-on désormais parler de « plusieurs » langues françaises ?
Mais notre réponse scientifique est qu’il existe bien un corpus de règles générales fondamentales, une matrice de base sur laquelle viennent se greffer tous les usages Concernant les expressions figées, qui semblent a priori les plus variables
Display an item on scroll.
A tool similar to Shaarli: a bookmarks service that provide magic link (permalink), categories, etc...
Fixed my issue on Arduino Genuino
- I still don't know very much.
- The hardest part of software is building the right thing.
- The best software engineers think like designers.
- The best code is no code, or code you don't have to maintain.
- Software is a means to an end.
- Sometimes you have to stop sharpening the saw, and just start cutting shit.
- If you don’t have a good grasp of the universe of what’s possible, you can’t design a good system.
- Every system eventually sicks, get over it.
- Nobody asks "why" enough.
- We should be far more focused on avoiding 0.1x programmers than finding 10x programmers.
- One of the biggest differences between a senior engineer and a junior engineer is that they’ve formed opinions about the way things should be.
- People don’t really want innovation.
- Your data is the most important part of your system.
- Look for technological sharks.
- Don't mistake humility for ignorance.
- Software engineers should write regularly.
- Keep your processes as lean as possible.
- Software engineers, like all humans, need to feel ownership.
- Interviews are almost worthless for telling how good of a team member someone will be.
- Always strive to build a smaller system.
A blog post as response to it ?