Entretien avec Kristina Lead UX chez La Combe du Lion Vert qui nous partage son expérience et quotidien en tant que ergonome, service designer et UX. Pour l’écouter c’est ici : manuthechene.lepodcast.fr/entretien-avec… Bonne écoute ! #devlife #ux

Emmanuel Conrardy Oui ca sera en remote en plus 😉 Rdv le 8 septembre à 19h meetu.ps/c/2CMBV/wljq2/d

A tremendous amount of the slowness and unpredictability of software development is *caused* by accommodating the assumption that developers must/should/best work alone.

"Quiet quitting" isn't laziness. Doing the bare minimum is a common response to bullshit jobs, abusive bosses, and low pay. When they don't feel cared about, people eventually stop caring. If you want them to go the extra mile, start with meaningful work, respect, and fair pay.

Hier avec MAGIER Dan workshop living documention & développements dirigés par les tests, merci à lui ! Prise en main super rapide avec Gitpod et très complet ! Vous pouvez trouver le sujet sur github github.com/HEIWA-IT/tripp… !

Teams need to focus on learning, not just doing. When teams focus only on getting a job done, they perform worse than teams that also spend time learning from each other. Groups should be encouraged to think about learning for the future, not just on what they are doing now.

You: I submitted that pull request. Time to start a new thing! Me: can we not? Are there pull requests to review? Untended upkeep, like libraries to upgrade? To keep WIP low, avoid starting a new thing. Move anything in-progress forward first.

Best ways to speed things up: • Work on only one thing at a time. • Work as an ensemble, not as isolated individuals. • Get all the skills needed to do the work in one place. • Don't' waste time building things nobody wants/needs. • Trust people to do their work. 1/2

Software teams have two jobs: 1) produce valuable software; 2) increase, or at least sustain, their ability to do #1. Software development is unique in that ignoring #2 will rapidly destroy #1.

« I’m being vulnerable because the alternative is to be an impostor » — @tdpauw #FlowConFR

La rentrée MTG:Montpellier continue, avec cette fois un évent en présentiel sur la méthode Mikado, présenté par Emmanuel Conrardy ! Et pour celles et ceux qui ne peuvent pas être présent·e, un live youtube est prévu 😉 meetu.ps/e/Lw21X/ClvlK/i

On remet ça chez R&H ! Le refactoring c’est la base, non ? Il existe différentes approches et on va en découvrir une : ) Il y aura aussi un moment sur place autour d’un apéro pour se rencontrer et partager nos expériences. Merci MTGMontpellier !

Do you struggle to code after a meeting? In the morning? Do you struggle to pay attention to a meeting after a deep work? We know that context switching is costly but we rarely talk about how we can be more interruptable. Here's a simple interruptible workflow that you can try:

Emmanuel Conrardy nous présente le refactoring de code avec la méthode #mikado Et pour celles et ceux qui ne peuvent pas être présent, c'est en live sur youtu.be/S4njaoRHNRQ 😉 Merci au Cabinet Recherches et Horizons pour leur accueil 🙏

“It’s the circle, the circle of life” 🎶

⚖️ Bottlenecks vs Opportunities I believe you should hire because of *bottlenecks*, rather than *opportunities*. What does it mean? 👇

Back-to-back meetings drain our brains. We need downtime in between to recover. New research: even 10-minute breaks between meetings are enough to reduce stress, improve focus, and boost engagement. Instead of defaulting to 30/60min meetings, we should schedule 20/50min blocks.