1.As a software engineer, you are not there to take requirements blindly. You are there to partner with your business and product partners. That means you have to earn an equal seat at the table on product decisions.

2. Being smart or good at what you do does not give you the right to be a jerk. Empathy as an engineer is a superpower. Caring about those you work with will do more for your career than writing beautiful defect-free code.
3. As someone in the code, every day, you will see things that others will never see. You will know what's possible; they'll guess what's possible. Some of the best product features are born because engineers found clever ways to solve something. Look out for those things.
4. You are there to add value first. All the code you wrote will end up in the recycling bin of some computer if it does not add value directly or indirectly to the business. It doesn't matter how pretty your code is or how much you love it if it doesn't add value.
5. Your code should follow this pattern: Make it work → Make it fast → Make it beautiful [make it right is included in the make it work IMHO]. Reminder: You won't have a chance to make it fast or beautiful if it doesn't add value.
6. Build relationships with engineers in other teams and other companies. Learn about the problems they are solving. Learn different architecture and designs than the ones your team uses. You never know when their solutions will save you days of work.
7. You don't need permission to add value. If you see something and know you can fix or improve it, do it. Nobody will ever say to you, "why did you add all that value? WTF is wrong with you!?" Every time I've done that unexpectedly, I've earned outsized rewards.
8. 10x engineers do exist and so do .1x engineers too. If you think they don’t exist, that’s just because you haven’t worked with any of them yet.
9. Just because you think someone shouldn’t be hired, that does not mean they aren’t a good engineer. It also does not mean they don’t have a strong work ethic. A strong work ethic is the most important thing, and it's nearly impossible to tease out in an interview.
10. Advocate for junior engineers. Without junior engineers on the team, no one will grow. Help others grow; you'll grow too.
11. Have empathy for the people you interview. You could be in that situation. The set of things to know is large, even if you only ask basics. Plus, on a whiteboard, the other person is being judged. They have a lot to lose, maybe hundreds of thousands in income.
12. Even though you work with computers, your career and future depend on people. Until AI runs things, people still run the world, and relationships matter a lot. Build relationships with people outside of engineering, listen to their problems. It will change your trajectory.

TL;DR;
apply every hover effect on devices that can not support the hover effect (smartphones, ...).

Use the @media (hover: hover) media query to target devices that have the :hover effect available, or @media (hover: none).

Le message que je trans­mets aux nouveaux c’est « Pose toutes les ques­tions main­te­nant, même celles qui te paraissent honteuses, parce que plus tu tardes plus tu auras honte de ne toujours pas savoir. L’in­té­gra­tion dans l’équipe t’offre l’op­por­tu­nité de le faire. »

A more subtle unspo­ken rule dictates approxi­ma­tely how long you are expec­ted to struggle with some­thing by your­self before asking someone else to help you.

1. Don’t Disable Copy-Paste For Passwords
2. Don’t Rely on Passwords Alone
3. Drop Strict Password Requirements
4. Social Sign-In Isn’t For Everyone
5. Replace Security Questions With 2FA
6. Users Need Options For Access Recovers

5% de carburant économisé en moins pour juste 15% de temps en plus

C'est beaucoup!

7 L/100km est beaucoup. 4L/100km devrait être la norme

la climatisation pompe également de la puissance. Prendre une voiture blanche au lieu d'une noire fait gagner 10-15 degrés. Suffit de poser la main sur le capot de voiture de différentes couleurs pour s'en rendre compte. Les voitures noires consommeront bien plus en clim.

AppImage is similar to dmg files for MacOS. If you have the file, you can run the app.

A Snap image contains all dependencies. A snap app will run in isolated mode. The rights of the contained application depend on the level defined in the snap: classic, strict, or dev mode. There is therefore a real security benefit since a given piece of software will only have very controlled interactions with the rest of the system. A snap app is often two or 3 times larger though.

Flatpak is similar to Snap. Differences occur for the developers, who have nearly nothing at the beginning, and the user must approve every data request (personal data, network, process). Security has been criticized though. Executables take also a noticeable amount of storage.

The files can be put in a directory (automatically created) with the -e option. So we don't need specific commands (tar, zip, 7z, ...) anymore?

J'ai passé plusieurs décennies à écrire du C et du C++, voire même un peu d'ASM. Et franchement, je suis admiratif des quelques codeurs "safe".
C'est comme jongler avec des tronçonneuses: ce n'est pas parce-que certain y arrivent qu'il faut en faire une recommandation.

Mentoring for the win. But how frequent?The author thinks about once a week

A state of the art library for vue components

Victor Mono is an open-source monospaced font with optional semi-connected cursive italics and programming symbol ligatures.

🤦‍♂️

A shell history as SQLite database. It provides also more po

Improve the maps with an AI assistant

In response to pressure from employees, Google announced that it would delete location data of users who had used the platform to look up abortion services.

All of the largest tech giants have been pressed on whether, and to what extent, they may cooperate in investigations that seek to punish women for seeking an abortion. In June, Meta spokesperson Andy Stone told the Washington Post that the company “carefully scrutinize[s] all government requests for user information and often push[es] back, including in court.”

Donner les atten­dus, à la fois en compor­te­ment et en objec­tifs, c’est donner les moyens à la personne de faire le néces­saire pour y arri­ver… et éven­tuel­le­ment deman­der de l’aide s’il leur manque quelque chose ou si elle ne sait pas comment faire.

Même ensuite, les grilles de compé­tences sont un très bon outil pour expli­ci­ter les atten­dus de chaque rôle. Pas de « ce n’est pas mon boulot » ou de « est-ce que c’est dans mon rôle ? », ni en amont ni au moment du retour annuel. Ce n’est pas un cadre fait pour brider, mais au moins on expli­cite à l’avance ce qui est attendu de chacun.

Pas que d’eux, évidem­ment, mais aussi d’eux. Parce que les maux ne s’an­nulent pas, ils s’ad­di­tionnent, mais aussi parce que si on s’au­to­rise à ne pas respec­ter les droits du voisin en jugeant qu’il ne le mérite pas, je m’ex­pose à ce qu’on ne respecte pas les miens le jour où quelqu’un jugera que je ne le mérite pas.

Ne pas dire « oui mais de toutes façons c’est un salaud » est ce qui diffé­ren­cie l’État de droit de la vengeance arbi­traire et du lynchage public.

Nice project

Un dashboard d'accessibilité reprenant un bon paquet d'outils. C'est bien fait, complet, et ça rend la démarche d'accessibilité approchable

(via https://nicolas-delsaux.hd.free.fr/Shaarli/?-ovkdg)