Il fallait le faire 🤣

Every time I learned a new PC programming language, the industry changed. It made it impossible to keep up wit hthese changes.

Tips:

• While you should keep up with the computer language changes, it is nearly impossible to do so. [...] go onto the major job sites and search for a current language and see how many jobs are out there. This would be a barometer to see what languages are current.

(or if you want to learn a language for fun, do it.)

• The second piece of advice is to find a few people in the companies you work for and keep in touch with them even if they leave the company.

Outside of technology, the world prefers stability

Similarly, the engine controller in cars, and medical devices like pacemakers and insulin pumps, are running on C. They don’t run on C because C is a good language with all the latest features, they run on C because the risks and mitigations for issues in C programs are well-understood and documented as part of MISRA C.

Comis about IT topics

A dev / hacker community and platform

Basically translation is harder than you will first think. Here some points and examples.

In tech, localization means making sure the words and concepts in the language the content was originally written in make sense to the person who will be reading in the language you wish to update it to. Localized content requires you to be both linguistically and, importantly, culturally fluent with the community you’re trying to serve.

Still english is the implicit default.

They got a point here:

Shared devices are a thing: the “device language preferences may not be the person’s written language preferences” fact

31 tips after 10,000 hours of programming.

A list of fonts for developers with icons

Programming is based on mathematics in the way that cooking is based on chemistry. All of cooking is chemistry but you don’t have to know the periodic table to cook. Even if you suck at math, programming still might be your jam.

🤣

Many thoughts that are applicable in real life too, not only for the IT projects

Acceptance Criteria define how a particular feature could be used from an end user’s perspective.

1. Each Product Item Backlog must hast at least 1 acceptance criteria
2. Acceptance Criteria are written before implementation
3. Each acceptance criterion is independently testable
4. Acceptance criteria must have a clear Pass / Fail result.
5. It focuses on the end result.
6. Include functional as well as non-functional criteria - when relevant.
7. Team members write acceptance criteria and the Product Owner verifies it. It confirms the PO and the team have a shared understanding of the user story.

I don't know what _why was, but the thoughts he has given us let me thinking.

All the automation in the world won’t help you if you don’t have someone around who knows what they are doing. Some people can outsource this to “the cloud”, but not everyone.

« Fais de ta passion ton métier, et comme ça, les jours où tu auras besoin de décompresser de ton travail, tu pourras même pas aller te relaxer avec ta passion. Hé oui, dommage ! »

Oui cela s'applique bien dans la programmation.
Plusieurs solutions:

• ne pas avoir besoin de décompresser, car presque chaque jour est agréable
• avoir la même passion, mais effectuer différentes tâches dedans. Dans le cadre de la programmation, avoir des projets totalement différents.
• décompresser en pratiquant cette passion en même temps avec d'autres gens (pair-programming, prendre une bière tout en programmant et en discutant, etc...)

On peu avoir plusieurs passions aussi !

Remember to code for fun and profit, not for evil

I look at the web today. Not as a programmer, but as a user of broken sites that are unable to obey the most basic rules of navigation and usability, terribly slow despite the hardware progresses. And I can only think that modern frontend development has failed.

👍
I try to do my best. But it is hard. I keep trying.

A custom DNS system into an ERP has broke up and every services of the company are now unreachable. I am surprised that a wiki or something can still be reachable....

I don't understand everything and it seems to be a very complicated situation.

What I retains is always have a backup...
For example, a Mattermost server could be hosted or duplicated elsewhere, to at least have a way to communicate with everyone.

Github Copilot écrit pour le moment des fonctions, ou des lignes de code suivant une logique initiale d'après les exemples. Nul doute que cela va s'améliorer.

Et que les jobs de développeurs vont changer

and why they are overrepresented in this field ?