أنجزة العمل أخري في قبل سنوات mead i've been doing this job for six to seven years and it's something creative something that is my art something I'm doing when I'm tailoring when I'm making clothes and somebody wears that somebody wears that and they feel happy and I feel proud I feel satisfied that I made somebody happy so I really like it because I'm helping another human being I know that someone is elderly كنت أردت المساعدة في المساعدة في المساعدة وقد أستطيع أن أستطيع المساعدة في المساعدة وقد أستطيع المساعدة في المساعدة وقد أستطيع المساعدة في المساعدة The Sewing Program here at Curtin has been going for over a year It's very important for the clients to continue the skills that they've learned in the past We've done projects in town at the Nungah Women's Centre where we produced clothing for them and from May this year we started a project with the nursing home in town whereby clients have been designing and making pillows doing the covers and curtains The Department of Immigration approached us saying that they've got guys from the detention centre who are happy to offer their services freely They had different professions and quite a few of them were tailors and they are very skillful and very professional and very neat, very neat here We appreciate their services The activities are very important here at the centre in terms of keeping clients busy and keeping them active The good thing about the Sewing Program is that it allows the clients to connect with the Derby Community and the advantage of that is that they get to meet people in the community make new friends and learn a little bit about Australia I think it's very important because it sort of gives the residents that are out at Curtin an idea of what Derby is like and Derby residents get to see that those people are really nice and able to work with them


What happens is a lot of times when we buy from the manufacturer, the manufacturer themselves will have in here escalation clauses. So manufacturer will say, will give you a price increase after a certain period of time. But if you signed a contract six months ago or five months ago, you may not be able to pass that cost off to the prime contractor or the government for that reason. So this is an example where I received a notice of a price increase from my manufacturer, okay, and it says that the project extended past the material protection date, which it did. However, in my contract, it says there is no material protection date or material cost protections afforded under my subcontract agreement. So my cost went up $40,000 on this particular project. And because I did not have any clauses for material cost protections and my subcontract agreement, guess what I had to do? Eat it.


وأقول في القرآن ما جاءت به آياته فهو الكاريم المنزال وقال الله جل جلاله والمصطف الهدي ولا أتأواله الحمد لله رب العالمين له الحمد الحسن والثناء الجميل وشد الله إلا الله وحده لا شريك له يقول الحق وهو يهدي السبيل وشد أن سيدنا ونبينا محمد صلى الله عليه وعلى آله واصحابه والتابعين لهم بإحسان إلى يوم الدين أمما بعد I beloved brothers and sisters who are listening to me إن شاء الله تعالى I want to share this important message with each and every one of you this message is about the concept of to have fanaticism for a particular individual to the extent that if this individual says to you that this is where you could go you go and if they say to you you can't go here you don't go and this حقيقة it goes against the methodology and the way of أهل السنة والجمع ولذلك الشيخ الإسلام ابن تيمي رحمه الله he mentions in his مجموع الفتاة he says وليس للمعلمين أن يحزب الناسة it is not befitting it is not permissible it is not allowed for the teachers أن يحزب الناسة that they divide the people and they break them into groups ويفعل ما يلقي بينهم العداوة والبغضاء and they place them in the hearts of the people حيث and enmity so the teacher will say to his student for instance don't go to that particular teacher and the reason why he would say that is because he has a personal issue with that teacher he doesn't personally like that teacher so he forces his students and those who take knowledge from him not to go to that particular person because of the grudge and because of the personal inclination that he has he bans his students from going to benefit from that person and this sheikh of islam ibn taimi he says it is not correct وليس للمعلمين أن يحزب الناسة it is not right for the teacher to do this and nor should he go that direction and then ibn taimi when i'm carrying on to say بل يكونون مثل الإخوة المتعاوينين على البر والتقوى كما قال تعالى وتعاونوا على البر والتقوى ولا تعاونوا على الإثم والعدوان إن الله شديد العقاب الله سبحانه وتعالى he said ايد one another in good and righteousness and piety don't aid one another in الإثم والعدوان don't aid one another in that which is sinful and that which goes against obedience and righteousness dividing the students and dividing the people is التعاونوا على الإثم والعدوان and then Allah says be conscious of Allah and fahm him or teachers إن الله شديد العقاب الله تبارك وتعالى his punishment are very severe i want to mention a story here إن شاء الله وتعالى this story is regarding a great scholar a scholar that lived in this time that we were living he is none other than المحدث محمد ناصر الدينة الالباني الشيخ محمد ناصر الدينة الالباني two people came to him one day and they had a conflict and these two people who came to him both of them were مشايخ people of knowledge the first one is الشيخ محمد ناصر الرفاع and the second one is محمد ناصر الترمانيني رحمهم الله may Allah have mercy upon each and every one of them الشيخ محمد ناصر الرفاع and محمد ناصر الترمانيني when they both came to him الشيخ الالباني رحمه الله he listened to the khilaf the dispute that was present between the two sheikhs الشيخ الالباني was listening he listened to the khilaf the dispute between الشيخ محمد ناصر الرفاع and الشيخ محمد ناصر الترمانيني he listened and الشيخ الالباني after listening he came to the conclusion that the truth is on the side of الشيخ محمد ناصر الترمانيني that the truth is with him and that الشيخ محمد ناصر الرفاع is in the wrong when sheikh الالباني spoke to الشيخ محمد ناصر الرفاع to tell him that he is wrong and that his position in this issue is to come back and to ask forgiveness from his brother الشيخ محمد ناصر الرفاعي was refused and when he refused الشيخ الالباني became angry with الشيخ محمد ناصر الرفاعي and sheikh الالباني took the side of الشيخ محمد ناصر الترمانيني and sheikh الالباني boycotted الشيخ محمد ناصر الرفاعي الشيخ الالباني boycotted him keeping in mind that sheikh محمد ناصر الرفاعي is a man of knowledge and they say that he was the the one who established جمعية الدعوة السلفية so الشيخ الالباني what he did was when he realized that الشيخ محمد ناصر الرفاعي does not want to take the truth and he does not want to follow the truth الشيخ الالباني boycotted him but the moral of the story is this this is the moral of the story and that is الشيخ محمد ناصر الرفاعي when الالباني boycotted him he didn't tell his students to do that and he did not force his students to follow him in this view rather his students they would go to الشيخ محمد ناصر الرفاعي and they would take knowledge from him and they would benefit from him and they would converse with him and they would even have dialogues regarding their affairs الشيخ ناصر الالباني never forced his students to follow him in his view and this teaches us something that the scholars were never ones to do to حزيب الناس to divide the people and to teach the students to be fanatic towards them and to have fanaticism towards them they were far from that they believed that the people if they're going to stick to something and if they're going to hold on to something it has to be the كتاب and the سنة and also بما عليه سلف الصالح that which the pious predecessors were upon so let that be إن شاء الله تعالى something that we that we implement in our lives as teachers especially and also if you have a group of people who listen to you don't be a person who تحزيب الناس divides the people because of your person who issues with a particular person anything which I have said that was wrong but incorrect is from me and Shaytan and Allah his messenger are free from it سبحانك اللهم بحمدك أشدو ألا إله إلا الله أستغفرك وأتوب إلي


