Lmst
Login

#NewCrafts

NewCrafts Conferencenewcrafts
2025-06-03

The first round review of the talks is complete!
Our editorial team has just wrapped up the first pass through proposals — and what a journey it’s been.

🙏 A heartfelt thank you to everyone who shared their brilliant, bold, and occasionally unconventional ideas. Your passion and creativity made this selection process both challenging and inspiring!

👂 In the meantime…
What’s one topic you’d love to see on stage at NewCrafts this year? Drop it in the comments — we’re listening.

Clare Sudberyclaresudbery
2025-03-24

I really enjoyed keynoting the @newcrafts community crafting event in Paris in 2023, with my Compassionate Refactoring talk. It’s about kindness and forgiveness, and the paradox that the more you accept and handle bad code, the more likely it is you'll end up with good code.

You can watch the talk here: vimeo.com/showcase/10559193/vi

Jessicajessicab@hachyderm.io
2024-06-02

Working on my slides for #NDCOslo

There's a few tweaks I want to make since my talk at #NewCrafts

While I'm at it, I'm sneaking in a couple of unsubtle hints. Every little helps on trying to get those green votes 😂

Green square with the text "Don't forget to vote!" in black
Maaret Pyhäjärvimaaretp@mas.to
2024-05-28

I watched @ez test on video and narrate for a full length talk, and I recommend that.
vimeopro.com/newcrafts/newcraf

My highlights:
- Definition of #ExploratoryTesting: testing, thinking what and why it matters while doing it
- Reference to microheuristics, decision rules for the moment and shoutout to @alex_schl
- #curious as polite way saying you have degrees of disagreement on how great things are

Thanks for recording #NewCrafts, many talks worth watching there.

Lisi Hockelisihocke
2024-05-28

The recording of my talk on "Team Transformation Tactics for Holistic Testing and Quality" is already available! 🎉 vimeopro.com/newcrafts/newcraf All the other talks had been published as well, so many gems to discover 🤩 vimeopro.com/newcrafts/newcraf

Krisztina Hirthyellowbrickc
2024-05-26

My talk about feedback-based product development instead of thinking in projects was made available. It is time to acknowledge that digital products can't be created on assembly lines - if we want to enjoy this work, that is.

vimeo.com/949430441


Trond Hjortelandtrondhjort@hachyderm.io
2024-05-23

Excerpt from my talk on human-centred system design at @newcrafts. See the full talk here: vimeo.com/949428992
#SocioTechnical #OpenSystems #newCrafts

Lisi Hockelisihocke
2024-05-20

their tenth, my first, and what a memorable one | A Tester's Journey: NewCrafts Paris 2024 - A Memorable Conference to Rave About lisihocke.com/2024/05/newcraft

Maaret Pyhäjärvimaaretp@mas.to
2024-05-19

@lisihocke @newcrafts Lisi, heart felt thank you for these notes. Another great #newcrafts and you enable us who didn’t travel to enjoy the contents. ❤️

Lisi Hockelisihocke
2024-05-18

"Technical Neglect" by @kevlin

Sketchnote of keynote "Technical Neglect" by Kevlin Henney at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "We tend to mix up cause and effect" Technical debt became a term - let's talk about neglect instead Habituation and learned helplessness - accepting it's just like this Or teams learn how to deal with neglect yet not how not to create it Quote, framed: "As an evolving program is continually changed, its complexity, reflecting deteriorating structure, increases unless work is done to maintain or reduce it." by Meir M. Lehman It's not due to bad development - it's in the nature of change Our attention span is limited, we can only focus on one thing Insight, circled like a cloud: What makes a metaphor effective is familiarity to its audience "Debt" is familiar yet can be considered positively "Unhedged call options" only makes sense in fintech "Legacy" connotated positively outside, costly in tech "Housework" sounds fitting yet most people in tech don't do or manage it, doesn't work Use LLMs to generate code? Congrats on automation of legacy code creation and your new role debugging and fixing it It was never the absence or presence of the tools Insight, circled like a cloud: Unmanaged technical debt is the problem; therefore, things are harder than necessary Insight, circled like a cloud: maintenance counters inaction - what we don't see Continued in next imageSketchnote of keynote "Technical Neglect" by Kevlin Henney at NewCrafts Paris Conference 2024, part two Learn to see the neglect - not refactoring, testing, reviewing, recording decisions, revisiting decisions, updating technologies, turning down the noise Insight, framed: Tackle neglect now, part of feature work Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"Bring meaning back to your retrospectives (no matter your role)" by @sofiakat

