Software Crafting Sociotechnical Systems complex-adaptive-systems-thinking
Paris, Île-de-France, France
"Non mais pas vraiment", 'Nan mais moi....", "Ici c'est different..." ou autant d'autres reactions qui peuvent surgir lorsque nous abordons des sujets tel que le mérite.
A l'aide de la Communication NonViolente, nous vous proposons de ralentir sur cette notion tout en ralentissant sur ces petites phrases qui apparaissent d'elles memes sans meme avoir besoin de les chercher.
Prendre le temps d'écouter nos "et moi et moi", les résistances et les levees de boucliers pour créer des espaces de non violence en soi et éventuellement se donner une chance de voir les choses différemment.
Beyond red -green-refactor, beyond test-first,
Why do TDD even in a hackathon? Even in code you'd throw away?
I shall walk you on the way i teach TDD to people from the intro
(so if you are a full beginner you are also welcome), exploring a lot of specific techniques (lazy naming, branch notation etc) then beyond all that into the discussion of why it works and how to exploit that : TDD as socratic discussion with the code, TDD as accessibility, TDD as a practice of dynamic meditation.
Ok au-delà du "test first", puis "test guiding" puis "Red green refactor" : de quoi on parle quand on parle de TDD?"
Dans cette session on couvrira pourquoi faire du TDD même si on est dans un hackathon et qu'on va jeter le code: TDD en temps que dialogue socratique, mindfulness & TDD, l'intention de design derriere l'outil.
Pour ce faire je vous montrerai d'abord comment j'apprends le TDD aux debutants (du coup, debutants bienvenus aussi!), en ralentissant à chaque partie et faisant les techniques de lazy-naming, branch reduction, purposeful-bad-faith, etc
Puis nous plongerons au-delà de l'intro
We do an ensemble/mob programming over a kata, but some of the participants are secretly saboteurs! Like a game of "werewolf"
The idea is that a saboteur does not want to be found right? So a saboteur will make believable sabotage! And hence we end up living team dynamics we could live in real life situations and the team tries to solve them, while coding, and fighting the sabotage instead of the saboteur.
Every workplace, every community, and in fact every social interaction, is governed by various forces, hidden power structures, implicit oppression and submission. We oppress people by accident, and we are oppressed by others by accident.
Bourdieu's social theory (with concepts like “symbolic violence", “cultural capital” and “hexis”) explain what is happening. By understanding what he meant, we learn how each of us influences and is influenced by the people around us, in ways that we wouldn't expect.
This talk tries to make Bourdieu's ideas accessible. Learn how to improve your environment immediately; see why meritocracy is a dangerous lie; recognise oppression and submission when it happens; and gain the tools to fight it day to day.
Without any big conspiracy (nor any bad person on top) We have created dysfunctional corporate cultures where waste reins, sadness is rampant and the majority has abandoned hopes of changing.
It is a system where every participant is oppressed and also complicit in their oppression.
This talk aims to help you see the system and in seing it arm yourself to fight it. This talk also aims to convince you that you can, in fact, make a difference.
Ok beyond the "test first, then test guiding then Red green refactor" stuff : what is the fuss all about?"
In this hands-on we'll cover that, we'll cover why to do TDD even if you're doing a hackathon and throwing away the code: TDD as socratic dialogue, tdd as mindfulness, the design goals behind the tool.
To do that I'll start by showing you how I teach TDD to people (so, if you are a beginner you are also welcome), slowing down in each part and doing techniques of lazy-naming, branch reduction, purposeful-bad-faith, etc
Then we shall dive into the why.