Okay, hello everyone. This is the Circuit Python Weekly meeting for Monday, August 22nd, 2022, so 822-2022. This is the time of the week where we get together to talk about all things Circuit Python. I'm Dan and I'm sponsored by Adafruit to work on Circuit Python. Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit, so if you want to support them and Circuit Python, consider purchasing hardware from Adafruit.com. We host this meeting on the Adafruit Discord server. You can join anytime by going to adafru.it slash discord. We hold the meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. Typically, this meeting happens on Mondays at 2 p.m. U.S. Eastern Time, 11 a.m. Pacific Time except when it coincides with U.S. Holiday. In the Note Stock, there's a link to a calendar you can view online or add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. If you would like to receive these notifications, ask us to add you to the Circuit Python East as Discord Role. As I mentioned, there's a Note Stock to accompany the meeting and recording. The Note Stock is posted in... It's a few posts up in the Circuit Python Dev Channel right now, and you can also find it in the pinned messages in the Circuit Python Dev Channel. The Note Stock, it contains timestamps to go along with the video, so you use the doc to view only the parts of the video that interest you most. The meeting tends to run 45 to 60 minutes, so it gives you the option to skip around. After each meeting, we'll post a link for the next meeting's notes, documents, the Circuit Python Dev Channel on the other Discord, and pin that to the channel. If you wish to participate but cannot attend, feel free to leave hug reports and status updates in the document for us to read out loud during the meeting. Meeting is held in five parts. The first part is community news, where we look at all things Circuit Python and Python on hardware. The second part is the state of Circuit Python libraries in Blinka. This is a statistical overview of the entire project. It's a chance to look at the project by the numbers separate from what we're all up to. The third part is hug reports, which is an opportunity to highlight the good things folks are doing, taking the time to recognize the awesome folks in our community. The fourth part is status updates. Status updates is an opportunity to sync up on what we've been up to. You can take a couple of minutes and talk about what you've been doing in the last week since the last meeting, and what you'll be up to over the next week until the next meeting. And finally, the fifth part is in the weeds, which is an opportunity for more long form discussions. These discussions can come out of something reported in the status updates or be something you've identified ahead of time as too long to discuss in status updates. So with that, I'll do community news right now. And let me put it in a timestamp, scroll up to here and press the button. There we go. OK. So these these news items are from the upcoming CircuitPython or Python and microcontrollers newsletter that's coming out tomorrow. Thank you, Ann. OK, first thing is that CircuitPython 800 beta zero has been released. It is a relatively stable release, but there will be further additions and fixes before final release. Usually we wait when we do a beta to say that the APIs are not going to change and the feature list hasn't changed. There'll probably be a few changes, but not very many before final release because we've got a while before final release. But we want to make it clear that it's sort of past the alpha stage right now. There's a whole bunch of interesting things in the beta release. The last alpha, the previous 801 release was the alpha release and it was over two months ago. So since then, things have come in like the Wi-Fi workflow is really quite functional now. There's a status bar that shows up on your terminal window or on the display, on board display, on the sort of Python board.  Let's look at the release notes. There's a link in the note stock to those. Okay, next item, timestamp. Circuit Python Day was a success. Great success. That was last Friday. It was August 19th. In typical fashion, it did not disappoint with many of video streams with the community and folks showing their projects thanks to all who participated. There's a playlist on the Adafruit YouTube site of all the streams that we sponsored. There's a link to that playlist in the notes. There was a Circuit Python Day introduction and then there was a panel discussion run by Paul Cutler. With a number of us, then there was a development sprint, video intro. Maker Melissa did a project build on video. There was a longer form show and tell, which was great. Scott did a Circuit Python 8 preview of the upcoming features, including Wi-Fi workflow and the status bar that I mentioned. Then Catney, Jeff, and I had a chat about projects that we're working on and interesting things that we've been working on. And finally, FOMI guy did a Circuit Python Day game jam stream, which is hard to say fast, 10 times. And also, the Blues Wireless Company did a YouTube on reimagining IoT deployments with Circuit Python. So check out all those links, which you can find in the notes doc. Okay. Next thing of note is that recently, not in beta 0, it's been, I think it was after that, I believe, I'm not sure. Circuit Python added RP2040 I2C target support. It used to be called I2C peripheral. But basically, it can act as an I2C device rather than a controller of an I2C device. So that means it's useful for communicating between, say, two RP20s, 2040s. One would be the controller and the other would be the target. And there's a link to the pull request for that. Next up, in regular Python news, Python 3.11.0 RC1 is now available. That's the first release candidate of Python 3.11. It's the penultimate release review, entering the release candidate phase, where only reviewed code changes, which are clear bug fixes are allowed. Second candidate in the last plan, release preview is currently planned for Monday, September 5th, while the official release is planned for Monday, October 3rd. So 3.11, it doesn't seem that long ago that 3.10 came out. So this is very interesting. From my point of view, one of the most interesting things in Python 3.11 is that it supports something called task groups in async.io, which makes using async.io a lot easier. And we hope to put task groups into Circuit Python. Eventually, MicroPython is also looking for that. And we'd probably just take their implementation. Another really interesting thing about Python 3.11 is that the performance has been improved a lot in various ways. And so it's worth checking out for that reason. So where did us all this news come from? It came from the Circuit Python Weekly Newsletter, which is emailed every Tuesday. The archives are at a link available in the note stock. The newsletter highlights the latest Python or hardware-related news from around the web, including Circuit Python, Python, and MicroPython developments. We'd love to have your contributions to the Weekly Newsletter. You can contribute by emailing cpnews at Adafruit.com. You can tag a tweet on Twitter with hashtag Circuit Python, or you can submit a portal request to the newsletter. And the link to the GitHub repo for that is in the note stock. So feel free to contribute. We'd really love to have news and pictures and all kinds of stuff. And more of the merrier. OK, so now we'll move on to the state of Circuit Python libraries in Blinka. Overall, in the past week, there were 33 pull requests merged, 23 authors, some new ones that I haven't seen before, new authors are Socrates, O. Kennedy, Colin W. Q., R. Balsen 1, maybe VM 0824, Vladik. Probably some of these people have contributed before, G. Belland. Thank you very much. There were nine reviewers of these 33 pull requests. And overall, in the whole project, there were 24 closed issues by 14 people and 23 opened by 16 people. So as usual, the number of open issues and closed issues tends to stay about the same. OK. So next up is core. Since I'm running the meeting, Jeff, would you like to read about the core? Is that OK? Hello, sure. Let me just get back to the correct part of the document. So in the core, we had 17 pull requests merged from 12 authors. May R. Homar is a name I don't recognize. So thank you to you and any other people who are new or infrequent contributors to Circuit Python. And thanks also to our five reviewers. Reviewers are what makes the world go around and lets us merge in high-quality changes to Circuit Python. And Ketney will talk more about what reviewers do when she talks about the libraries. Anyway, in terms of pull requests, we've got 16 open pull requests, some of them up to 194 days old, and the newest is three days old. I know some of those older ones are in draft condition or waiting for response to a review request. So if that applies to one of your PRs, please let us know when you are able to work on that, push some new work, or if it won't work out, then please just feel free to say that as well. Sometimes it doesn't. But our goal is to help get your pull requests merged. So also ping us if you're waiting for action from somebody kind of on the Adafruit core developer side. Issues-wise, we had 12 closed issues by seven people and nine open by seven people. So we are net down a couple of issues. That's always nice to see. That leaves us 551 open issues. However, we usually categorize things by milestones. And the important milestone that we're looking at right now is 800, which has 34 open issues. We are probably going to look at that list soon and move some of them to an 80X list. Those are issues that wouldn't stop 800 from being released, but we still think are important to address as bug fixes, fixing regressions, or hardware support for some of these new microcontrollers that we're adding in 80. Also, there are 491 long-term issues, and that means that Adafruit doesn't prioritize working on them, but we are more than happy to see you pick up and work on any of them that are of interest to you. And Discord is a great place to ask questions about how to get started working on one of those issues. And as Dan already touched on, we released the first beta for version eight, and that is kind of continuing towards completion. And we just need to chip away at those 34 open issues either by resolving them or by deciding that we can move them to a later milestone. And that's what's going on in the core. Thank you. Okay, thank you, Jeff. Okay, next up is libraries, and Kat and you can tell us about all about the libraries. Thanks, Dan. This section applies to all of the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscore circuitpython underscore. We had 15 pull requests merged by 11 authors, number of those names I don't recognize. Most of them Dan called out earlier, and seven reviewers. We merged a few pull requests that were a month old and one that was just under two weeks old. So I'm really glad to see that we're still getting to older issues. And we currently have 31 open pull requests, which that number is up, but I believe we had a number of folks submitting PRs last week. So that's not surprising. We had nine closed issues by five people and 10 open by six people, leaving us with 669 open issues. 173 of those are good first issues. If you're interested in contributing to Circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all this information and more, including open pull requests, which if you're interested in reviewing, that's a great place to start. Take a look at the code. If you have the hardware, test it. If you don't, leave a comment that you looked at it. Let us know what you saw, is there an issue? If there's not, let us know that. All of that is very helpful. And once you're comfortable with that, we can talk about leveling you up to the review team. And if you're interested in contributing documentation or code, check out the list of open issues. They're divided up by repository, and you can search by label. And if you're new to everything, good first issue is a great place to start. We have a guide on contributing to Circuit Python using Git and GitHub, and we're always available on Discord to help you out. So don't let the process intimidate you. We wanna make sure that you can help out in a way that works for you. There's also bug or enhancement in terms of more difficult issues to fix up. And so depending on your level, we should have something that works for you. In terms of library updates in the last seven days, we had no new libraries, but a number of updated libraries that I will not read off. The list is in the notes if you're interested. And that's what I've got. Okay, thank you very much, Katnie. Okay, next up is Blinka, and Micro Melissa will talk about it. Hello, so Blinka is our Circuit Python compatibility layer for Micro Python, Raspberry Pi, and other single board computers. And this week we had one poll request merged by one author and myself as the reviewer. And we have currently four open poll requests still. There were three closed issues by three people and four open by three people, leaving a net of 81 open issues. There were 11,608 pie wheels downloads in the last month. We are currently at 89 supported boards. And that's it. Okay, thank you very much, Melissa. Okay, next up is Hug Reports, which is a chance to highlight folks in the Circuit Python community and beyond for doing awesome things. I'll start as meeting host, then we'll go down the list alphabetically. If you're text only or missing the meeting, but you have a hug report, I'll just read it off as I get to it. So feel free to contribute to this even if you can't attend the meeting or you can't speak during the meeting. Okay, so I'll give a time stamp for myself. First of all, thanks, Catney, to Organite for organizing Circuit Python Day last week. It was fantastic and ran really smoothly and had just jam packed. I think it was our most eventful one in terms of number of events, which was great. Thanks to Paul Cutler for running the panel that several of us were on and interviewing us. We had some pre-discussions before that and it worked out really well. Thanks to Catney and Jeff for joining me on the stream chat that we had. And especially Catney gave a detailed overview of a mailbox monitoring project. And this is a mailbox, a physical mailbox, a USM mailbox and it was a very interesting project and it was a really practical project and it's interesting how many pieces there are to such a, that kind of project. Thanks to all the people who streamed on Circuit Python Day and everyone who attended the live streams or watched the streams later. Thanks to now leaving Circuit Python, thanks. Thanks to Scott for fixing a ton of issues just before his parental leave, which starts today. He'll be gone for about 12 weeks and so we've got to take up the slack in his stead but he fixed a whole bunch of things and left us in a really good place for an eight hour release. Thanks to Dave Putz who quickly diagnosed and fixed a rotary IOSU that somebody posted just a few days ago. Thanks to Maker Melissa for adding at light speed all the new boards that were added in the 800 beta zero release, that was fantastic and it makes Circuit Python work up to date. Oh Maker Melissa says she added some new boards but there are a lot of boards, I think there were like 15 boards or something. So thank you for continuing to work on that. And in my own life it's just I started being paid to work on Circuit Python five years ago this month by Adafruit. Thank you so much Adafruit for contracting with me for five years. It's very fantastically fun. It's a really gratifying work. It's like kind of the best job I've ever had and it's a huge pleasure to work with and get feedback from the community. That's one of the most gratifying things about it. Okay, next up is Blitz City DIY Liz who isn't at the meeting. So I'll read her notes. Thanks to Katnie for organizing Circuit Python Day. A group hug to everyone who came on the Good Circuit Python Day show and tell. And thanks to Melissa for lead hosting the regular show and tell for the first time last week and hosting her own solo live stream on Circuit Python Day. So thank you very much. Okay, next up is C Grover. And I'll read their contribution as well. Thanks to the team for organizing and conducting Circuit Python Day. The special show and tell was amazing as well. Thanks to John Park for adding practical build content with wonderful photos to a recent learning guide project. Hugs to Anne B for assisting with the guides publishing logistics. Thanks to FOMI Guy for educational inspirational live coding streams. Not only does FOMI Guy introduce and explain Python programming solutions, the high level thought process and structure examples are greatly influencing my design decisions and approach. And thanks to Dan H on his Adafruit Anniversary.  Thank you very much. Okay, next up is David Clouder who also is not speaking but is in the meeting. Thanks to Dan H for the release of 800 beta zero. Thanks to Jeff and Scott for sharing on the tiny USB versus Circuit Python and board with or without UF2 boot loader. I guess that's for sharing an explanation. Thanks to Neeradoc for explaining Creator ID versus USB Vid and PID for ES32 boards. Thanks to John Park for an oddly specific stream on LCDs. That's a new product that Adafruit is stocking. Oddly specific is the maker of that. And they're very interesting LCD boards. Thanks to Todd Gott for suggesting ES Play Micro V2 as an alternative to the impossible to find Odroid Go. And thanks to all the architects, organizers, and participants of or to the CP Circuit Python Day. Okay, thank you, David. Okay, next up is FOMI Guy. All right, thanks, Dan. Echoing what a few folks have mentioned, hug report for Catney for planning and organizing Circuit Python Day. Definitely had a great day and echo again what Dan said. It went really smoothly. And so really appreciate all the work that went into it. Everyone who participated in or watched along with any of the streams on Circuit Python Day, there was lots of great content and lots of great folks popping up in the chat and even just watching along. So thank you to everybody who did. Thank you to GitHub user TC Franks who has been submitting a bunch of PRs lately, lots of typing information and other improvements to libraries. So thank you to them. A report for TechTrick for doing the introduction video and working on Sprints on Circuit Python Day as well as the rest of the folks who participated that I didn't list. I definitely appreciate everyone who helped out in the chat and anybody who did make a contribution. Thank you to, let's see, Bab Lock B for submitting some improvements to the Sparkline graph inside the display shapes library. Thank you to Retired Wizard for jumping in and helping on the hack tablet, helping troubleshoot some of the issues we're seeing there. And then a group hug for anybody who I missed because I'm sure I have missed somebody with all the great stuff going on lately. Thanks. All right, thank you for me guys. Okay, next up is Jeff. All right, hello again. I wanna thank Ketney for organizing a marvelous day by which of course I mean Circuit Python Day and Paul Cutler for hosting our panel session. And Paul put a lot of thought into that beforehand and I think it really showed in how things flowed and how it worked. And I wanna thank everybody else who participated in Circuit Python Day in one way or another. There were a lot of people doing the streams, there were a lot of thoughtful questions and discussion in the Discord chat and it was a lot of fun to see all that go by. And just to cheat a little bit, I wanna thank everybody that Ketney is about to thank as well. Okay, thank you, Jeff, by forward reference. Okay, okay, next up is Ketney. All right, so overall thank you to everyone who participated in Circuit Python Day 2022. More specifically, thanks to Liz for hosting a special edition show in Tel. I watched along the whole time and it was excellent. To hub from Melissa for her first ever live stream, it went amazingly well. There were multiple comments about was this really your first live stream? I don't believe it, so good job there. To Paul Cutler for introducing the whole day. When the panel discussion that was also hosted by Paul ended up being the first event, I thought why don't I have Paul also introduce Circuit Python Day overall? So I asked him to do that and freaked him out a little bit, but he offered, when I offered to brainstorm through it with him, he was like, all right, yeah, let's do this. So thank you for doing that. It was one less thing on my plate and it's kind of like perfect for a community member to be introducing Circuit Python Day since that's kind of what the whole thing is wrapped around. And also Paul for hosting a panel discussion. To Jeff, Dan, and Tim for participating in the panel discussion with me outside of Circuit Python Day to Dan for five years at Adafruit, back to Circuit Python Day. Scott for the Circuit Python 8 preview and demos. To Jeff and Dan for joining me for a wonderful Circuit Python Day chat. To Tim for hosting the Game Jam stream. To Tectric for coordinating and hosting the Circuit Python Day development sprint. Group hug to the folks who volunteered to help out with the development sprint and group hug to those who contributed during the development sprint. To Ann for keeping up with the socials, blogging the events and getting all of the day's videos into one playlist on YouTube. To Phil for support while I was planning Circuit Python Day. To Mr. Certainly for moderating multiple chat streams throughout the day and aggregating questions from YouTube and Twitch into Discord so that the streamers could monitor a single chat while live streaming versus needing to keep track of everything. To Mark Gambler for providing two as seen on show and tell feather badges to give away. To Kmatch for providing the hack tablets to give away around, for me guys, Game Jam stream. To Adafruit's graphics creator Bruce for the Circuit Python Day 2022 graphic and creating a separate graphic for my chat with Jeff and Dan. In terms of a project I did, thanks to Carter for sending me two Pi Zero Ws a while back, making the mailbox demo that I did on the chat stream possible. To Rose for helping me get the right demo code going on the mailbox demo at almost the last minute. And to Jeff for helping me explain the parts of my demo that I didn't quite entirely understand. There's parts of the code that are a little outside my wheelhouse and that was greatly appreciated. A group hug to the community for watching the Circuit Python Day live streams and making Circuit Python what it is. And apologies to anyone that I may have missed. Thank you all. All right, thank you, Katnie, for that comprehensive overview. That was great. Next up is K-Match who isn't here, so I'll read their contribution. Thanks to everyone who made a great Circuit Python Day and thanks to Mike Mabee and Jerry Diedel for the Ultrasonic Sensor Library, which is the HCSR04, including a few key comments. Okay, next up is Melissa. Hello, I wanted to first give a hug to Katnie for organizing Circuit Python Day. It went wonderfully. And again, to Katnie for encouraging me to do a live stream on Circuit Python Day. It went better than I expected. I hugged to everybody who watched my live stream and gave me encouraging feedback. To Liz for co-hosting Show and Tell with me again and also for her special Circuit Python Day show and tell. To Katnie, Jepler, Fomey Guy and Dan for the discussion panel. To Scott for the Circuit Python 8 review stream. To Paul for your participation in Circuit Python Day and a bunch of different areas. And everyone who participated in Circuit Python Day, including those just watching that I hadn't mentioned. And to David Glada and Bill88T for adding boards to CircuitPython.org. And a group hug to anyone else. And that's it. Thank you, Melissa. Next I have several text-only entries. First up is Mark Gambler. Thanks to Katnie for organizing Circuit Python Day and everyone who participated. Thanks to Lee for continuing to work on his ADC buffer poll request and taking the time to learn about all the little gotchas for a core contribution. Yes, very much so. Thank you. Next up is Paul Cutler, who's text-only. Thanks to Katnie for all her work organizing Circuit Python Day. Thanks to Katnie, Jeff, Dan and Tim for being part of the panel discussion. And thanks to everyone who contributed to Circuit Python Day. Thanks to Brent Rubel for being a guest on today's podcast episode and a group hug. And next up is Tammy Makes Things. Hi, everybody. So I have hugs for Mark Gambler, Keith, the EE, Deshipu and Tech Trick for organizing slash participating in the Circuit Python Dev Sprint. Hugs for everyone who organized and participated in Circuit Python Day and a group hug. Okay, thank you. Next is Tech Trick, who's also text-only. Thanks to Katnie for organizing all the logistics for Circuit Python Day. Thanks to Tammy Makes Things, Keith, the EE, Deshipu, Mark Gambler and others who volunteered to help with the Circuit Python Day mini development sprint. Thanks to Dexter and other authors that contributed PRs during said sprint. Thanks to everyone who held the panel, participated in the panel, shared a project or otherwise chimed in during Circuit Python Day. Definitely a great day all around. Thanks to TC Franks for all the awesome type annotation PRs they are submitting. Thanks to Lady Aida for being the guinea pig for the Pi project that Tamil updates to the cookie cutter. And finally, a group hug. Okay. So that concludes our reports and we'll move on to status updates right now. Status updates is a time to sync up on what we're doing. I'll start and go through the list alphabetically as before you can take a couple of minutes to talk about what you've been doing since the last meeting or what we'll be doing in the next meeting. It does not necessarily have to do with Circuit Python but it usually does. Okay. All right, let's go ahead and I'll start first here. I released Circuit Python 808-0 which had over two months of changes, something like 146 pull requests, something like that. So there's quite a lot of stuff in there including Wi-Fi workflow as I mentioned. And I'm continuing to fix issues for 808-0 final which is a ways off but we're making very good progress on that. Okay. Next up is C Grover who's not attending today. Inspired by FOMI guys, state machine coding approach. I spent the week refactoring an old but favorite Eurorack hysteresis-based quantizer module called Range Slicer. Also upgraded it from Circuit Python 5.3 to 7.3. Code is easier to read and module performance was improved by 40%. When the module refactoring is completed it'll be adjusted to power two new rack modules that use the same custom PCB board as Range Slicer. Hope to have ZY Comp and an HP test equipment inspired precision VCO working soon. And now since we are seeing more than, more 100 degrees Fahrenheit plus Sundays the extensive outdoor wind chime and wind sock collection is experiencing simultaneous UV related materials failures. I'm restringing everything, substituting new materials and applying UV protective coatings where possible. I'm assuming that the neighbors will appreciate hearing the late night windstorm concerts again. All right. Next up is David Glaver who's text only so I'll read their contribution. CircuitPython.org improvement. Some typo modification so that all boards of the same manufacturer match exactly. Thank you for that consistency check. And adding solder party BBQ20KBD that's from R2-R0182. Suggesting improvement to learn guide, how to add new boards in the CircuitPython website force the aspect width and height when using eggif.com. And also talking about creator ID versus PID and VID for ESP32 boards. ESP, PID and VID. Okay. Reporting an old BLE bug when emulating mouse on two separate devices simultaneously, testing I2C Targon RP2040 and searching the box with all my ESP32 boards and failed to find something. I don't know. Okay. I know that feeling. Like where is this thing? It's on the floor or something, I'm not sure. Okay. Next up is FOMI guy. All right. Last week did some preparation and stuff around CircuitPython day for the panel and then my game jam stream on Friday. I last week learned about building a debug build of the core, had never built a debug one before as well as using the utility to I guess decode or parse the output of a stack trace. Use that to work on troubleshooting on the hack tablet. I submitted the kind of first draft version of a PR for measuring the MPY file size from an actions task. I'm printing that information in a comment. And then last week feels like forever ago, but just a week on Monday, I submitted the Octopus guide for a final review. Couple of things in mind this week. I am looking to if conditions inside actions. I've used some very basic ones, but I'm trying to figure out how to use them to basically limit when it will actually make a comment about the file size based on if it's a big enough margin over the current version. So that we don't necessarily print stuff out if it's not really that big of a change at all. I will also in relation to that effort for the size measurements. I need to move the script that actually does measure the size and compile it together for the comment over to repo and circuit Python org right now. That's just under my GitHub. This week want to try out MPY tool, which is a command line utility and figure out what all it does, what it can do. I'm not super familiar with it and see if there's anything in there that could help us on the memory measurement front instead of doing stuff super manually with MPY files it might be able to tell us useful information about them. And then last thing I have is start publishing some walkthrough videos showing how to set up a Minecraft server and all the plugins that you need if you want to create a virtual feather synced inside Minecraft with real ones. This was a project I showed a little while back on show and tell in a few places, but it was kind of just in the proof of concept stage. And I've gone back through it and tried to really generalize it and make it so other people could hopefully repeat this on their end as well instead of just my one specific hard code it set up. So I'm hoping to publish some of that information this week in videos, thanks. Okay, thank you. Okay, next up is Jeff. Hi, so last week I was on a little vacation in Colorado which is the next state over. And on Friday I made it back to participate in Circuit Python Day about which much has already been set today. And there's an image in the note stock that I will drop into Discord in a second. I was helping move a four ton CNC machine about 15 miles across town. This morning we headed at the front of the garage where it had to leave from and by this evening it has to be in its new place. And just as an update while I've been taking a break to come inside and go to this meeting, it's reached the new shop. Yay, it's safely down on the ground but it will be a process to get it moving again just due to its complexity. It needs air compressor and three face power and things to be checked and all sorts of stuff but it'll be a little bit of a process. So for the rest of the week I am going to be working on updating the camera guide for Circuit Python to talk about the new module that's on the expressive family microcontrollers. And then after that I'm gonna start on the PyCow Wi-Fi module support. The first question is to fit the firmware blob how much do we have to give up in Circuit Python? Because I think the firmware is pretty full as it is but we'll see. And the more hopefully I should have given her a hug report, hopefully walked me through like here's how to bring up the interface that generally bring up the interface between two devices that aren't using a standard protocol. So lots of helpful ideas for troubleshooting and problems that I might encounter. So I hope that soon, but soon might be two weeks that I can get the LED that's attached to the Wi-Fi module to blank. And David asked over in the comments on the Google Doc where the firmware has to be and I clarified that it does need to be on the RP2040's external flash chip because the firmware is uploaded every time the Wi-Fi chip does not have permanent storage for the firmware. So that's simply how it works. And that means that approximately 400K of that flash chip which is split between Circuit Python and the CircuitPy drive will just be taken up by that stuff. And that probably means giving up something but we don't know until we try and that's what I'll be working on. Thank you. Okay, thanks Jeff. Okay, next up is Catney. Thanks Dan. Last week I fixed up two templates. The I2S template was using a discontinued I2S breakout so that's been updated. And the I2C template was using outdated terminology. So I got that updated. I still have a blog post update for that. I merged a few PRs, continued coordinating Circuit Python Day and the days leading up to it and Circuit Python Day which I will say I have a little paper cat attached to my microphone. And at the moment I have a sparkly purple snake that nobody noticed. So I thought that was kind of funny. This week I'll be finishing up the S3TFT feather guide and then I will start working with ESP32 V2 Wi-Fi and deep sleep in preparation for a Wi-Fi version of my mailbox notifier project. I'll be updating the Circuit Python ESP32 Quick Start Guide to have a more thorough THANI section now that support for all of this has been released. And then working on the mailbox notifier project guide. It may include Laura as well as Wi-Fi but at the moment we are changing it up a little bit. The plan is to find bugs with the ESP32 Circuit Python setup and also use THANI as my ID to test it out with the new Circuit Python ESP32 support. Then after that I'll be updating the main guide for the Quad Alpha Numeric Backpack which now has STEMIQT and then a countdown project using three of the Quad Alpha Numeric STEMIQT Backpacks. And that is what's on my list. Okay, thank you, Catney. All right, next up is K-Match. I'll read their contribution. Tested the Adafruit Ultrasonic Sensor, the HCSR04 variant to capture the distance to a rapidly passing sphere. In this case, it's a bowling ball. I think it's fast enough. That's like a very interesting project. Okay, next up, Maker Melissa. Hello, so last week I created a loader script so that the entire code.CircuitPython.org website, just the editor itself really, will load from the device itself and then I started adding some new boards to CircuitPython.org. I finished up the code for the robot I built for my live stream and then I also did lots of other like camera preparation, kind of doing a long run through for my Circuit Python Day live stream. I co-hosted show and tell again, but in the lead role this time. Then I live streamed on Circuit Python Day and I started moving out of my offices over the weekend. This week I'm gonna finish adding the rest of the boards to CircuitPython.org. And then I'll continue working on adding web workflow to code.CircuitPython.org and finish up any features that are missing there. And if there's any time left, I might possibly start on a guide and I'll probably be doing some more moving and packing from offices. And that's it. Okay, thank you, Melissa. Okay, next up is Tammy make things. Thanks. So last week I participated in the CircuitPython Day dev sprint and we had some fun collaboration and discussions. I added a comment to a pull request on the AdafruitCircPython debouncer library. I wasn't able to actually test the code, but I had a couple of comments on how it was structured and working and stuff. So added those. And this week I have no idea what I'm gonna get done because work has been absolutely ridiculous and I have 36 meetings this week. Okay, thanks, Tammy. I hope it clears up. Okay, next up is Tech Trick. I'll read their contribution. Last week hosted the CircuitPython Day mini dev sprints along with a few others in the community started submitting bug fixes about how Adabot generates the infrastructure issues page on circuitpython.org, added additional typing protocols to CircuitPython typing, updated all the version strings that typically get replaced that's in the libraries to be compatible with PEP 440 so editable installs work again. Fixed an issue with the NeoPixel library where chain dependencies weren't being recorded in the wheel that was built for PyPy causing downloads via PIP to fail. Okay, and then this week continue working on patching and improving Adabot to handle recent updates to the libraries, catch up on a bunch of type annotation PRs, implement a patch for allowing Sphinx to keep the copyright date up to date each time documentation is built and add additional cookie counter updates. So thank you Tech Trick for all this library infrastructure stuff which makes libraries so much smoother. Okay, and finally, in status reports, Ann says, I will be blogging about the NASA Artemis 1 moon rocket launch and behind the scenes as a social media selectee by NASA. Look on the Adafruit blog, Twitter and my Twitter at sign Ann and underscore engineer through into early next week. So check this out. You will see all kinds of Cape Canaveral rocket stuff. It's really interesting. Thank you, Ann. Okay, so our last section is in the weeds where we do more long form discussions that come out of status updates or that people have identified ahead of time. If you have any in the weeds topics, please make sure they get added while we're discussing other things. So we're not waiting around to see if anyone has topics. So I will turn this over to Tammy make things who would like to talk about making circuit Python dev sprints a regular activity. Go ahead. Thanks. Yeah, so I think we had a lot of fun on with the dev sprints and one of the things that we were talking about in Discord was that that kind of dev sprint format is a good way to lower barriers of entry for newcomers who wanna get involved with circuit Python but who want a little bit more interactive sort of guidance and support than just reading the learn guard guides and jumping into our very busy Discord. And so we were talking about whether it might be interesting and useful for the community if we had a monthly or quarterly like circuit Python office hours or something that we had people who were a little more experienced who would volunteer to be there. And then people who wanted that support could come and get some support. And I think if we did it on a monthly or quarterly cadence, the frequency would be manageable enough that getting a couple of volunteers for each time shouldn't be super difficult. I know I certainly would volunteer but I wanted to see what the rest of the community thought. Does anybody have any comments? I would say this sounds like a very interesting idea. And I think just the idea of office hours even if not even something else so organized is really good if somebody knows that they can drop in at a certain point to be able to ask questions and get them answered is really interesting as opposed to just posting when you're in the middle of some problem not being sure whether you're gonna be able to move on at that point or not. Oh, I'm definitely a fan of this. However, my concern which may have just been alleviated by Tectric, my concern is the cycles needed to do it. If the community is willing to support it, I would definitely be all for it. If it's the expectation is that we as developers are also required and not just able to jump in when we're available, that might be an issue just because we never know when we're gonna have cycles in the future because sometimes we're running down bugs or trying to get a final version out, et cetera. And that would mess up the cadence if we just couldn't do it at that time. So for me, the sprints are pretty confusing because I volunteered for them and I was present on all the candles. But I didn't really do anything else from what I normally do. I'm not sure if that's what I was supposed to be doing or if I should have done something else. Maybe more actively look for people who need help or something. So I'm not even entirely sure what's happening during the sprints because for me, it was regular helping on this card. The Shippu, you're always helping folks. And that was the point. It was just that was a time dedicated to helping folks. So you doing exactly what you normally do was absolutely fine. Okay, thank you. That makes sense. Yeah, I think the goal at least of what I'm imagining is that we would announce ahead of time and at the time of whenever we're doing it, like, hey everybody, I'm here for the next two hours if people have questions or need a little bit of extra support and like there's people volunteering to do that. And it doesn't even necessarily have to be scheduled ahead of time. Although I think it's beneficial if people know the fourth Friday of every month from whatever time to whatever time you can come to the Discord channel and there will be somebody there who is like sort of there just to help people. I agree with the scheduling. I think it adds a little bit more. I know like when I joined the community, at first it was a little bit overwhelming to try and just jump into the Discord with everything that's always going on there. So some way of making it visible, that there are people here who they are here for the purpose right now of helping you if you need help getting started. Something like that. That reminds me, there used to, Brian Locke used to have for just a few streams, used to have those streams called Project Doctor. He would basically sit in the stream and people would ask him questions about their own projects and he would give suggestions about what could be done to improve them. I'm not sure, this is probably something completely different but I'm not sure if that could be useful somehow. Like have a Project Doctor. I know I have helped with Project Doctor or something like that. But it's not just throwing it out there. Just throwing it out there. Not really suggesting anything in particular. I think that's an interesting idea too. That's sort of like office hours. So he's had, we know of some other Discord that do this kind of thing. I think we could just try something on a casual basis and see how it evolves. I don't think we have to format in stone or something. So I'd say like if we set a time, see how it works. I think it might be interesting to have times that are not always at the same time, especially for people in other time zones. Like we might think of a morning sprint for people who are in Europe or further afield at some point and announce that in advance because usually often people are not on in the morning and so people in Australia or somewhere else might say, I just, I never see those people on when I'm awake to be able to ask them questions. So you might consider also some more unusual timing on some cases. This meeting actually started as something totally different and evolved. So I agree entirely with, let's just give something a try and see how it goes. And yeah, move forward from there. So we can, Tammy, we could make a thread on the CircuitPython dev channel here for discussion. We can add all the folks who are interested in helping out and other folks can view it and comment, but we could at least make sure that we invite everyone here who said, I would love to help out with this, et cetera. Is that okay? Absolutely, absolutely. Perfect. That's, I think the route will go and then we can give it a try and see how it goes. Okay, that sounds good, Tammy. All right, if anybody wants to add a couple of notes to the, in the weeds to the notes doc, that'll be great just to summarize. Like that will have a thread or something. So that'll learn people who read the notes doc. So I think if there's nothing, is there anything else? Otherwise I'll move on to the next topic so I have this, which is quite short, I think. Okay, I will go ahead here. So my question is, we have a space problem on the matrix portal. It's at SAMD51J19, which doesn't have as much RAM as the other Pi portals, which tend to be 51P20s. And so we found that projects on the matrix portal often run out of space. When you import large libraries. So we've frozen some libraries, but then when we freeze libraries, we don't have enough room for all the usual firmware. So we've actually gone around, like at one point we removed VLE support to make room for the libraries and then we added it back. We've also talked recently about removing ULAB because that's also large and both of these things have disadvantages. And so Carter and I, for instance, discussed, like, well, if we had to get rid of one of these things to make room, which would it be? And I was just wondering if people have done matrix portal projects or other display projects that use up a lot of RAM, whether you feel like, oh, if I didn't have ULAB, I'd be in trouble because I'm doing all kinds of calculations or, oh, I really want, if you got rid of VLE, I wouldn't be able to update my Times Square News display from my phone or something like that. So if anybody had any opinions about either of those things, about which you'd be the most reluctant to give up. Maybe you have no opinion. It's okay, too. Go ahead. I think we're leaning toward, I think there's more, Carter thought of more projects that you might want to do with VLE than that ULAB. Yeah, I was leaning towards keeping VLE as well because it seems like you can do especially a lot more basic things. I don't know that it necessarily holds true but ULAB strikes me as a bit more advanced and the person who's interested in using it in a project may have an easier time being able to make a custom build and get themselves straightened out. Right, and there are the other things that they might then take out to make room or something. I mean, ultimately, we can also try to reduce the size of libraries but that's pretty difficult and you won't gain, we need to gain a lot of space. The library that was frozen, we took it out and we want to put it back and we put it back and it was like 16K of MPY size or something, so we'd have to cut it way down to make any dent in that. So I think we'll move toward you taking out ULAB for this particular case. Ultimately, we've talked about how the matrix portal product itself might evolve. It's not stuck, we have plenty of other chips that we can try to replace some of the stuff, make a new kind of matrix portal. So maybe someday you'll see something like that, who knows. All right, that's it. So is there anything else before I wrap up? If not, I'll tell you that the next week's meeting will be on Monday, August 29th, 2022 at the same time 2 p.m. U.S. Eastern, 11 a.m. U.S. Pacific. That's at the regular time. In two weeks, there's a U.S. holiday so it'll be pushed forward a day. But next week it will be at its regular time. Okay, thank you everyone. And we'll wrap up the meeting for today, thank you. Bye-bye. I'll stop recording. Bye-bye.