Sketchnote of talk "Bring meaning back to your retrospectives (no matter your role)" by Sofia Katsaouni at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "Retros are often measured by number of action items" Let's restart seeing retros as place to build meaningful trustful relationships with curiosity, vulnerability and empathy Insight, circled like a cloud: People often share evaluations instead of observations Decreases likelihood that people understand Invite people to share concrete things to meet them where they are Remain curious and help people reflect Insight, circled like a cloud: Feeling is a felt sensation in our body that tells us about our beliefs and what is important to us - let's not confuse them with thoughts "How are you feeling" can be a very difficult question - try to go for alternatives If you ask questions, check in from time to time if it's okay to continue Insight, circled like a cloud: Needs refer to our core values and deepest human longings - let's not confuse them with strategies to meet needs Our brains try to simplify the processing of information by creating shortcuts - resulting in cognitive bias, like confirmation bias, group attribution error, headwind/tailwind bias Insight, circled like a cloud: The observer is as much part of the observation as what is observed, including biases - not objective, sharing experience Observation iceberg by Roxy Manning: external, internal and systemic Continued in next imageSketchnote of talk "Bring meaning back to your retrospectives (no matter your role)" by Sofia Katsaouni at NewCrafts Paris Conference 2024, part two Insight, framed: Showing up with empathy and curiosity is up to each one of us Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"My Team Is High Performing But Everyone Hates Us" by Stephen Janaway

Sketchnote of talk "My Team Is High Performing But Everyone Hates Us" by Stephen Janaway at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "High performing teams can make mistakes that destroy them" Brand-new product and team, all shiny Got told to treat the rest of the organization as black box Worked super well: sponsored; clarity and focus; no dependencies or debt; great safe team spirit; shared, supported, self-organized One small entrepreneurial team against the world Autonomy was great - detachment was not Sponsor left Other teams jealous - we had siloed ourselves Challenge to keep spirit People got bored Insight, circled like a cloud: In times of failures resist that urge to just look at the negative Playbook for happy people in happy teams Point one: Set clear expectations - collaborate, make making fun, share and iterate Point two: Make hiring and joining great - spread the net wide, sell your team, make joining delightful Point three: Make your own tech choices - no debt, developer agency, support a golden path Point four: Share learning - competitive edge: share what you want to learn, provide time and space, encourage teaching - force multiplier Point five: Measure health - ask how things are, work out what's important, actually get some actions Point six: Check in regularly - measure individual's health: timely, bite sized chunks of performance feedback; and keep it fun Continued in next imageSketchnote of talk "My Team Is High Performing But Everyone Hates Us" by Stephen Janaway at NewCrafts Paris Conference 2024, part two Insight, circled like a cloud: Change will come, watch for the signs; build trust inside and outside the team; if all else fails, keep building high performing teams anyway Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"Shades of Conway's Law" by @tdpauw

