WordCamp Canada was amazing! | No Music Version 🔗 **Source:** [WordCamp Canada was amazing! | No Music Version](https://www.youtube.com/watch?v=bMC1rlipclw) > [!note]+ Document Notes > tags: [engineering-metrics, team-performance, ai-in-software] > author: [MISSING] > source: [MISSING] > reference: [https://www.youtube.com/watch?v=L0ZTdw5flsw] > date created: > > # 🏷️ Title: Measuring team performance isn’t getting any easier > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H3] Draft a WordPress.org-friendly metrics rubric — blend DORA + SPACE. https://leaddev.com/reports/engineering-team-performance-report-2025 #articleseed - [H5] Pilot a “DORA + outcomes” dashboard — pick two business KPIs. https://cloud.google.com/devops/state-of-devops #xref - [H6] Add monthly qualitative health checks — rotate facilitators. https://www.youtube.com/watch?v=L0ZTdw5flsw&t=880 #addendum - [H10] Track post-release quality signals — incidents, reverts, churn. https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1547 #articleseed - [H12] Propose an L&D OKR for AI skills — report quarterly. https://leaddev.com/reports/engineering-team-performance-report-2025 #share - [H14] Run curiosity clinics — pair seniors with AI-native juniors. https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2225 #share - [H15] Document “AI done right” playbook — prompts, reviews, guardrails. https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2445 #articleseed - [H11] Require context with metrics — anomaly notes by owners. https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1779 #aphorisms - [H17] Start peer-led AI hours — weekly, agenda-less, show-and-tell. https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2781 #articleseed ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - LeadDev x O’Reilly Engineering Team Performance Report 2025. https://leaddev.com/reports/engineering-team-performance-report-2025 - SPACE framework (Microsoft Research). https://www.microsoft.com/en-us/research/publication/the-space-of-developer-productivity - DORA metrics overview (Google Cloud). https://cloud.google.com/devops/state-of-devops ## 📝 Summary - The panel reviews the 2025 report with O’Reilly. It stresses persistent difficulty. [Report link](https://leaddev.com/reports/engineering-team-performance-report-2025). - Leaders value qualitative context more. They still track delivery health with DORA. Yet they add outcomes. - Prompt engineering interest rises. ICs show less enthusiasm than managers. AI adoption varies by tenure. - Risks include metric absolutism, throughput worship, and context loss. Tradeoffs appear around speed and quality. - Bottom line: pair lightweight DORA with context, outcomes, and learning programs. Avoid lines-of-code metrics. ## 📖 Main Content - The report shows teams still struggle to pick metrics. The panel affirms the pain. They blame context gaps and tool churn. [LeadDev 2025](https://leaddev.com/reports/engineering-team-performance-report-2025). - DORA remains useful for delivery health. It misses product outcomes and team well-being. Leaders add business KPIs and qualitative checks. [DORA overview](https://cloud.google.com/devops/state-of-devops). - SPACE complements DORA. It frames satisfaction, performance, activity, communication, and efficiency. Teams must choose local measures. [SPACE](https://www.microsoft.com/en-us/research/publication/the-space-of-developer-productivity). - Throughput alone misleads. Teams should watch incidents, reverts, and churn. They should narrate anomalies with short notes. - L&D jumps in priority. AI pressure and hiring constraints drive the shift. Upskilling beats replacement narratives. ### 🗒️ Notes #### ⏱️ [00:00:16](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=16) Session framing - ### [H1] Team performance measurement remains difficult - Context: third annual report; complexity persists. #### ⏱️ [00:02:22](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=142) Panelist backgrounds - ### [H2] Veteran leaders report varied team dynamics - Broad experience informs metric nuance. #### ⏱️ [00:06:23](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=383) Metric selection - ### [H3] Many teams struggle to select metrics - The report highlights persistent selection pain. [LeadDev 2025](https://leaddev.com/reports/engineering-team-performance-report-2025). #### ⏱️ [00:08:25](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=505) Frameworks and skills - ### [H4] Prompt-engineering interest outpaces IC enthusiasm - Managers rate AI skills higher than ICs. #### ⏱️ [00:12:52](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=772) DORA sentiment - ### [H5] Perceived DORA effectiveness declines in 2025 - Maturity exposes gaps beyond delivery. #### ⏱️ [00:14:40](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=880) Qualitative balance - ### [H6] Qualitative context complements delivery metrics - Context turns numbers into decisions. #### ⏱️ [00:18:38](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1118) Framework churn - ### [H7] Framework churn risks metric misuse - Leaders must protect team signals. #### ⏱️ [00:20:28](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1228) Blending methods - ### [H8] Leaders blend qualitative and quantitative inputs - Start with a problem; then pick measures. #### ⏱️ [00:24:11](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1451) Local fit - ### [H9] Teams need context-specific measurement approaches - No single framework fits every team. #### ⏱️ [00:25:47](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1547) Throughput critique - ### [H10] Throughput alone misses post-release quality - Track incidents, reverts, and churn. #### ⏱️ [00:29:39](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1779) Narratives - ### [H11] Leaders must add narrative to metrics - Require owner notes for anomalies. #### ⏱️ [00:31:32](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=1892) L&D shift - ### [H12] Learning and development priority rises sharply - AI and hiring limits drive attention. [LeadDev 2025](https://leaddev.com/reports/engineering-team-performance-report-2025). #### ⏱️ [00:35:05](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2105) AI disruption - ### [H13] AI disruption forces rapid skill shifts - New skills appear; budgets tighten. #### ⏱️ [00:37:05](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2225) Hiring signal - ### [H14] Curiosity plus fundamentals beat tenure alone - AI-open seniors outperform skeptics. #### ⏱️ [00:40:45](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2445) AI usage - ### [H15] Engineers using AI gain efficiency, not replaced - Skills and reviews still matter. #### ⏱️ [00:42:40](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2560) Communication - ### [H16] Strong communication improves prompt outcomes - Clear prompts yield better code. #### ⏱️ [00:46:21](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=2781) Peer adoption - ### [H17] Peer support reduces AI adoption fear - Bottom-up momentum beats mandates. ## 📚 References - LeadDev: Engineering Team Performance Report 2025. https://leaddev.com/reports/engineering-team-performance-report-2025 - Microsoft Research: The SPACE of Developer Productivity. https://www.microsoft.com/en-us/research/publication/the-space-of-developer-productivity - Google Cloud: DORA and the State of DevOps reports. https://cloud.google.com/devops/state-of-devops - Video: Measuring team performance isn’t getting any easier. https://www.youtube.com/watch?v=L0ZTdw5flsw ## 🗣️ Paraphrase - The report shows measuring engineering remains hard. DORA helps, but leaders add outcomes and context. Teams avoid lines-of-code metrics and prefer qualitative checks. - AI changes skill demands. Managers prioritize prompt skills more than ICs. The panel recommends L&D, peer support, and balanced dashboards. ## 📰 Newsletter - Team performance still resists easy gauges. Pair DORA with outcomes and SPACE-style health. Prioritize coaching, not counting lines. See the LeadDev x O’Reilly 2025 report for patterns and pitfalls: https://leaddev.com/reports/engineering-team-performance-report-2025. WordPress folks: apply this in Core triage, performance bounties, and Training curricula. The WPOCC can trial micro-grants tied to qualitative health and post-release quality. ## ✅ Action Items #### DevRel - Publish a short “metrics that matter” guide with examples. - Record a 10-minute demo: anomaly notes in dashboards. - Add workshop content: prompt patterns and review checklists. - Launch a quarterly survey for team context and blockers. - Capture funnel from demos to adoption with clear UTM plans. #### OSPO - Ship a lightweight contribution policy for metrics disclosure. - Define a license-compliance training loop with sign-off cadence. - Document an embargo and incident-response playbook with contacts. - Track SBOM freshness and ownership using an SLO per repo. - Offer AI consult hours; publish guardrails and approved tools. - Formalize upstream funding with MoUs and operator agreements. - Align OKRs with exec KPIs; report quarterly deltas. #### Community - Host roadmap clinics for maintainers; share templates. - Run “first issue” pairing rotations monthly. - Publish budget and milestone reports for sponsors. - Schedule cross-project incident drills twice a year. #### WordPress - Core: define release criteria tied to MTTR and incidents. - Core Performance: add profiling labs and perf bounties. - Core AI: set review rules, eval sets, and pilot tasks. - **Core Program Team:** implement weekly cross-team standups with notes. - Mobile: review telemetry; improve offline UX backlogs. - Playground: create browser labs for repro and lessons. - Community: update meetup kits; add speaker mentorship tracks. - Training: map learning paths; prototype certification pilots. - Marketing: ship a narrative on outcomes-over-outputs. - Support: tighten SLAs; document escalation flows. - Design: run quarterly UX audits; adopt tokens. - Documentation: fill DevHub gaps; add examples-first patterns. - Photos/TV: improve captions and moderation guidelines. - Polyglots: run translation sprints; align glossaries. - Accessibility: prioritize WCAG audits with heatmaps. - Meta: stabilize .org APIs; improve contributor tools. - CLI: expand command coverage and smoke tests. - Hosting: publish cross-host defaults and reliability checks. - Tide: refine scoring transparency and false-positive reviews. - Openverse: tune ingestion; clarify moderation policy. - Themes/Plugins: mentor reviewers; add provenance checks. #### The WPOCC - Launch fellowships on governance and release leadership. - Fund micro-grants for documentation and health sprints. - Publish a transparent ledger of awards and outcomes. ### FAIR - Add signature checks and provenance to local metadata. - Publish funding covenants with sunset clauses and anti-capture terms. - Ship reusable charters and scorecards as living artifacts. ## 🧪 Hypotheses - Blending DORA with two outcome KPIs improves predictability. - Monthly qualitative health checks reduce incident counts. - Peer-led AI hours improve prompt quality and review time. - Curiosity-focused hiring improves cycle time within two quarters. - Anomaly narratives reduce leadership misinterpretation incidents. ### 📊 Methodology - Run a six-month A/B across teams. Treat one group with “DORA + outcomes + narratives.” Compare cycle time, incidents, and revert rates. - Log peer-led AI hours. Sample prompt quality and review duration pre/post. - Track hiring cohorts. Compare changes in lead time to prod. ### ❓ Questions - Where does DORA fail without context? - Which qualitative inputs predict incidents best? - How do AI adoption curves differ by tenure? ### 🔮 Future Research - Build open benchmarks for narrative quality in dashboards. - Standardize a minimal SPACE questionnaire for engineering teams. - Study prompt clarity’s impact on defect density. ### 💡 Implications - Practice: present metrics with narratives and context owners. - Policy: avoid lines-of-code incentives. - Security: tie MTTR to incident rehearsal drills. - Education: fund AI literacy and prompt communication. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ≈ 11 (panel transcript). #### 👀 Visual learners - Present: slides and dashboards. - Improve: architecture and data-flow diagrams with captions. #### 🔊 Aural learners - Present: recorded panel audio. - Improve: a 3-minute audio summary. #### 🗣️ Verbal learners - Present: definitions of DORA and SPACE. - Improve: term comparisons and glossaries. #### 🧩 Kinesthetic learners - Present: none. - Improve: hands-on labs with fake incident drills. #### 🧠 Logical learners - Present: metric trees and KPIs. - Improve: causal maps and error budgets. #### 🧑‍🤝‍🧑 Social learners - Present: Q&A and Slack follow-ups. - Improve: cohort guides and peer reviews. #### 🧘‍♀️ Solitary learners - Present: report PDFs. - Improve: reflection prompts and self-checks. #### 🌿 Naturalistic learners - Present: limited alignment. - Improve: sustainability and lifecycle notes. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: headings and captions. - Improve: consistent alt text and language attributes. #### Keyboard navigation - Present: basic focus order. - Improve: remove traps; add skip links. #### Contrast and readability - Present: adequate text contrast. - Improve: check large-text thresholds and line height. #### Text resizing and reflow - Present: responsive layouts. - Improve: support reduced motion; prevent clipping. #### Media and captions - Present: captions and transcript. - Improve: audio descriptions; downloadable transcript. #### Forms and interactions - Present: clear labels. - Improve: inline validation and forgiving inputs. #### Standards reference - Map gaps to WCAG 2.2 AA criteria. ### 🌍 DEIB Assessment #### Cultural breadth - Present: global applicability. - Improve: more non-US examples. #### Inclusive language - Present: neutral terms. - Improve: plain-language sidebars. #### Neurodiversity support - Present: consistent structure. - Improve: icon+text labels and predictable patterns. #### Representation - Present: varied roles on panel. - Improve: broader voices across regions. #### Psychological safety - Present: respectful framing. - Improve: clear escalation paths in communities. ### ✅ Logical Validity #### Strong reasoning - Causal link between context and decisions is solid [H6]. It aligns with SPACE. - Inductive claim that L&D rose due to AI pressure fits market signs [H12]. - Analogical critique of throughput vs quality is apt [H10]. #### Fallacies - Potential hasty generalization: “DORA effectiveness declines, so it fails” [H5]. Safer: “DORA helps, yet needs complements.” - Ambiguity risk: “AI replaces engineers” countered by clearer framing [H15]. Use: “Engineers using AI become faster.” #### Tone of voice - Pragmatic, candid, and evidence-seeking. Minimal hype; some caution on AI. ### 🛡️ DARVO Analysis - Deny: none apparent. - Attack: none apparent. - Reverse victim/offender: none observed. - The conversation stays constructive and professional. ## 🎯 Conclusion - Delivery health metrics still matter. Context and outcomes matter more. - Fund learning, pair AI-native and senior engineers, and narrate metrics. Then iterate. Share results with stakeholders. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Team performance measurement remains difficult > [!quote] [Measuring team performance isn’t getting any easier](https://www.youtube.com/watch?v=L0ZTdw5flsw) by [an unnamed author]] via [[YouTube]]. Published [MISSING]. Accessed . > “Measuring team performance never seems to get easier.” Two lines: use this to motivate a blended metrics approach. Cite LeadDev 2025 for context. [view highlight](https://www.youtube.com/watch?v=L0ZTdw5flsw&t=16) #xref #articleseed ID:rw_[MISSING] ### [H2] Many teams struggle to select metrics > [!quote] [Engineering Team Performance Report 2025](https://leaddev.com/reports/engineering-team-performance-report-2025) > “Selecting the right metrics remains a top pain point.” Use this to justify a minimal, outcomes-aware rubric. [view highlight](https://leaddev.com/reports/engineering-team-performance-report-2025) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Pair DORA with outcome KPIs - Works when teams align on two business goals. - Links: [[DORA]] [[SPACE]] #### [Z2] Require narratives for metric anomalies - Owners add short context notes per spike. - Links: [[Measurement]] [[Leadership]] #### [Z3] Track post-release quality, not just throughput - Use incidents, reverts, and churn as signals. - Links: [[Reliability]] [[Quality]] #### [Z4] Peer-led AI hours reduce adoption fear - Weekly sessions build skills and trust. - Links: [[AI-Practice]] [[L&D]] #### [Z5] Curiosity plus fundamentals outperforms tenure - Hiring signal for adaptive teams. - Links: [[Hiring]] [[Skill-Development]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft minimal “metrics + outcomes” rubric — /reports/engineering-team-performance-report-2025 #fleeting #inbox - [F2] Schedule peer-led AI hours — Mondays 11am #fleeting #inbox - [F3] Add anomaly-narrative requirement to dashboards #fleeting #inbox --- <!-- deep-read:sections end --> ## 📺 Video ![](https://www.youtube.com/watch?v=bMC1rlipclw) --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=bMC1rlipclw)* **[00:00]** Hi. Let's try this again. Good morning, everyone. I jumped on stream 15 minutes early because my timer was wrong. So, I did that. Oh, look. It's my face. Um, how is everyone doing this fine morning? I'm going to quit my stream timer. It caused me grief this morning. There we go. Um, yeah. So, to Oh, you can't see. You can't see. Where's my There it is. I got my word camp. Canada to gone. I got two **[00:30]** of them. And here we go. Word Camp Canada. Hey A, I did this the other part, too. Nice hat. Yeah, I got two hats, Troy. I stole one of the orange ones. Look at that. >> Oh, great. It's Troy Chiplin. >> Malcolm Peralti. Hello. How is it going? Uh, I see you there on Twitter. Um, we're over here on Twitch if you're interested in um in uh joining the chat. Otherwise, you're welcome to just hang out. It was great seeing you at um Word **[01:00]** Camp Canada. Troy and I Troy Malcol and I worked together at uh Tennup a million years ago, I believe. Um and it was good seeing him. I haven't seen him in a long time. So, um yeah, I got uh I stole I stole the orange one on the second day or something. I don't know what whatever it was. Whatever it was. So, today I don't have any code stuff to I mean, we can probably get into some code stuff, but I was uh I was thinking about just maybe doing a bit of a recap of working out in Canada. Uh how amazing it was, how much fun I had. Um and also I got a **[01:33]** new computer while I was away, so I think everything's working. Just tell me if things seem weird, if audio levels are off or if like you can't hear me or if I sound like a robot or I don't know. I don't know. All those things. All those things. Karolina, hello. Good to see you. >> Um, yeah. >> Oh, great. It's Caroline Aona. >> Yes, it is. **[02:04]** The amazingly talented Carolina. U, I got bad news about I'm sure we all know this now, but the icon block that I I I've been working on is not going to make it into 6.9. And it's a bummer, but it is a makes sense because um we have some dependencies that just don't exist for it right right now. There's a talk of an API for for icon registration which I think is very much needed because we have a number of blocks that use icons. We have the social icons block. We have the the there's another one too. I can't remember. It's one that **[02:35]** you're working on Troy with the monochrome stuff. Um, anyways, there. Yeah. So, there's that and there's also we're not have we don't have any block supports for width and height and those things need to be in place before we can get it done. So, I'm going to continue working on it as I bang the mic. I'm going to continue working on it and um we'll see if we can get it into 7.0. So, there's that. So, there's that. Um, right. Okay. Cool. So, Word Camp Canada, we um we were we were in Ottawa again. It was a great **[03:06]** time. Carlton U was a fantastic uh I thought it was a great venue. It was really easy to get to. I took the uh OC Transo, the train uh for my hotel every morning. It was nice, easy. Uh I had to change trains once, but it was super easy. Took me like 20 minutes. It was great. I actually ran into Constantine uh Overland from um uh also from Automatic, who I've never met, but he's the tallest person I think on the planet. Uh nicest guy in the world. We ran into each other on the uh on the train and I was wearing uh I was wearing **[03:38]** my vest that I have that says.org or on it that I got at a meetup team, like an automatic meetup and and he saw it and he was like automatic and I'm like automatic and he's like because I recognized him because how can you not, right? But uh so we we we were chatting and yeah, super nice guy. Really really really nice guy. Um and uh yeah, he's been around the WordPress world forever and I don't know I can't remember what what his title is automatic. I need to look it up again, but I think it's like super director of engineering. Yeah, I know. I So funny story about that. We **[04:10]** were um all the automaticians who were at Bord Camp Canada um were uh were gathering for a photo. So um I saw him go into one of the rooms and I said, "Oh, I I'll go grab him and come right back." So I I well he walked into a room of people and there wasn't that many people in there and I walked in and he disappeared. It was like there was no other exit. He just disappeared and he had he and he he did so by just sitting down when I walked in. I was literally like, "What? Where? Huh? Where?" Like, I'm like, "How how do I miss this? What? **[04:40]** What am I doing here? What is this?" Troy. Oh, yeah. That's the photo. There he is. And there's me looking like I don't have my eyes open. Brian, James, lovely booth staff who I don't remember all their names, but I met them. And this guy who we all know, Mr. Matt. This is a Tro G. Um, you gave um you you gave Matt this. If you can't see what this is, can I zoom in? Hold on. I can't zoom. Why is my keyboard not working? **[05:12]** There we go. Uh, it's Maple Syrup from Canada. We go. So, yeah. So, that that was the team photo. Look like I've never felt so short. My my son is 6'5, right? And I don't feel that this short beside beside him as I do beside Costa, but he's like the nicest guy in the world. A leader. A leader. A literacola. A a literacola. Please tell me somebody gets that reference. Far. **[05:44]** Come on. Liter. Yeah, he's 6'5. Yeah, he's tall. You see what? Yes. Thank you. Bad dude court. You get all the internet props today. Super troopers. Great movie. Fantastic movie. The Yes, they are. I I've heard the same thing and it's going to be great. The first one is so funny. The opening scene. So, if you're not familiar with Super Troopers, it's about like a highway patrol, right? I can't **[06:15]** remember where where they're based in the northern United States, I think. Or maybe they're in Canada and they're just right on the border. I can't remember. But it starts with them having a Vermont. That's it. Thank you. It's It starts with them having a maple syrup chugging contest at like a little diner. It is so funny. And it spawned the phrase, "I am all that is man." Okay, we have to find that. I am all that is man. Is there's got to **[06:46]** be a video of this. Here it is. We're going to pause the music just to hear this. Can you hear this? One, two, three. Do it. >> Oh, go girlfriend. I'm your mother. Come on, Thorny. You're losing to the rookie. It's embarrassing. Come on, Rabbit. You can do it. Oh, Rabbit. He's killing you. I got Thorny in front by a lot. What's the matter? Your mama didn't teach you how to chug. Come on, Thor. Come on, Thor. Oh, **[07:18]** >> I am all that is, man. Every time. finish it up. >> All right, that is a funny funny movie. The funniest line in that movie in my opinion. It's very not safe for work, but it is the guys get stuck. Long story short, they get locked in the back of a big like big rig trailer because the bad guys whatever. And so that the thorny comes and unlocks the back of the door and it's just the two guys in there and **[07:48]** he walks up. The first thing he says, he goes, "Smells like sex in here." It is the funniest line of all time and so wildly so wildly not safe for work. But oh, such a good movie. Such a good movie. If you haven't seen it, you need to go see it. Go and watch it. Find it. I don't know where it's streaming, but man, it's good. That is so good. Um, I don't know where that came from, but that was a amazing trip down memory lane. Anyways, back to Word Camp Canada. So, I want to give a shout out to Troy. I because he did an amazing job. He was **[08:19]** the speaker lead. He wrangled all of the craziness. There was a there was a speaker that we didn't think was going to make it because of like visa issues and so he just just like deafly just just got in there and rearranged the schedule and made it all work and then yeah, it was great. So I think everything went off without a hitch. There was some internet issues at the beginning which is always internet issues at every word camp and uh the team handled it like rock stars. It was amazing. Anyways, I can't say enough good things. Uh venue was awesome. Food was great. It was really good. The afterparty was so much fun except for **[08:50]** the Blue Jays losing, but that's okay because now they're going to the World Series. Go Jays. Go Jays. We are a Jay's positive stream here. Um uh anyways, um I wanted to point out a couple of things. What did I want to point out? Okay. Um so I did I I I did two talks there. Uh the first was um was well I did a a full session on um the Blockber cookbook which was so much fun. Uh it was it was very condensed. **[09:20]** It's baseball carolina. Sorry. It's sports ball as as I like to call it. I don't usually watch baseball. I don't usually really follow sports. I enjoy I played hockey my whole life because I'm Canadian. It's sort of like that's what you have to do. Um or they kick you out. Uh but uh yeah, I just enjoy it. But because the Jays are doing so well, they haven't been to the World Series since 1992 and 93 where they won backto back World Series. And they haven't been back since. And they're going back to to the World Series. So hopefully we're going to do it. Anyway, **[09:51]** um I forget what I saying now. What was I saying? All right. The um soccer and football. Wow. Hockey, soccer, and football. So Caroline, when you say hockey, you're talking ice hockey or field hockey because what my my good friend Jonathan Boston who's on my team, his son plays hockey, but they call it but it's field hockey in South Africa, not um not ice hockey. So just want to clarify and I should say I play I played ice hockey my whole life. I think kind of goes without saying I'm Canadian. **[10:22]** Um right, so ice hockey, we have bandandy ice hockey. We have band Oh, is that what you call field hockey? Bandy. What? Oh. Oh, I never heard of this. Bandandy is the most insane variation of ice hockey you'll ever see. Oh, I don't **[10:54]** want to go there. Interesting. So, it's sort of like it's Okay. Bandies in winter sport and ball sport played on two by two teams wearing ice skates on a large ice surface while using sticks to direct balls. Oh wow. Okay. So it's like so they're so they're they're wearing hockey equip. That is a gigantic ice surface though. Oh, I've never heard of this. This is so cool. Yeah. Like how big is the ice surface though? It was **[11:26]** introducing to Canada in the Winnipeg in 1986. Uh the goalie has no stick. What? Played on ice with a small bat sticks. That's crazy. Okay. So, so because that looks I I don't think Okay. I don't know if you can see that, but that looks like an absolutely massive ice surface. Like **[11:59]** like NHL like ice hockey rings are not that big. That's crazy. I've never heard of this. I I'm gonna have to check it out. That looks so cool. H. All right. Oh, here we go. The first bandee that Oh, wow. Oh my god. That looks like a comical version of like the hockey net. That's crazy. Look at the size of that net. It's like a soccer net or football. I think it's bigger than than Olympic size. Look at that. **[12:30]** That's insane. How many players How many players do they have for that? The goalie has just these these these gloves. Yeah. Wow. Okay. Okay. So, there's one, two, three, four, five, six, seven, eight, nine. There's what is that? 10 players plus a goalie. Does that make sense? Wow. Okay, cool. So, in ice hockey, you you play five on five and with and then a goalie. Uh, but it Yeah. So, it's like soccer on ice. **[13:01]** This is crazy cool. Did is there like What is this? Is there body contact? Oh, here we go. Penley area. So, this looks very much like 16 meters. That's craziness. Is there Is there body contact? Like you allowed to like in hockey you're allowed to kill each other. Um Wow. That is so crazy how big that is. Wow. **[13:33]** Well, we learned something today. We learned something. Let's see. The playing service called the Bandy Field or Bandy Rake is a sheet of ice which measures 300 to 360 feet by 148 to 213 feet. Size of a football pitch like a So yes, soccer. Whoa. The rules. What are the rules? 11 players. Each team consists of maximum of 11 players. One of whom must **[14:05]** be the goal. Okay. So they have Okay. duration. Okay. So, is there like penalty warnings and penalties? Oh my god. So, they have like cards to save us uh soccer ball, banny stick, bandy field, protective equipment. Wow, that's really neat. Wow. We went down a rabbit hole, but that was totally worth it. That's so cool. I've literally ne never heard of this. That's so cool. Um, so anyways, Bandandy. Um, I forget what I was doing. **[14:35]** Oh, right. I did a a talk Uh, so they the or the organizing team working pan had an amazing idea to do like a like a workshop track on contributor day. I thought that was a really really great idea. I've been to a lot of contributor bid days over the past few years and um people that know how they just go and they do and then there's a lot of new new like new folks that are just like maybe unsure and they kind of get lost either like in the setup phase or they um you know once they're they're set up they're not really sure where to go who **[15:06]** to talk to and stuff. And so having that alternate track of content for folks that um that maybe you know want to be part of it but but don't know where to start or maybe get frustrated and want to want to change gears. So like there was this really like Ashanta did some really great stuff on like intro to WordPress and Jonathan actually talked about like h how to contribute. So like these are sort of talks and and workshops, right? And I I I think that it was a great idea. So I I I did this half day thing on custom block **[15:36]** development. I'm super proud of the title. First one was called Ain't Nobody Got Time for That, which is the idea is you're you're busy developers. The other name for this is like a custom block development for busy developers. And then the second part is custom blocks. Here's some time for that. I was so proud of that. So proud of that concept. Uh but anyways, um so I'm going to share my slides here if you all want to see them. Uh where's the link? Copy the link. These are the slides. So the idea and and they're public. you can have a **[16:06]** go at it and there's a repository as well uh in here which is the accompanying repository for it. So if you want to take a look at this you can whatever but basically the idea is like there's a there's a bunch of stuff that we could talk about various things and then like there's like these moments where it's like okay just trust me you don't need to know anymore and we're going to move on. So I'm not going to go through all this stuff. So it goes from like there's command there's the sorry the create block package and we get into all the files and reg how what blocks you register and how block JSON works. **[16:37]** Um what else? What have we got here? And there's these little mini assignments which is kind of fun. U I thought this went really well. I completely o overprepared content so I ran out of time at the first section and then we just ended up doing this over over the the the two sections. But the attendees seem to want they were into that. So it's good. It was fun. [Music]