This coming Monday, June 13th, donors, foundations, advocates will be gathering in London for the first pledging conference for the GAVI Alliance, which is the alliance that delivers vaccines and immunizations for the world's poorest populations. This is a very important moment. The organization has put out an appeal for $3.7 billion in assistance for the next period 2011 through 2015. They're hoping to be able to add that to existing resources of $3.1 billion and be able to bring forward vaccines for an additional 250 million poor children around the world. Despite the poor economic circumstances and the budgetary stress that governments are under and donors and partner countries, there's quite a bit of optimism that in fact they will achieve success. And if they do, this will carry GAVI into a new era. The GAVI secretariat will have a new president and CEO as of August 1, has a new board chairman and is looking to really put the world's focus on this critical dimension of global health, which is that vaccines are vaccines particularly for poor populations, especially for the young, are a specially effective and cost effective way of improving the health of the world's poor and reducing mortality and illness. In the future, looking beyond the pledging conference in London on Monday, it's going to be very, very important to take the long view and for the GAVI Alliance and its backers to be able to build substantial resources into the long term from multiple directions. There needs to be higher level efforts at engaging the emerging powers to begin to participate as backers of this initiative and there's much more that can be done in terms of getting partner recipient governments to engage in higher levels of co-financing and there's more that can be done in engaging industry and shaping markets so that price levels can be brought down without damaging the market so that you can get better bang for the buck in the dollars that are secured.