Sketchnote of talk "Shades of Conway's Law" by Thierry de Pauw at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "Similar observations in different industries around the same time - organization design, product design, architecture" The Mirroring Hypothesis - Colfer and Baldwin First empirical evidence for the software industry in open source - better quality in open structure Information hiding allows individual contributors work independently from each other Many people paraphrased Conway's Law - all coming to the same conclusions, list of four points: Systems are isomorphic to the organization Underlying Conway's Law is the homomorphic force Organization and systems are congruent The organization must be compatible with the system Sketch figure with speech bubbles: "When software reflects the organization structure, it won't allow the organization to change" and "If architectures of system and organization are at odds, the one of the organization wins" - footnote on the latter: unless systems are long-lived (Reverse Conway's Law) Insight, framed: Inverse Conway Maneuver: Break down silos that constrain the team's ability to collaborate effectively Organizational flexibility is important to effective design - we should be able to change it to build what we should build Incremental software development impacts the organization Insight, circled like a cloud: Managers are architects and vice versa Continued in next imageSketchnote of talk "Shades of Conway's Law" by Thierry de Pauw at NewCrafts Paris Conference 2024, part two Insight, framed: Grow the team with the system; start as small as you can and grow as you need to - only way to keep control Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"Power Structures and their Impact on Software" by @ahl

Sketchnote of keynote "Power Structures and their Impact on Software" by Andrew Harmel-Law at NewCrafts Paris Conference 2024 Sketch figure with speech bubbles: "Team structures have a massive impact - power structures do too" and "If we're aware we can do something about it" Part one: Depressing facts Code is knowledge; structuring of code is the management of knowledge Code is a record of knowledge Code is power; gatekeepers are everywhere Code is knowledge and societal power; gender bias in open source PRs Code is solidified knowledge and power; visible in big balls of mud Code is structured knowledge and power! Elites are groups of friends using backchannels - end up as gatekeepers; code is not neutral Part two: Why so depressed? Three prerequisites for unequally distributed power - you only need two: control of punishment; control of information; individual charisma - people are scared to change certain code because of who wrote it Insight, circled like a cloud: We fix it by listening to everyone and be painfully inclusive, learn and fail, challenge our egos Part three: Freedoms! Freedom to reorganize Freedom to move Freedom to disobey Insight, framed: Anyone can make any decision but must seek advice from all affected parties and people with expertise in the matter before Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"Don't Hit the Iceberg" by @diana

Sketchnote of keynote "Don't Hit the Iceberg" by Diana Montalion at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "A good day in my life is when the bug we found is in the code" - footnote: not relationships in systems Seen people repeat the same mistakes all over again expecting different results We are moving from software to systems You are a system of thinking; we are; we can change it; we can invent them Insight, framed: Iceberg model systems thinking, list of four points: Events - what's happening? (visible) Patterns and trends - what's there? Structure - how are patterns related? Mental models - what values and beliefs shape the system? (invisible) Point one: value knowledge work; we need both knowledge stock for efficiency as well as knowledge flow for effectiveness Insight, circled like a cloud: Can you learn new things, adapt to new circumstances, and help others learn? Point two: Think well together; improv teams are the ultimative generative team "Yes, and ...": even if you disagree, acknowledge and find out reasoning; leads to systemic reasoning Point three: Discover leverage points; we often know where to find them but either still push change in the wrong direction or hardly anybody will believe us Design for emergence - will allow innovation Point four: Change the paradigm; let go of what doesn't work and go for what does Move away from the "Mom Test" Continued in next imageSketchnote of keynote "Don't Hit the Iceberg" by Diana Montalion at NewCrafts Paris Conference 2024, part two Insight, framed: When you feel like a cog in the system, imagine that you are the architect. What would you change? Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"Effective software design: The role of men in debugging patriarchy in IT" by @kenny_baas

Sketchnote of talk "Effective software design: The role of men in debugging patriarchy in IT" by Kenny Baas-Schwegler at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "From the moment I could talk, I was ordered to listen" Patriarchy - literally the rule of the father Culture is based on symbols - they can give power "Male domination is so rooted in our collective unconscious that we no longer even see it" - Pierre Bourdieu Insight, framed: Patriarchy reinforces our collective unconscious and preserves symbols of patriarchal power Insight, circled like a cloud: Patriarchy influences who and what can be discussed, thereby affecting the knowledge that is incorporated into our software design We play roles - and they can get stuck (the nerd, the weird, the emotional) Contradicting ideas are difficult to share then A role is larger than a person - can we relate to the need they have so we can talk about solutions? A person is more than a role - give more air time to underrepresented roles so we learn to relate to their needs Insight, circled like a cloud: When roles become fluid, we will get more and better solutions Create awareness and role fluidity before asking for (strong) opinions when discussing design Boys get caught up in the circle of shame and suppression of emotions leading to withdrawal or violence Resolve every conflict within the group Continued in next imageSketchnote of talk "Effective software design: The role of men in debugging patriarchy in IT" by Kenny Baas-Schwegler at NewCrafts Paris Conference 2024, part two Insight, framed: If you realize your privilege that you benefit from the system more, see whom you can help with it. We're all part of it and have to start with ourselves. Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"Human-centred system design" by @trondhjort

Sketchnote of talk "Human-centred system design" by Trond Hjorteland at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "Unhappy people can't do their best work" Why do some teams work better than others? 1940 group climate (structures) experiments by Lewin, Lippitt and White - teams just being left alone not working (laissez faire) 1951 beginning of socio-technical systems (Trist and Bamforth) - birth of self-managing teams 1950 "Open Systems" (Bertalanaffy) 1959 "Characteristics of Socio-technical Systems" (Emery) 1962-1967 Norwegian Industrial Democracy Project (Emergy and Thorsrud) - People have intrinsic needs; list of six points: elbow room, variety, learning on the job, meaningfulness, mutual respect and support, desirable future Measure these to see where you are now 1967 Organizational design principles (Emery) - redundancy of parts versus functions, moving to group tasks 1971 first participative design workshop (Emery) diffusion phase begins - no expert needed, people have the context 1974 "Participative Design" (Emery and Emery) 1993 "Participative Design for Participative Democracy" (Emery) Bion's basic assumptions, list of three points: dependency, fight/flight, pairing 1962-65 conceptualization of L22, causal texture, full open system (Emery and Trist) - the environment changes the system and vice versa 1999 searching the theory and practice of cultural change (Emery) Continued in next imageSketchnote of talk "Human-centred system design" by Trond Hjorteland at NewCrafts Paris Conference 2024, part two Insight, circled like a cloud: People have to feel accountable for effective implementation Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

"From Pilot to Transformation: Embracing the Reality of GenAI at Scale" by @patrickdebois

Sketchnote of keynote "From Pilot to Transformation: Embracing the Reality of GenAI at Scale" by Patrick Debois at NewCrafts Paris Conference 2024 Sketch figure with speech bubble: "What can BuzDevDataQASecOps do for delivering GenAI?" Prompt engineering looks simple but requires lots of trial and error; moved to: Flow engineering New model requires lots of refactoring Which model to pick? List of four points: Prompt length differs Bigger is not always better Lost in the middle phenomenon - when a model forgets things in the middle Token pricing Sketch figure with speech bubble: "Pick one model to get started and learn from there" Quantisation allows models to run locally Choose and apply models based on use cases Insight, framed: know what the model is trained on - beware of bias in the models Opt out of AI training Data SBOMs Bring your own data into the model; list of two points: Retrieval augmented generation Finetune, rather patching Can do access control this way Insight, circled like a cloud: keywords versus question search takes time to get used to for users Agents: stop building the thing, build the thing that builds the thing Orchestration layer to bring it all together Frameworks start to stabilize Use good engineering practices, tweaked to GenAI - test and observe all the things Insight, framed: Platform, enablement and governance to make GenAI scale Sketchnote author: @lisihocke@mastodon.social
Lisi Hockelisihocke
2024-05-18

With , @newcrafts celebrated their tenth edition, and I celebrated my first . 🎉 It was a blast! Highly recommend to meet this amazing crowd and broaden your horizon on all things socio-technical systems. Here are the I took during the conference. A thread. 🧵

Trunk-Based Thierrytdpauw
2024-05-17

Whether a PR is accepted or not is a power one has over someone else. That is an elite that decides on this. And an elite is not necessarily the more competent or talented people.

@ahl talked about power structures and their impact on software at @newcrafts

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst