It was also a bit funny as we were discussing some management challenges, and I could refer them to the talk I did at #devlin2024 last week plus the talk I did with Jakob Wolman at #cphdevfest that we will repeat at #oredev next week.
Good to know that we talk about relevant things :)
I got lost in conversations and listening to talk, which is why my posting stopped :)
Which is a bit too bad as there are many good things to take home from #devlin2024
I did my talk “We need more managers” - not totally happy with it. I had too much content so had to go fast at the end.. darn
You can use scratch refactoring to learn about code.
You can use it to see if you understand it, if the test still passes or why it doesn’t. Lots of learning.
Often you throw away the refactored code (unless it improves the code) - don’t fall in love with it
@emilybache.bsky.social #devlin2024
Use the IDE:
Look for highlights
Fold the code for overview
Scan how it looks visually, like
* big methods
* long lines of codes
Look at structure
@emilybache.bsky.social #devlin2024
Heuristics of reading code from Emily:
Scanning practise:
Codesmells are easy to spot; they might not cause a problem, but it can imply that something bigger is wrong.
Code smells have names, so you can talk about it
@emilybache.bsky.social #devlin2024
@emilybache.bsky.social #devlin2024
Reading legacy code is about sensemaking and context.
We want to quickly understand context, and find a good place to start making changes.
A study of eye tracking showed that people who scan find the bugs faster than people who read the code from one end.
@emilybache.bsky.social #devlin2024
I won’t be posting much from the next session :)
Looking forward to listening to @emilybache.bsky.social talk about “Reading Legacy Code Effectively”
#devlin2024
Not much news for me in the talk of Robert Gistvik; part of it are in my workshops.
It was nice to get confirmation of what I know and I like the way it was presented 💕
And perhaps the reminder will help me do more of these things.
#devlin2024 Robert Gistvik
We don’t choose all our anchorings, but we can add to them.
You become what you think, you become what you do.
Things I want you to take away:
Your brain is lazy, you can feed it with the stories you want, you can create anchors.
#devlin2024 Robert Gistvik
The brain ignores “not”. It also doesn’t distinguish between true memories and stories we make up. They are the same to the brain.
We can use this to our advantage and anchor things to taste, touch, emotions, smell etc.
And we always have our emotions with us.
#devlin2024 Robert Gistvik
You can prime your brain to look for specific things…
If you focus on one thing you will observere that more, do that more.
And it needs to be positive.
In football freekick: “I will score” works better than “I can’t miss the goal”
#devlin2024 Robert Gistvik
Do you feel thirsty?
Then you drink water. And afterwards you feel less thirsty.
But the water has not arrived in the places you need it. Your brain just tells you how your body will feel later based on history.
The brain maps things as well like music with training.
#devlin2024 Robert Gistvik
Might be a bit slower with the next one as I will be processing and translating Swedish :-D
You will become what you think by
#devlin2024 Robert Gistvik
Important:
It is not a silver bullet. There are no right or wrong answers.
Dysfunction mapping is _one_ way of looking at the problems. There are many.
Culture influenced from the top, process influences from the “bottom” - do it incrementally.
#devlin2024 Michael Lloyd
Instead of only having culture aspirations, look at what we want to achieve and symptoms that this is not happening.
Leaders can work with culture dysfunctions.
Observe where the culture is not ideal, find symptons, purpose, experiment, measure.
#devlin2024
Things to think about.
Dysfunction mapping is a non-linear process…
Michael Llyod’s experience is that teams can influence some thing, but rarely culture and values.
How can we help create leadership experiments?
#devlin2024
Dysfunction mapping has different card sets to help get ideas, like solution cards, measure prompt etc
Step 5: measure the impact to seen if the symptom(s) are moving in the right direction.
Make the changes visible like having a backlog of dysfunctions.
#devlin2024
There can be many causes - we pick AN dysfunction and experiment to figure out if solving this will remove or diminish symptoms.
Step 3: understand the purpose of fixing the dysfunction
Step 4: hypothesize a solution. Simple actionable steps to get towards that solution
#devlin2024
Dysfunction mapping:
Step one: listen and observe to create a list of problens
Step two: look for symptom and group; eg “Missing quality focus”
Now we have the beginning of a hypothesis, and we can start experimenting by working on a potential dysfunction/underlying cause.
#devlin2024
At #devlin2024 realising that I am totally out of the habit of posting…
Devlin is a small developer conference with all the sides of what that means.
We are starting out with an introduction to dysfunction mapping by Michael Lloyd.
Finishing my presentation for #devlin2024 for tomorrow.
Being asked to speak at a developer conference about needing more managers was not what I expected, but I look forward to it.
And then of course I decided to change the order and the flow :D
As I do.... Always learning, always changing :)
Next week I do a half day workshop on psychological safety at #devlin2024 in Linköbing
Sign-up closes in 2 days, so you still have time (click the green button with "Anmäl dig nu!"):
events.responsive.se/component/ci...
Linköbing is only a 47 hour walk from Stockholm, so what are you waiting for?