How many of you have been to an Agile Conference before? If you've been to an Agile Conference before, you know what happens when the person nominally leading the session puts their hands up, don't you? Everyone else puts their hands up and stops talking. Kia ora tātou. Good day, folks. Cora Shane Hasty, teni. My name is Shane Hasty. I've got all sorts of things that I do, but one of them is I'm the Director of Agile Learning Programs for the International Consortium for Agile. And this session, we titled the Golden Age of Agile Coaching, but really it's my journey to becoming a coach. So we started with a few questions. I hope you're now sitting next to somebody who you now know that you didn't know before the session started and that you've had a conversation. So what are some of the characteristics? What are some of the things that you concluded makes a great Agile coach? Please call them out. Asking powerful questions. Not giving the solution. Being a good listener. What's the difference between a scrum master and Agile coach? Is that boundary? Does it even exist? Maybe we can explore some of that. Allows people to come with ideas, to bring their own ideas. So there are some key things about coaching and capabilities. And I'm going to go through the coaching as a discipline and then Agile coaching as, oh, is it a subset or a superset of professional coaching? The domains, the competencies and the journey of becoming a coach. Then we'll put it into practice. We're actually going to use powerful questions with each other. I'm not going to use them, you are. And through this, I will talk to my own personal journey of becoming a coach. So first of all, what is coaching? There is a discipline of professional coaching. And there are bodies, one in particularly the International Coach Federation, that has a framework for what coaching is about. And they do distinguish between coaching and other disciplines. And they provide some very explicit guidelines. It's about partnering with clients in that thought-provoking conversation, a creative process and some of the points that came out, the coach doesn't have the answer. The coachee has the answer to maximize the coachee's potential. One of the things that the International Coach Federation in particular focuses on is that coaches need a code of ethics and professional conduct. This is something that, and this is a personal perspective that I strongly believe is missing in the Agile community at the moment, is most of us who call ourselves Agile coaches do not have a commitment to a professional code of ethics and conduct. And this worries me, because coaching can do a lot of harm. Any of the professions that have a code of conduct, almost always their code of conduct starts with the duty to society as a whole and do no harm. How many of us are coaches in the room? How many of us self-identify as a coach in some way? How many of you have signed a code of ethics? How many of you live by a code of ethics? A few. I would encourage those of you who aren't, who haven't gone down the professional coaching journey to think about this is actually where we need to go. The ability to establish trust, the coaching presence, the respect that we pay the coachee by being 100% focused on them and their needs during the coaching engagement. Incredibly important. Facilitating learning. And here's a scary one. The coach takes accountability for results. All too often I see, particularly in the agile community, the agile coach comes in a bit like a seagull. Screams a lot, perhaps all over the place flies out. No. The coach on the ground, and if we think of the sports teams, the coach on the ground is responsible for the team's outcome. The players play the game. But if the players are consistently unsuccessful, the coach gets fired along with everyone else. But in the agile community, we seem to have forgotten that one. No, no, no, we don't take accountability. We care a lot about these people. But obviously when they didn't do it right, they didn't listen to me. That's the coach's mantra, isn't it? So coaching is a partnership. There's a process for discovery. It's a way of exploring options. And it is not giving advice, consulting. It's also not learning from an experienced professional. That's mentoring. Now, consulting and mentoring and facilitation are skill sets that matter. But they're not coaching. So I want us to think carefully about what it means, what coaching is, what it isn't, and what does it mean to me to be a coach? Lisa Adkins in her book, Coaching Agile Teams, has generously given the world this diagram, sometimes called a butterfly, the X-wing, the picture of what are the competencies that we need as an agile coach. So one of them is that professional coaching. So this was the question I sort of asked earlier on, is agile coaching a subset or a superset? We are saying, and Lisa is saying, that professional coaching is one of the competency areas, and she actually does reference the ICF. But then there's others. To be an agile coach, you need to be a strong agile lean practitioner. You need to understand not the mechanics of agile. You need to understand deeply the intent of agile. So whatever framework you have chosen, why do the elements of that framework exist? If we talk about SCRUM, one of the most common practices within organizations that adopt SCRUM as a framework, is the daily stand-up, the SCRUM meeting, in which we stand in front of each other and we ask three questions. What have you done? What will you do? What's in the way? What's the difference between that and a status meeting? And as an agile coach, if you can't answer what's the difference between that and a status meeting, you are not a deep agile practitioner. By the way, the difference? The questions don't matter. The purpose of the daily stand-up is for a group of people who have work that has a dependency upon each other to collaborate effectively in the delivery of that work. Status can and should be achieved through other means. And if your daily stand-ups are focused just on those three questions and status and you're reporting to somebody, then you are not using the SCRUM meeting with the intent of the SCRUM meeting. And if your coach is allowing you to get away with that, they are not a coach. They don't have the deep agile lean practitioner competencies. Then there's the teaching competencies. As an agile coach, yes, we have to be able to teach the practices to explain to people how to use the different practices in the context of their organization. A coach needs to be able to mentor. And the mentor relationship is learning from the skilled professional, from the experience. When in my experience, when I saw this context, this situation, that's what happened with me. I shared experiences. That's mentoring. And then facilitating, taking groups of people to a journey of discovery together, to achieving outcomes in group settings. And then, oh, by the way, on top of that, we also need to have at least one area of deep mastery as a coach. Whether that's technical, if you're working with development teams, can you help those teams implement a DevOps framework? Can you pair with somebody in designing the architecture for a new product? If you've got that deep technical mastery. Or is it about business mastery? Do you understand the end-to-end value stream? Can you empathize and bring the customer voice to the team? Or is it about transformation, working at the enterprise change level and looking at areas of organizational design and bringing structures like holocracy into an organization? This is a scary framework. This doesn't happen with a three-day training class. To become a competent coach with all of those skills requires many, many years of deep, deliberate practice and working with a variety of teams in different contexts. And we need to start as a coach. The area we start closest with is self-management. If you cannot hold the mirror up and know your own strengths and weaknesses, then how can I dare turn to somebody else and say, hey, here's a mirror, look at it? But that's what I've got to do as a coach. And then I can work with individuals and I can start to hold the mirror up there. Then I need to work with teams. And this is maybe where the role that Scrum calls the Scrum Master starts to come into play. Some of the team facilitation skill sets that enable us to work with groups of people and help them achieve their common outcomes. And then moving towards multiple teams looking at coaching at that team and program level. That's the agile coaching. And even at the enterprise level working at the organizational level. And typically we do see this as a progression. I know for myself, I'm not good there. I don't have enterprise transformational experience. I've never worked in those roles. I would not go into a large organization and say, oh, let me coach your executive team. I haven't worked at that space. I don't honestly know whether I want to. On the other hand, at the program and team level, I'm good. I'm your person. I can help there because I've done this a lot. And my personal areas of mastery, not too bad in the technical, but that business mastery, that's where I truly can. So if the problems the team is facing is around understanding customer value and so forth, I'm a really good person and I can bring that expertise in a mentoring perspective. I can also ask powerful questions because I've experienced what's involved at that level. So again, know thyself first and foremost. And there are multiple paths to mastery. Obviously, I work for ICHL. We are a certification organization and we have a pathway for coaching. And it starts with the foundations and then it goes to that team facilitation. And this is a course that we see a lot of take-up in India, the three-day agile coaching. And it's very important. This is agile coaching, not coach. And at the end of that, you probably are a beginner. You're at the level of Shu in the Shu Hari. You understand the key competencies. You know what you don't know. You need to go away and build on that. And now you go and get deliberate practice.  You work with different teams in different contexts. You find different challenges. And you fail frequently. And it's okay. You can do the failure bow. And you build additional skills. That is not enough. In my own journey, I went on and my strongest competency area in the X-Wing is actually the teaching. So I went deep into learning the teaching competencies. So, for instance, things like training from the back of the room is a way of designing classes. There's some of that in this concept, in the structure of the session, with the connections activity right at the beginning. Then when you get to a point where you consider yourself an experienced practitioner, there's a way of validating that. In the icy agile world, this is a competency-based certification called the icy agile certified expert in agile coaching. You have to have a minimum of two to three years' experience and a wide range of experience. You have to be able to prove that experience through CVs and references. And then you have to provide evidence of competency in two of the skill sets, being facilitation and teaching, and that's done by submitting a video. The panel then looks at those videos and looks at your references and so forth and says, yeah, looks okay. Come and be assessed.  They test your knowledge, but much more importantly, they assess your competency. In that live session, you are expected to coach somebody on a real issue that they are facing and take them through the coaching arc. And you need to take them through a mentoring arc and you have to be able to show the difference. Live with people, in my case, people like Lisa Adkins was doing the assessment. That's scary. Oh yeah, I failed. The first time through, I failed. I felt I was ready. I'd had all the knowledge. I'd been a professional coach working with teams for four years. So I went up, went into this initial assessment with a level of confidence, dare I say perhaps a little bit of arrogance. I know what I'm doing. And then when I coached a person who had a real challenging issue that I empathized with, I didn't do a good job of coaching. I wasn't able to hold up the mirror and help them come to conclusions. Not too bad. And there is a published rubric that looks at what are the competencies and how well, what do you need to achieve. But the first time through, I failed. And failure's not fun. The feedback from that panel, however, was incredibly powerful. There were very, very explicit things that they said to me, this is where you need to go and build your strengths and go away and work on this. And they took, they gave it to me in writing that I could walk away from and say, okay, here are things I need, I know I need to go and do. And I went away and for another seven months, I put in deliberate practice in those areas. And then in August last year, I sat the assessment again. And this time I passed. 60% of people fail that first assessment. And that's really good because the learning that comes from that failure is really, really important. So there is a pathway. But even at that level, I consider myself maybe an experienced practitioner. I'm hard. I know before read and read comes from many, many years of working with multiple teams with different people with different problems. Addressing adapting practices. But please do not call yourself a coach when you are here. So yeah, there is a published rubric of competencies that looks at the, at these different areas. And if anyone's interested, I'm happy to share it with you. And it's available on the ICHR website. When I went into the first round of assessment, I think you've come across this Dunning Kruger effect before. It was a study that looked at how confident people are in their competencies based around their level of knowledge of a topic. And there's a point very early on just enough to be dangerous. Think of the 17-year-old boy learning to drive. And I'm not sure who authored this that came up with the, the peak of Mount Stupid. I've been teaching a 16-year-old granddaughter to drive lately and we've had a few Mount Stupid moments. And then we get to the valley of despair. Oh no, I realize just how complicated this is, how hard this area is. And I'm at the beginning of building wisdom. And really interesting in the studies that Dunning Kruger did, we never get back to the peak of Mount Stupid. We realize that the more we know about something, the less we actually know about it. And we become wise over time. So one of the promises of this session was you will get an opportunity to do some coaching. Think about one of the specific competencies. And it was mentioned earlier the concept of powerful questions. Powerful questions are ones that do force you to look in the mirror. To explore possibilities together. So examples of things like what would you like to have happen? What may be holding you back? What would the ideal outcome look like? Now, if any of you are going to get some coaching from Deb, I would deeply sincerely encourage it. On Sunday evening, after the coach camp, she and I sat down and she gave me a coaching session. And it was a deep experience and she uses powerful questions phenomenally well. So if you're struggling with something, I would encourage you to take up that offer that she's made. But the more common types of questions we often see are the what's the problem? Can you do that? The advice couched in a question. Why did you do that? Judgment. So let's put this in practice, shall we? Please stand up. Form groups of three. And we're going to do this fairly rapidly. We will have three three-minute sessions in your groups of three. And each person will take a role initially. One will be coach, one will be coach E and third one will be observer. Coach E. You have something that you have been struggling with at work or at home. I'm sure you have. Coach, use the powerful questions and here are some examples. And I'll leave this up on the screen while you're busy. Spend about two minutes asking those powerful questions and exploring this topic with your coach E. Observer, watch what is happening. At the end of two minutes, I will stop you and the observer will then give feedback. And then we cycle. The roles change and we repeat the roles change, we repeat. Does this make sense? So each person will take coach, coach E and observer role and we've got nine minutes. Go. Just experience it. Just the experience of using powerful questions. Yeah. So as the coach the coach E has got something that is struggling with ask the powerful questions and see how it feels and then the observer will watch what is happening. Okay folks, that is the first round. Observer you've got one minute to give feedback. What did you see happening? Think about emotion. Think about interaction. Think about engagement. What did you see happening? And then we'll cycle. Okay, time to cycle. Move, move roles and do it again. So the person who was coach takes a different role, coach, coach E Observer. Another two minutes. The next session needs I was looking, I was just going to say this. Speaking for the next session needs those. All right, that was two minutes. Again one minute of feedback. Observer, please tell your coach and coach E what you saw, what happened. This one would be met with three 10 minute blocks. That's okay. They're still getting the experience. The hands-on piece. Yeah. That's it. Okay. And cycle different coach, coach E and Observer. And then people put half an hour of the practice. And the Observer is really important because it highlights things. Yes. Yeah. Yeah. That was two minutes. So a final round of feedback from the Observers, please. Okay, folks. Now this would have been somewhat frustrating. I'm very sad to have to stop to cut you off at this point. But we do have time limits that the conference has imposed upon us. But I would encourage you to think about doing this as practice back in the workplace. And that pairing of coach, coach E and Observer and take the different roles and give each other the Observer role. Really, really important. And yeah. The slide set is all available for download and there are some examples of powerful questions. But if you just do a simple search for powerful questions, you'll find lots of them. So my story I spoke about I would like you to stop and think as we finish up what are you going to do differently? And one of the most important things that I hope you take away from this is that coaching is a journey and becoming a coach takes a long time. It doesn't happen with three days of training or whatever else initial kickoff. But the journey to becoming an effective coach and think also please about that concept of professional ethics and the responsibilities and accountabilities that we should have as agile coaches. There's about one and a half minutes for questions. Imposed by the organization. And as you deal with people and I believe strongly that as agile coaches you do work with people. It's more about people and less about the process at some point in time. So during your Shuhari journey it's more you tend to be more people focused rather than a process focused.  The frameworks are like training wheels on a bicycle. They're a beginning point but the mindset of agility and this is the mindset day. That is something that is if you're acting as an agile coach that mindset of agility is incredibly important and knowing the practices and the intent behind any of the practices. Being able to convey that and look at it in terms of the human impact of that. But then as we become more and more coaches it really is about working with the teams and inevitably thinking of software engineering and software development teams. These are people who are professional problem solvers. As a coach my job isn't to give them answers it's to give them here are the questions because they will figure out. Alistair Coburn got his PhD and he was looking at lightweight methods way back in the 1990s and he actually came to the conclusion that left to themselves that if you're a professional problem solvers with a small team with a defined problem the best methodology is no methodology because that team figures it out for themselves as the coach my job is to create that framework of safety for them to do so. Thank you. All the things he's just giving us a question there's no ground reality there and we don't really have an answer and it's a very practical thing that actually happens. How do you use the gap between the developers and the jugglers and make them really understand because when we give them examples of games let's just go to the football team okay they coach them there but we're not playing football those are actually not the exact practical examples that we go to because we do like let's get games with the different examples that's not the difference so how do we use the gap when the team actually has to trust the coach and accept that their question is actually ultimately going to help them So one of the key things there is does the team need coaching or teaching have they got the competency or do I need to help them gain the competency if they're coming to me with a question and the question is we do not know how to do this we've got no idea then coaching and saying what would be a good way to do that it's not necessarily the right approach I might need to change hats and if we go back to that x-wing diagram teacher or mentor might be the better role for me to take in that context so if it truly is there's a lack of knowledge on how to do something then teach the team be open that I am teaching I am not coaching when I am coaching we are exploring something together that you will figure out the answer to I'm also never consulting the consultant role is to come and do it for them but as a teacher I'm pointing them in the right direction as a mentor I'm looking at my own experience and saying I did this there this is what happened would this be applicable to you whereas as the teacher I'm saying here is how you set up the framework for continuous integration using these tools now go and do it as an example does that make sense so it's change the hat you're wearing but be clear with the team this is the mode I am in a different set of interactions I'm going to be around the whole week thank you folks


on state-separating proofs of reduction methodology for real-world protocols. Oh wow, thanks for reading out the title. So, that's a more serious talk. So, sometimes I suffer. So this talk is about easing my suffering. So more in detail. Key exchange researchers more generally sometimes suffer. And so this is a self-help talk for key exchange researchers. So I want to share my experience as a key exchange researcher and tell you a little bit of how I hope to overcome some of the obstacles of key exchange researchers. So once upon a time, I was a PhD student and I worked on key exchange. And at night, when I wrote proofs, I suffered. Because there were tons of work. Because key exchange protocols were super, super complicated, especially real-world protocols like TLS. They had many, so the proofs, many see me in these simple steps. But once I had done the proof, I wasn't even sure it's right. So it was not possible for me to verify where it's right. It was not human verifiable.  So those are actually very simple. So you have a key exchange protocol that outputs symmetric keys that look random. And then you use them in an application protocol that is secure with random keys. So this should be straightforward, even without using universal composability. So what I was really concerned about is the theorem seems very simple. So why is the proof so hard? So I tried to see the aspect where I tried the nice things. My colleague tried the nice things. And each time the proof looked really, really happy. So one of the difficulties is that there's state between the key exchange and the application protocol, namely the keys. And this is a multi-session and multi-instance game. So in more detail, how do we prove things? So we would prove things by saying, okay, replace those key real keys with random keys and then reduce the security of the application protocol when you use random keys here. And so in each of these steps, you have to maintain lists in the reduction, pass on keys to the right sessions, etc. It's boring. Yeah, it's boring, but it's very complicated, and you have to do it. And in this religious step, you also have to do it, so it's very annoying. So the first idea is to say, okay, if we share state between those packages, maybe we can move the state to a key package and have the shared state in the one-year version. And then you have rules to specify those packages. So then you get the reduction automatically. So the idea is that when you reduce to the application protocol, this is your reduction automatically. And so the idea is to define operators that allow you to come to those packages. So one is a regular operator that allows you to parallel composition, and if they use a package in a circle or a rotor, and this allows you to do proofs in a very simple way. So then we define some algebraic rules, which, so for example, for the hybrid argument, you can plug in an ID, and this is still the same package, and now you can do a hybrid proof in a very simple way. So this becomes your reduction to the simple assumption. So let's start from the beginning. You want to swap out this package 0 to 1. We do this by moving this package here, this is the reduction, then we can reduce to this single session assumption, and then we can move it back. And this is automatic, and what doesn't need to do anything for it. So this is just some example. So those simple steps, they're a little work, they're precise, they're human, they're very viable, and so a little bit of the notation. So Mike Roosevelt uses some of those ideas, and especially a very similar notation, in the draft of his book, The Joy of Cryptography, which is very, very nice, and he has been using this in his undergraduate classes for many years. So I think this makes this type of notation very usable for making complicated proofs as simple as possible, and I think it's a very useful thing. So our hope that we can use this method to prove TLS 103, to use this method for material reductions, to make key exchange tables readable again, and most of all to suffer less, and to hopefully understand more. So my request and my suggestion is that if you suffer from writing seemingly good simple proof steps or from making them accessible to readers, check whether our notation can help, and if you have the same struggle in teaching, check whether Mike's book can help you. So many of those conceptual ideas are, of course, new. Some of them are from the universal composability framework, some of them are from the random system, some are from Crypto, constructive Crypto, some are from the METLS work by Mike's research in New York, Paris, some are from PyCode, and we put those ideas together with a focus on proofs. We're not trying to find the right model, we're just trying to simplify proofs as much as we can. So it's now in the different states of writing proofs, the reduction methodology for real particles and maybe help you too. Thank you.


Namaste everyone. Today I am here to talk about Aishwagandha, this magic herb. Many of you might have heard about this particular herb. It's one of the best rejuvenatory herb, adaptogenic herb and it also has the beneficial effect on the body and mind. It's very famous for its effect on stress. There are several research study also evaluating the efficacy and effectiveness of this particular herb for stress relief and calming the mind. Another effect of this particular herb is it's also good for muscle building. It gives the strength to the muscle. There are several research study happened on Aishwagandha and its effect on improving the immunity. So, it's very important herb in Ayurvedic medicine. Please visit us to learn more about Ayurvedic medicine.


Hello everyone, welcome back to the Average. Today we've got a cool thing that we're doing. Potted sent me this home pottery kit so we're going to try it out today and I have a special guest Christopher, my husband. Say hello. Hi. For your hands in, you have to wave. A bit further, bit further, very good. I've also got these pastel pinks that you can use with them which is going to be great. So what do you get? You get a quick start guide. Top tips. So it tells you how to use, it gives you instructions, how to paint, how to do these things. This is cool, like different, ah, examples. I want to make a pinch pot. That's not a pinch pot. I don't know if I want to make a pinch pot but it gives you all the instructions on the different things. You just pinch it. Yeah I think so too. A squiggly tray, a trinket-ish for your trinkets. Photo stand, that's quite cute because if you have, we have one of these uh, bolognese cameras. That's what I want to do, a plant pot but for pens. I'm going to do this one. Chris, you just said what you want to do. Comes with everything you need I think which is really cool. I've got tools that me and Chris are going to fight over. A sponge, a stick, another stick. Need water though. Really, more sticks and a little curry. This is really nice actually because all the tools are branded which, quite sweet. Mm. Quite sweet. Super sweet. So I've got another pastel pinks which I didn't know it came with so there we go, we've got two pastel pinks that we can share. They look good. I used to talk into myself. Well I didn't know I was on the video so now I don't know how much do I say. Paint brushes, very nice. Very good. Stop. Just stop and do it. Super clay. It's a two days to dry. Okay so we'll do another video of us painting them I think. I don't know what this is, oh this is for the instructions to hold it up. We've got gloss varnish and base coat. So let's get going. Oh it's very brown than I thought it would be. Very brown. Pesto. She wants to do a pop too. Pesto pop. Why are you talking like that? Okay. She wants to do a pop too. It's the YouTube candle. Hi everybody, welcome. Chris you can have this much because that's what I've decided. Gimme. Gimme that. I'm already like annoyed with it. I feel like it's going to be weird in my hands. Okay divide the clay into a small bowl, one for it and are you okay? Can you get in camera please? Uh yeah sure. Release some water. You don't need constant background noise. Oh my ring's really good.  Ring flakes. Okay cut that out. It's not going cut out. You're going completely destroyed. No, my first time doing a video with you. Can you see on your side? There's a reason you're being very bourgeois. This is my one and you were doing a pinch pot. Where's your pinch pot instruction? What are you making? I'm making a plant pot. Oh right that's what I want to make. Don't look at mine. You're not making a plant pot as well. I couldn't find those instructions. You're just copying me. No we can both do one and then we'll see where it goes. Make a little vase or something. Then we compare them. No because you're going to beat me. I'm not going to beat you. Yes you will. I've never done pot for you before. You'll be amazing at it for sure and then I'll just be sad. Are you talking like it's not really so insecure? Stop being so insecure. Chris it doesn't mean flatten it.  Yeah I can't really read the instructions. It's right there. It's not that hard. It says divide the clay into one small bowl, one third and one larger ball, two thirds and also grow up like seriously. I think I've done mine. Okay roll small ball out into a small circular slab. This is small ball so this is my small ball. I feel like this is not small enough now.  I'm going to roll here. Okay go for it. Yours looks very oh no I think with the tin foil. This is trash. Why are we making the same thing? It's so boring. I was going to make a pot anyway. Yeah but you're going to make a pinched pot. A pinched pot. Okay my turn. I need to roll mine out now into a small ball. How are you supposed to make that round honestly? Oh use a bowl. Okay we need a bowl. We need a bowl Chris. I think that this grease proof paper doesn't really help. I think you're grease proof. But does it have to be a centimeter thick? It doesn't say anything about. It doesn't say anything about a centimeter but I do need to cut it into a bowl shape. I think I'm just going to do it. Just wing it. I'm just going to ring it. It's going to make my own circle. What are you talking about? Hey!  Five minutes earlier. Have more confidence in yourself. Two seconds later. Well if my pot is wonky I don't mind. I think it's going to be quite cute. You think it's going to be charming? Yeah like a wonky pot. Like you don't make stuff to just have perfect like things is it? Exactly. That's my point. That's my point. You don't make stuff to be perfect. Yeah you don't have it. You don't want it like like manufactured. Exactly. Zuccements. Okay done it. This will form the base of your plant pot. It's a little bit thin. Last ball into a long salad. Why is mine like break apart when I roll it? I'll just get your hands wet. I don't know. Yeah but yours is looking terrible and also get on camera please. Sorry I'm not a professional like you. Yeah well you have to be. You have to turn up. Yeah. You have to follow instructions Chris. I didn't say to use water though. It doesn't matter.  Get bullied on YouTube. Shout out. It's too wet. I feel like this is not this is too thin but let's see. No that's not thin enough. I don't know. Okay that looks much better. What's going on? Why is your so scrumpty? I'm not sure why it's so scrumpty. You've overworked the clay. You've overworked. I have no idea. Don't make you nervous. Can you hurry up? You've rolled that out five times now. Yeah because I hope I'm trying to get it like perfect but it's just fading every time. Please. Sorry I've messed it up wait. We don't need a bowl. You've got to do it by eye like me. Oh we'll do a square. No it'll be too hard. What are you doing? Don't go away from the instructions. Don't do these. We have a plan. We have our instructions. That's what we're doing. Plant pots have to have folds in the bottom though. I thought that was something you should do right but this one doesn't. I'm not going to use my for plants. I'm going to use my for pens but I'm just saying. Could be nice. Look at your perfect circle.  You dare sir. You know I've only got one shot. I've got to make a count. Mine is not really a circle now. Oh crazy. Come in secure. Mine's bigger. We're going to have a bigger plant pot. Now I have to make a long thing. Now what do you know? I'm going to make a long one. Cut that out and you make a large bowl into a long slab. What's that just gone in there? What is that? A bit of crumb. Try not to hit my ear. Yeah could you move your perfect circle out of the way? I'm going to destroy it. Relaxy here and it's perfection. Oh really? So once big boots. I don't know what that means. Don't need a ruler. We just play it by ear. Watch it be not long enough. That's wonderful. Wait, wait. I'm going to do this eye now. These are going to be for my bits. I'm going to stick on the outside because it doesn't say to do anything on the outside but I'm definitely am. You're going to decorate it. But I'm definitely am. What are you going to put on the outside? Cats of course. I'm going to put cats and like sparkle shapes. Look at that. The perfect scraped rectangle. It's not a thing square and it came out of scraped which is not even a thing. It's a scraped angle. It's perfectly scraped. It's great. You think it's going to go around all the way. Good question. You know what? A ruler would be handy right now. How? You can't measure the ruler of this. Here you go. I'll take measure maybe. Okay, okay. Okay. Is it going to make it smaller? We can make that smaller or? Yeah. Wait a minute. Oh is it going to be the perfect circle now? Am I really, really good? Look at that. Okay. It's not hurt. It's not quite Chris's perfection circle. Don't touch. Sorry. Okay. I'm going to move mine other way so you can make your rectangle now. That looks great. That looks creamy. It looks delicious. Awesome. Oh no, you got skunk on mine. Slather some water on. What did you say? Like creep. Oh no. You pushed too hard. You have to be gentle. Oh god. Put too much water. What did you say? Good to be gentle. Oh my god, weirdo. Why is that weird? Why is everything like that with you? What? Just cut this bit. We like that again. We say you're perfect at this, but because you have like five tries. Christopher, in the frame, please. For the ladies and gentlemen's at home's to seize. What shape do I have? You have to make it a ball. Like remember the instructions from the beginning. This is so painful. I didn't know they skipped ahead. No, not too much pressure.  Make it a ball. Has to be a ball. Okay. Perfect. So close. It's sabotage. You need to hurry up. My thing is getting melty. My side of my pot is not doing well over here. You need to hurry up. Almost died. This is good. It's stressing me out. We're dying. These plant pots are going to be tiny by the way. We're like, yeah, we're going to make this giant plant pot. Now we've just got these two tiny. They're broke again. What is going on with you? Why is it? I don't understand. Maybe it's too hot. The place too hot now because you'd be working it too much. Maybe I'm not an expert, but I just put this down again and just roll it out. Oh my goodness. Please. Sorry. Shall I do it? If you want. Okay, I can try.  You have to babysit mine. Why is it drooping over the edge? What did you do that for? Why did you do that for? It's to spike. No, no, I didn't do it to spike. You're naughty. Let's make this into a ball again. Perfect slab. Also, I don't think you have enough clay here. I've got enough. I've got enough. No, it's not enough. I want clay here as well. It doesn't matter. Clay Guida. What? Maybe it's because of this, like the rollers wet. It could be a multiple reasons that we don't know because we don't make clay things. Yeah, come on. Give us a break. Give us a break. Chris, please, hurry up. This is how my brain works. You ready? Ready about five hours ago. Okay, you just chuck that and it hit my base. And I'm annoyed now. Your face? The base. We need this for our bits and bobs. Indiana Jones and the rolling pin. I loved it. I could cut that out. No, that was so good. I haven't cut that out. Indiana Jones and the rolling pin was so good. Yeah, I loved that. Didn't you see my reaction? But yours is looking really short compared to mine. Yeah, that's cool. All right, let's get both of them on camera now. Yeah, let's just roll mine out. There's not enough time in a day, Chris. It says to score the bottom. You can see that me and Chris are very different the way that we approach stuff.  So it's really hard to work together at the same time, but it's fine. Okay, now we have to score the outside like this, Chris. Here's your tool. Are you doing it? You've got one. Never mind. No, because mine's not long enough. Mine's really short.  Okay, I don't know how long it hasn't been recorded, but Chris is rolling his out and I'm attempting to make the side. It says to carefully wind a rectangular shape around the base and then cut off any excess. It's so hard. Why is it falling? There's no way it's going to stand. It's too thin. It needs to be thicker. It's too thin. I'm just going to go for it. I don't care. If it falls in, it falls in. If it dies, it dies. Slip and blend the pieces together. Okay, I can try. This is painful. You got it. You got it. Here is Chris's perfect sculpture. Structural integrity is an A star. Smooth. And then here's mine. And it's got a little wonky, but we still love her, you know. We have to love wonky pieces of work sometimes. But yeah, we're going to leave this up to dry and then we'll probably decorate these next week. So if you want to come back next week, subscribe and like the video. Thank you. Just ridiculous.