Hello, my name is Amanda Killibuck. I am the manager of employment and education at the Museum at Inuit, located in Ottawa. Well, we have several programs. We used to have the education support program, and that was funded through the Ministry of Advanced Education and Skill Development. And that was targeting Inuit students in the Ottawa area in post-secondary. So it would range from, like, 18, 19 to probably early 30s. Yeah, and we would provide social, dense, cultural, sensitivity training if needed at the post-secondary institutions. We work with the Indigenous Centres in the post-secondary institutions, and we provide, like, country food and emotional guidance, I guess. Our aim is to provide the necessary wraparound supports needed for a student to be successful, and it all depends on each person's version of success. It's not necessarily completing a program. There's a lot of circumstances where a student may face where they might have to make a choice. And so our programming provides them the tool box, I guess, of whether it's coping mechanisms or just available options for them to make choices and hopefully stay in school. We also, like, through my other funding pod, which is assets, so it's the Aboriginal strategy on skills and training, we put together a program. So we have partnerships with other companies, and so we provide first aid training, forklift training. We might do a hodgepodge of certifications and then, like, with women's working at heights, food safety. So with that, we don't necessarily teach them, but we kind of put the programs together to offer to our clients. Well, it builds up confidence. These are very short-term programs. We also partner up with iSisters, it's another non-profit organization, and their mandate is to increase the technological skills of women. And so then we partner up with, let's say, ESDC, and so they might come in and do a job fair presentation, and back in the fall they hired four of our graduates from iSisters. And then we did a landscaping program last summer, and we partnered up with Habitat for Humanity, and so they were able to spend a day or two building a home and using the skills that they learned in the landscaping program. When I first started, there wasn't as much, I guess, any cultural inclusion in the program. So we've been trying to incorporate, like, elders, or with iSisters, have a side project within that program, whether it's beading or yearning making and just kind of reconnecting, we always try and offer country food. It's very hard to get, especially if you live outside of Inuit Nunangat, and country food is an important part of our culture. So just at iSisters we had frozen caribou, frozen fish, and it was delicacy. So it was good, and country food is so food to us. So there's other programs at TI that may offer elements, and so being in an urban center, that's all really what we could do is just provide elements. And so our community-wide projects include like apple picking, strawberry picking, sugar bush. So it provides an opportunity to be in a more green space. The apple picking and strawberry picking kind of mimics the harvesting that we would do back home with berry picking and stuff. So we do elements, and then one of the youth programs, they just came back from Barclay, and so they take a bunch of teenagers, and I think it's West, and they do some outdoor activities, leadership training, and it's not necessarily like the traditional on-the-land programming, but there's elements of it. Those programs that I just mentioned, they're very, very popular, and so I think that just kind of illustrates how important it is to provide elements of our culture in an urban setting. We have assets. I've mentioned like we've done, it's all skills-based training. We do resume workshops. We do career cruising workshops. We try and partner up with other employers to come in. We call it a job fair, but it's really like an information session, and any time a client goes through one of our programs, then they make an appointment with one of our counselors, and then they update their resume. We have three locations at TI, so our employment counselors will go to, as our locations, we're pretty in the West End, and a lot of our clients live in Invenie or in the East End, so they'll go on Friday afternoons to ours of our location and provide one-on-one kind of employment counseling they'll reach. With some of them signing up for a program is success. Completing a program is a success, and sometimes, I don't know, the funder may think like employment is success, but there's various levels, I think, of success that leads up to employment. And so the different programs that we do offer at TI, I think, contribute to the different levels of success. So we might start off with a two-week program, or even just one day, like, if it's the first day, and then we might have repeat clients that will take the program over and over again, and you can see the confidence being built in them after, like, let's say, the second completion. And we've had clients that in the beginning couldn't finish a program, and then they would try it again, and maybe by the third time they've completed one of our programs. And so for us, that is a success, is that they are able to complete a program. And one of the things that we provide also is job start support. So if someone's already employed, then we will help them with anything to kind of keep them employed. And so if someone hasn't been out of work for a while, they will need help with bus transportation and will provide bus passes. And if they need specific equipment for the job, like steel door boots or non-slip shoes, we can provide stuff like that. So we're trying to create enough wraparound services to help people move into the labor market, but that's not necessarily our primal outcome. We just want people to be comfortable, to be confident. And then when they are ready to go into the labor force, then we want to provide them the supports for the entry into the labor market to be successful. To me, hearing the people on the second floor laugh at lunch break, and they're eating country food, and they're enjoying their space here when they recommend certain programs to their friends and family. We communicate our programs on social media, and so you can always tell a popular program with the reshares. But for us, with certain programs, we do get 100% completionary just because they're geared for success. You might know when to roll it out, or the length of time. Sometimes program length could play a factor in completion rates too. It's just knowing our clientele. Most of our programs will come with a certification of some sort, whether it is like women's or working at high aids or forklift training. With iSisters, we do have a higher succession in going into administrative fields. And so I think people see that, and even though they might not realize what their outcome is after the program, I think they certainly become more confident. And they use our employment counselors a little bit more after that, because their interest is peaked entering into the labor force. With the assets program, since I started in this role, we have had one year extensions. So it's been very hard to plan. And then we've also had influx of money at the very end of, let's say, a fiscal year. So it's very hard to be strategic in our programming. What I would like to do is have a progression. So if it starts with iSisters, then the next step would be something more about the receptionist field, because iSisters is just introduction to Microsoft Outlook and Word. So I wanted to do a progression, but because of our current financial situation, I can't necessarily plan how I'd like to plan. And currently we're in a 10-year agreement, but the money is still not available to TI. We do have an evaluation form at the end. And so it asks them about what they liked about the program and so different aspects. So about the location, because sometimes it's here, sometimes it's at another location, like it might be at our contractor's location, or it could be at Sabard or 604 Lurie. But then we also provide hospitality, so we always ask about that. And then we ask about questions about, I guess, course content. And then at the end we always ask what other fields or what other programs would they like to see. And so when we get more money or if we get more money, that's something that I would like to develop, because we've received a lot of feedback about Inuktitu Keyboarding, and that's something I would love to offer. But it depends on finances. It's easy to install on our computers, and I have it on my computer, but it's just knowing where the syllabics is because one letter could mean two or three syllabics. So yeah, I think that would be a fun course to offer. We are lucky because our current funder, ESDC, since I started we've been able to carry forward whatever money that we didn't spend and that's usually because we get an influx of money in, let's say, February. So it's unrealistic for us to develop programs and then deliver them by March 31. So they've been very flexible in terms of letting us provide them a timeline of how we want to deliver the programs. Currently, in this 10-year strategy, because it's now from assets to ICESTS because it's Aboriginal to Indigenous, it's distribution-based. So all First Nations, there's a First Nations stream, MET stream, an Inuit stream, and urban unaffiliated. And currently TI is with the Inuit stream, and so it's just navigating through those kind of tables to kind of voice that urban Inuit require a lot of support and financial support. And I think it's close to 40% of Inuit or people say, or Inuit reside outside of Inuit Nunangat. So they live in urban centers or in centers outside of Inuit Nunangat, which is Inuvialu region, Nunavut, Nunavik, and Nunatzebu. So it's just trying to, because this is a different approach of funding allocation. So it's difficult trying to communicate to your northern counterparts the struggles that urban Inuit face. I think it's a spectrum. I think at the very least, it should be, because I went to high school a long time ago and I didn't even learn anything about our north about Indigenous peoples. It wasn't until I went to university and it was a part of my elective. And so I think that it should be part of the curriculum and it should be from Indigenous perspectives. And now looking back at what I have learned in high school and university, everything is from the explorer's viewpoint. And there's nothing from whether it's First Nations, like their viewpoint of when settlers came or explorers came. I think that we're at that emerging change, I think, in the educational system. There's an Inuit post-secondary school here in Ottawa, Nunavik, and I've never attended, but I have many friends that have. And it's a place where you really get to learn your land claims. You learn about Inuit history. They gain so much confidence through performing. And I think it's a valuable tool on how to teach. Because they're really teaching history, but through Indigenous lands or Inuit lands. And I think the move towards that would be what I would consider Indigenous education. I would love to see for Inuit and the way I view how Inuit learn in the past is through observation, through respect to watching your elders, especially with hunting and stuff. But I also recognize that not everyone can learn that way. Just like, you know, some people have more visual audio. They need to write it down. So I recognize that not every Indigenous person would appreciate Indigenous indigenizing education, right? Like it all depends, right? So it could be like learning the outdoor space, or it could be, right? Or it could be talking about the biology aspect of when you're harvesting or hunting and it's a wide spectrum. But I think we are at that emerging level of approaching education in a more kind of multi-dimensional way. A lot of, you know, in Inuit, I'm not fluent. I know enough to get around and I understand more than I speak. And I think that part is, like, just confidence. But it is very important. And if you're here on a day where there's programming, then you hear a lot of Inuktitut and laughing. And so I think it's very important. And we have Inuktitut speaking staff here at the employment center. So if anyone requires assistance in Inuktitut, then we're able to assist them. So I was just at Literacy Essential Skills and Literacy kind of workshop for Indigenous learners and just talking about literacy. And then I just had to say, first of all, just to clarify, you guys are talking about it in English. Like you're not talking about literacy in Indigenous languages, which is also very important because, you know, I think people get, or some people get trapped into, you know, they're not completely fluent in English and they're not completely fluent in Inuktitut. So it's hard and if you're not proficient in either, then I think the confidence level goes down. So even if we're providing Inuktitut, let's say, keyboarding and, in a sense, kind of Inuktitut language at the same time, then even though it's not the working language of Ottawa, I think the byproduct of that would be perhaps stronger English skills as well, right? So I think Inuktitut is very important to any program that we offer at TI and we also have, like, our languages advisor and we have Inuktitut Word of the Day that gets sent out to everyone because not everyone speaks Inuktitut and not everyone here at TI is Inuk. So, and it's also a good reminder because I think even if you do speak Inuktitut, it's a good reminder that we are placing, you know, importance on Inuktitut in Ottawa. Well, TI is trying to secure PEE, so post-secondary student support program funding. Currently, Inuit students that reside in Ottawa, they have to apply to Mississauga New Credit First Nation to get funding. And over many years, TI has been requesting to INAC or ISC as Indigenous Services Canada for the transfer of the funds because we're an Inuit organization. We are invested in our community and we want our community to succeed and not saying that Mississauga New Credit First Nation doesn't, but we would put more emphasis on outreach and making sure our Inuit students are aware of all the possible funding opportunities. Even though I don't have the PEE-TRABELUS-PEE funding yet, I secured a scholarship with the Canadian Federation of University Women, the Canada chapter. And to my knowledge, it was the first kind of scholarship that was dedicated to an urban Inuk woman. And that kind of spun off into like now I have a listserv for post-secondary Inuit students that are looking for funding and I send them. It's about like over 50 people from all over and I let them know it's up to them to kind of determine which scholarship or which funding pod they're eligible for because it doesn't matter discipline or region, I just send it out. But I will help and I have helped people with their applications. I'll send reminders for certain scholarships and Mississauga's deadline and Nunavut fans deadline and so that's what we're doing. But if and when we get this PEE-TRABELUS-PEE, I would love to see an Education Support Officer where this person would touch base with the funded students to keep the lines of communication open if there's any kind of academic support that may be needed to help them kind of navigate through just being in a post-secondary institute.  And so just navigating the whole system, parents or families that have children in post-secondary schooling don't have the history of going to university or post-secondary. So it's also kind of supporting the family in terms of kind of what to expect. You know, and it depends on the institution. It might be a little bit more rigid than they're used to or it might be hard to navigate if there's no one's taking attendance in the class. It's just navigating all those kind of situations that Inuits at post-secondary institutions may face. I want to ideally fund them appropriately.  A lot of our students, they might have dependents. You know, a lot of them might have children before going to post-secondary. And so I want to be able to support them fully. It's such a barrier that it would be easy for someone to say, I'm going to quit because it's hard to see past that hump. Like it's just, you know, it could be four years of just struggle.  You can, you know, like, but I don't want it to be such a struggle. I was a parent too at school, so I know the struggle. Even though it was very first nations based, I went to the Indigenous Centre a lot. And I went there to study. It was, even though it wasn't in the need, I still felt some sort of connection. Like I felt like culturally safe. So, and that's another role for the Education Support Officer is to really encourage students to use their Indigenous resource centres at the post-secondary institutions because you might not see an immediate benefit, but if they have a computer lab, it's printing, it's just, it feels culturally safe there. So anyway, so yeah, I used the Indigenous Centre at University of Mantua quite often. Well, I currently sit on a few Indigenous Education Councils at Algonquin University of Ottawa, Queens University. And so it is just slowly providing material. I, if there's any documents that they create, I edit through an Inuit lens and I always try to incorporate the voice in whatever documents that they produce. It could be like providing artefacts. So, you know, we've provided some seal skin, like, and some like, inuit art to some of the centres to kind of, so if inuit students do use those centres, they can see kind of themselves in the Indigenous centres. Every Friday we do, or the cultural programme, we'll host Elders Tea every Friday afternoon. And then I think Elders are used, their knowledge is captured in a lot of different aspects of the programming. Last year our human resources contracted an Inukah elder and he did a series of talks on different subjects. And so that's something that we told our HR that we'd love to see. It's not like a TED talk, but it was very informative and it was very organic. It's really interesting.


Hang on a minute. I have installed the extension. It doesn't seem to be working though. Um, I'm sure it worked on my machine. Well, let's debug it together and find out what went wrong. First, let's load the source code into Chrome. I'll head to chrome colon slash slash extensions, enable developer mode in the top right and choose load extension. I'll find the folder with my code and load it in. Ah, I can see there's an error already. I can click to view the errors here on the extensions page or click service worker to inspect my background context and see exactly what's happening in the console. This looks like a typo and an easy fix. I just need to make sure the method I'm calling actually exists. Uh huh, that's how you debug an extension.


I want to go. You all right? Craig, how are you? Nice to meet you. How are you Neil? I'm good, doggy. Yeah, good, thank you. We're only upstairs so you bring me up to the box. Yeah, that's fine. See you in a bit. How are you doing here? Good. Yeah, very good. Thanks. Good. Are you all right? Biggest one for us is just training-wise.  Biggest bike. Any questions from your son? No. Do you put your stuff on my tablet? Yes. What do you know about it? It's about the nice beats. Do you know what? That's where I signed as a fighter with the music. That's where I signed. Nice beats and just nice plays. Hi. Hi. Keely, this is Keely. Hi. Thanks for being here. This is Zayna. Zayna's a fighter. He has a lot of myself. So we work with Zayna. Keely is the PA to the manager. Nice to meet you too, brother. This is Lee. Nice to meet you. Nice to meet you. Nice to meet you. Hi, nice to meet you. So these are our masters. Well, she's on Leeds and Manchester. I have to run this over there. I'm quite close. See you in a bit. See you in a bit. See you in a bit. Alright. How are you? Good. Nice to see you. Nice to see you too, Ket. Good? How's it going? Good, guys? Good to see you. How are you? Good to see you.


And we already had, like, I think it was mentioned in two or three talks already, this Academy promo writes about Weyland, we developers talk about Weyland, but Weyland is a very... It can mean different things depending on the context. And with this talk I wanted to look at not all, I don't claim exhaustiveness, but some of the meanings that the term Weyland can have. But first things first, and this is my first Academy, my first real Academy, so quick, who am I? I'm David, one of the Davids. I am a KDE developer, I joined KDE in 2019, currently I work at Plus Systems with the other David that had a talk yesterday. And I don't know how it happened, like, when I joined Plus Systems in 2020, I never did, like, Weyland stuff in Plasma, but somehow David gave me tasks and somehow I'm doing no Weyland development on Plasma, I don't know how it happened. And the real kind of reason I thought of this talk, I also read comments under news articles and on phoronics, on Reddit, and people write about Weyland, I think you're not trying, you're not, what you're writing is not correct, that's not how it works, so that's maybe the real reason for this talk. So some things that you are guaranteed to read there are like, yeah, Weyland doesn't implement something, like, it's missing this feature from X, most famously probably, I can't position my application absolutely on the screen or whatever. Weyland is also a display server like the X server was, or the most recent one I read that your application will need to support three different Weyland implementations and need to have code for everyone of those compositors, like if you run on Plasma or GNOME or with Sway, yeah, let's start with the first meaning of Weyland. First, Weyland is of course a project which develops Weyland and it's also a community. Here is a screenshot of the Weyland group on the free desktop and we can see there are some projects there and there's an IRC channel on OFTC, there's a mailing list called Weyland Devil and there of course also belong to the Weyland community, all the other Weyland developers working in other communities like the MATA developers, GNOME, the GTK developers, developing the GTK backend and so on. And of course, we are also part of the Weyland community with Plasma developers and Weyland compositor and our apps. So Weyland is about how we show things on the screen, how can an app get its UI on the screen instead of using X. And to do this, applications need to talk to each other. We have a special application called the compositor that shows things on screen and the applications talk to it. And in order for the applications to talk to each other, there needs to be a great way how to communicate. Otherwise, if they don't know how to talk to each other, it doesn't work. So Weyland is a Viya protocol like Ibus. It defines a syntax of bytes that the two applications send to each other. And yeah, it's an object oriented protocol. It means like each message, the applications send to each other identify an object and then a method on that object. We say it's a request if the application is sending the method and we call it an event if the compositor does it. But it doesn't matter. Just that it's a defined way of sending bytes across sockets to each other. But that's only the syntax. If we only have syntax, we can't do anything yet. So we also need semantics. So Weyland is also a protocol. It's the Weyland repository contains a core protocol. And with that, you can already do very much. You can show things on screen. On the right of the bullet point, I just added some Weyland debug output so it doesn't look that empty. But if you're interested, you can look it up. You can do input like mouse. The compositor sends you when you move your mouse. Or if you press the key on the keyboard. And that's very good because otherwise the applications would know that you did something, right? And it also can do clipboard and drag and drop. It's already in the core protocol. And I think that's one thing I read somewhere that somebody claimed Weyland doesn't have drag and drop or clipboard support. And I don't know where that came from because on Plasma, you can just, on Plasma Weyland, you can use your clipboard and drag and drop things. So, and Weyland repository contains even more things because Weyland is also a library and not only a protocol. There are actually two libraries, LibWeyland server and LibWeyland client. One for writing your compositor and one for writing your client. It already has a compiled version with C bindings of the protocol included. It handles all the converting your request to this binary format for sending it across the socket. And it also contains some utils for writing a server and a client like handling different queues for different objects where the requests and events are handled. It has some event support for your compositor and also how, and it has facilities to integrate it into a custom event like queues event loop. There's also a third library, LibWeyland cursor, which handles basically your X11 cursor themes, but you get like Weyland images, Weyland objects out that you can then interact with and send to your compositor to show a nice cursor on the screen. But there are even more protocols like the core protocol. It doesn't include every functionality that people then realized later that they wanted. So we have the core protocol, which we already talked about. And then we have a thing called Weyland protocols, which are these additional protocols that are like extensions to the core protocol. And Aleish will talk about it, how you create one and how people agree on that. But some interesting things of the additional protocols are XZG shell, which we use for window management, XZG activation, which we use to activate a window of another process. Tablet input is one of these protocols, or a DMA buff, so we can show things and images on screen more efficiently. And finally, we also have custom protocols in Plasma. Also, Nome has their custom protocols like that are used by our components and are not intended for your general application, like Plasma shell uses custom protocols to communicate with Quinn, to place panels, to manage your screens, and so on and so forth. But if later people think it can be useful to other applications, we can also upstream them instead of creating new ones, of course, in Weyland protocols. Some examples are layer shell, which came from WR routes, and we started using that in Plasma, and it's currently being in process of being standardized. And for example, idle notify 2, which came from us as implementation of K idle time on Weyland, and it tells you when the user is not using the computer and people thought that it is useful for your general application. So there's also, it even wasn't even proposed by us. Simon there from WR routes proposed it to standardize the protocol upstream, so it's quite cool. Now we can look at this beautiful picture and take a sip of water. So doing this talk and thinking about what to talk about, I had a realization that maybe in the end I was wrong when reading and being angry reading all these comments, because what the user sees is if they look into the session in STDM, it says Plasma X11 and Plasma Weyland. So for the user, it doesn't matter everything I just talked about. Weyland is what they see. It's the entire suit of implementations and interactions between them. It's Plasma, it's Quinn, it's a cute Weyland client, it's GDK Weyland, it's some native Weyland and all the interactions between them, and if something goes wrong, Weyland is at fault and I can't be angry about it. I think nobody can because we don't expect our users to be that technical. In an ideal world, we wouldn't have this switcher at all, like there would just be Plasma and the underlying technology should not matter to the user, but certainly we are in there. But I think when reading these comments, I shouldn't be angry, but maybe I should be a little bit angry. Because it's always a matter of how you phrase it, right? But if someone is angry, then there's a problem that we need to solve and it's our task to make Weyland as good and even better than the X session. And I think that it's kind of a conclusion already of my talk that we have to keep that in mind and with that, I want to revisit some two of the things I showed in the beginning of these comments that I read. So the one that applications need to support three different implementations, like one or even more for every compositor. I think that's not true because first the protocols are standardized and most, so everybody has to implement the core protocol. It's standard. The additional protocols are standard and most of them are implemented by most compositors. Mine, Modulu, some things. And all the implementations like Qrin, Matter, Qt, GTK, they try to follow the standard as it's written. And if a developer discovers there's divergence in implementation and it sometimes can cause bugs because the events come in different orders or because it's not defined in which way to send them, then people go to the IRC channel or to the GitLab file issue and then people talk, discuss and we find a conclusion what it should be, the correct thing to do. And so we reduce this need for, there's no need because everybody tries to do it the best way there is and correct ambiguities. Also, I think it was with a screen sharing or something that the people said, or for screenshots that you need to support the three different ways. But I think in the future, or in general, it's also not true because if somebody or two different people have similar custom protocols to a thing, then there will be a process and people try to agree on a common one and upstream that. Or even maybe valent is not the correct place for the protocol. Like maybe it's better suited to the pedestal part like screenshots or screen sharing. And of course we use Qt as a toolkit and that also reduces the need to have some of these. Like when I said not every compositor implements every protocol, for example XDG decoration is the most famous one and so if you use server side or client side decorations and Qt handles that for you and if you're writing a native app for some reason, like valent native, there's lip decor which handles that for you so you don't need to care if your compositor implements the protocol or not. The second thing is valent doesn't support X, Y, and C like valent in the general sense and that can of course be true but it's not like we say we want to have your session be pro. Your use case is not useful but it will not be that the valent developers will say, yeah, you can't do that. Let's do it like you say. We want to understand first the use case because it's maybe possible in a different kind of way or you can give some kind of more data to the compositor so it can fulfill your need so it's not like blindly porting the X protocol to valent protocol and then having the same thing again but understanding the use case and finding a good solution for the missing use case and then we can create a custom protocol if it's just something that we're missing maybe between Plasma and Quinn or it's for every application we can create a standard protocol and if it's a problem people will have out from other communities or maybe again maybe a portal is the correct place but people will try to find a solution if there's really a problem. Then we can implement it in Qtvalent client, in Quinn, in Plasma, wherever maybe some a bit of custom code in the app and then everyone is happy and that's a really nice thing and now without break it's not a late turn and he will talk about us how you do valent protocols.


The storyboard is one of the most difficult exercises in the design sprint. In this video we're going to show you exactly how to do it. The storyboard video you're about to watch right now is from our design sprint online course. So we're just giving you a free preview of inside the design sprint online course and we're going to show you exactly how to create the storyboard. If you're interested about this course, if you're interested in running your own design sprints down below in the description you'll see a link to a one and a half hour web class on how to run and sell design sprints. You should definitely check that out afterwards if you're interested. While watching this video if you have any other questions around storyboarding or around design sprints make sure you let us know in the comments. Hope you like this video. We're up to the final exercise in the whole group workshop part of the sprint, the very end of the second day, the storyboard. So this is going to look something like this with you as a facilitator or we also suggest and we do here at AJ & Smart often have a second person actually doing the drawing while the facilitator is then free to kind of moderate the group, moderate the discussion and really guide what's happening and then they don't have to have their back to everyone while they're drawing. So if you have someone in the group that enjoys drawing, likes drawing can sometimes be tricky to actually get someone to volunteer but try and get someone to just be the scribe of the artist collecting what everyone's comments and making the actual storyboard. So the actual exercise we break into two parts to make their basically give a sense of achievement and help you feel like you're really getting through the whole storyboard by doing it in a few passes, a few phases. So part one is first drawing eight. We usually draw eight boxes or cells on the whiteboard. You can have even a couple of extra ones if you want but we're going to now try and translate those six post-it notes from the user test flow into really what might happen on each screen or at each real step along the way. So often a step on a post-it note might translate into more than one screen so we give ourselves a few extras here. Then place those six post-it notes inside the boxes and you can leave a few spare ones if you think maybe this post-it note might take up a bit more space but you can always move them around so don't stress about this. Place the post-it notes inside and then this is a really key step is looking back around the room where you should still have the concepts all around you including the winning concept the one that you actually chose to go ahead with and see if you can find drawings and parts of drawings that you can actually reuse that maybe already have good illustrations of something that's in one of these post-it notes and the trick here is that you don't only have to be limited to the winning concept there might be a drawing in a concept that wasn't chosen but that's still a good representation of the idea that's going on in this screen for example a login screen might be the same in different things or a great drawing of a graph or a chart you can just pull it out of another concept so start getting the group to find the drawings cut them out and find the things that really might already work and save us some time not having to draw them all over again in the storyboard and stick them up onto the white board so you've already starting to get half the job done already before you've even had to draw anything new so this is all about avoiding unnecessary efforts by using what's already there and it also actually helps give your team the team members a sense of achievement and validation when they've drawn something even if it didn't get chosen that it's now being used in the final storyboard so it can really help every everyone feel included and invested in the the final product the final prototype the purpose the whole purpose of the storyboard is really to leave no open questions really get all the detail out now now that we've got the basic steps that we did in the user test flow we now want to get all the detail out so that the next day when the prototype is really sit down to build that prototype they don't have to answer anything or look anything up or get some information that they don't have already they can just build the prototype so this is really important to get all the detail in and it's really important also even though you're wanting to add detail to the high level parts of the concept that we haven't really fleshed out yet be very careful not to add any new ideas here or add anything that's unnecessary like if you're not testing the login flow for the product you probably don't need to draw and build a login screen you can just skip that and pretend it's there so don't add things that the prototypes will have to make more effort to design if it's not an important part of your test no brand new ideas and nothing unnecessary now you can go into part two of the storyboard where you fill out the rest and draw the rest so filling in the missing pieces by drawing around them or taking a drawing that's already there and really building on it and using that as a base so it's a great idea to start with the first cell the first box that's often a simple one like a google page someone googling to find out about a laundry service or maybe it's an email where someone's told about a new product or an add on facebook it's usually something that you've seen before and you can really just quickly draw again then it's a great idea to go to the very last box in the last cell and draw what's there and that also might be quite simple it might be a final clicking to buy something or confirmation or sharing something with a friend that final step that's confirming that the user might actually use subscribe or share that service with someone and that's usually something that you might know what that looks like as well so doing those first two helps the team feel a sense that they're actually getting somewhere they're actually moving along and they're already filling out those two simple cells and then it's a lot easier to see what happens in between as well then finish drawing the rest and there might be one or two screens in here that have most of the heavy stuff in them the the key screens we call them the ones that are really showing what the product is so in our example it might be the marketing page and then the checkout page so these ones might take a little bit more time try and keep your team time boxed using the suggested timings in our your facilitators checklist that you got with this class and really kind of keep them time boxed and maybe use some time boxes that are a bit shorter than what you hope for so that you can extend them a little bit and give them give the your team a bit of extra time but keep them time boxed so they really keep moving fast another great tip for this storyboarding activity which can sometimes be stressful and keeping the whole team really engaged can be really tricky thing to do because people start debating and discussing particular features and ideas is giving people side tasks so if one or two people start really debating what might happen on a particular screen or what copy needs to go there or what order things should go in you could give them a marker and say great you two work on that screen while we move on with the others and then we'll come back and then we'll get a lot more done so this can help people it's hard to keep everyone just paying attention to one thing for a long period of time so giving people those jobs or telling like other side task examples are go and look up some copy that you might have on your marketing page already or sit down and write some copy and then come back to us this really helps get more done and keep everyone engaged and that feeling of investment in what's going on as well and another great tip is delegating the drawing like I said before find someone in the group that can do the actual drawing for you so that you can be facing the group and not having to have your back to them and really watching for things like people getting disengaged or having debates on the side and you can then allocate them side tasks and things like that it can be really tricky to keep the group engaged and active and it's a really important thing to do for this very last exercise where it's really the final thing that that group will do together on this day so really keeping people motivated engaged and excited and invested in what they're doing is super important to for you as a facilitator and for the team to have that sense of achievement together at the end so there you go that's the storyboard obviously there's a lot of other exercises around it if you've any other questions let us know in the comments and like I said earlier down below you can see a link in the description to a one and a half hour web class on how to run and sell your own design sprints if that's what you're interested in running them yourself don't forget we have a weekly podcast called the product breakfast club podcast on all podcasting apps we have daily blogs on instagram on our ajn smart channel we also have a newsletter you can check out down below which is a bi-weekly product innovation newsletter where you can get the most up-to-date product design news all the kind of industry stuff that you might want to know that comes to your email every two weeks no spam no bullshit finally we also have a super popular facebook group called innovation hackers where designers all around the world and innovation specialists all around the world come to share their links come to ask questions and come to share their stories about their work in product design so definitely check that out have a great one bye bye


And here's another question from Vazjan. Hi, how to connect a motor controller SMEACX144 via CAN bus to a STM Nucleo L476RG board to read the parameters like RPM, temperature, currents and so on? Okay, hello. First we have to assume that the controller is an external device that communicates over a CAN bus. It supports the CAN Open protocol via the process data objects. So if you want to connect it to the Nucleo board, you need to equip the Nucleo board with a CAN transceiver, which would be the extra connection because the CAN transceivers are not naturally implemented on the Nucleos. This is the hardware part. The software part means that you need to implement the CAN Open protocol on the STM32 microcontroller. There exist options that you can buy or obtain for free from the web. And you will need on top to understand the PDO objects and decode them or ask the motor controller to get this data. So you need to assemble all these three parts together to be able to obtain this task.


You don't want to contradict or correct your husband in public and same same with husbands You don't want to ever demean your spouse to your children if you don't honor your children's parent Your children will not honor their parent either and remember It's still Riba or backbiting to talk about your spouse in a way that he or she Wouldn't like instead of listening to those people who advise don't let marriage change you Amend their words to marriage should only change you for the better make Allah Subh'anaHu Wa Ta'ala your ultimate destination


I just want to give a heads up that this is a re-upload from the original 1.2 video that has now been privated. Now I made a mistake later on in the video, so if you've already seen this video in the past, you can just move on. However, for the rest of you, make sure you stick around. In episode 1.2, you will understand what public and private means, which are access modifiers. And you also know when they are used. Hello guys, it is CryptoGround here. Welcome back to another Unity Idolgate tutorial video. This is episode 1.2. This is the 2021 edition. If you guys learned something new, if you enjoyed this video, make sure you smash the like button. Subscribe to my channel if you're new and turn on the bell for future notifications of videos and live streams. Anyways, let's get on with it. So today, we're going to be using the controller and our data script that we created in the previous episode. So you probably have noticed that I've been using public for pretty much everything. Our classes, our variables are in our methods here. What does that actually mean? What are the differences? First off, if you want a detailed explanation, you should check out my, you should check out my access modifiers crash course. Links will be in the description below. However, but basically what public means is that you can access any of these variables in any class. That's pretty much what it means. Now, if we made this private, then that means we can't really access it. And it's only limited to this class here. It goes the same thing with classes as well. You can't access another class within a namespace, which is like something that goes beyond classes, which I also have a video on that as well. And the same thing for methods as well. So if you made, so if you made this private void start method, then you cannot call this method anywhere else except for in here. And yes, this will also be called by mono behavior. So it'll work just fine. So let's make our flash variable private. So if we'd made this private, we would see some errors here. None in data, but in our controller here for us, we would get an error saying that we cannot access a private field flash here. Basically, we cannot access a private variable in here. That's pretty much when you know you need to make this a public. Okay. If you need to access a variable in other scripts, then you need to make it public. However, if you were to make this text private here, this flash test here, you can make this private here. But now the issue is that Unity won't be able to access this here. One solution to this is by adding an attribute called serialized field. So it's private. You cannot access it in other scripts, but you can also assign it in Unity still. So if we go back to Unity here and check out our scripts here, you can see that we could still access our texts here. However, if we were to get rid of this serialized field here, as this is still private, it should disappear. Yep, there it goes. That's gone. So now if we made this public here, you could see that it's still defined. It's just that we can now see it. So you can either leave it as public or if you don't want to access it in other scripts, we can leave it as serialized field and make this private a private text. Okay. So that's your choice. Either one of these works, but it's it's your again, it's your choice. Now the same thing here with data. We can make this a serialized field and a private. However, since this is a controller script here, we're going to most likely be accessing data in different scripts. So we want to leave this as public. So for methods now, we can't just do serialized field here and we can make this private. So in our case, we don't want it. We don't want to call start or update any other script. It doesn't really make any sense. So we're going to make these two privates and now generate flash must be public. However, if we do private, so currently we have our on click set to generate flash. Okay. So if we take a look at this drop down here, you could see generate flash is in this list. So if we make this a private method, not only queen, not accessed as in any other script, but also we cannot reselect it. So right now it's still selected because it's the same thing as making a text private. It will still, it will remain there. However, once you bring it back, you'll be able to actually see it there. But if it's private, you can't change it. It's hidden, but it's still there. So now the same thing for generate flash here. If we go to the drop down, you can see it's not there. So now if we just select another run a method, you can't go back to it. So we're going to keep generate flash as public. So then we can have our generate flash selected in our increment button. You can either just keep it all public just to keep it simple. But if you want to just keep things minimal and don't want to have other things access certain methods or variables, you can mess with these settings and just make sure you keep an eye on it. Honestly, so I know those are really short episode, but I hope you guys learned something new and I hope it was really helpful and if it made sense and I really hope it made sense as well. Be sure to smash that like button, subscribe to my channel if you're new and turn on the bell for future notifications of videos and live streams. Anyways, I hope you guys have a great day night. I'll catch you guys in the next video, which will be episode 1.3 and we will be explaining all the different types of variables that we can use. Anyways, catch you guys in the next one. Peace.


Hello, beautiful souls. This is Christy with Art of Awakening. Thank you for watching and much love to you today. And this is just a quick reading. It's April 19th, 2019, and it is a full moon. I know I just did a full moon reading for the coming week, but this is just a daily reading and, you know, really pertinent to today or whatever day you happen to land here, if you land here at a different time, different time in the future.  The painting here is one that just happened to be on my table. It's a painting that I'm going to be shipping out pretty soon here. That's why it's here. But just kind of right off the bat, horse, I'm getting freedom here. A lot of freedom. It might be a really good time to get outside, get outside and move a little bit and just enjoy being in your body today. This is a really, like, this is like big guidance coming in. Just enjoy the body. Enjoy stretching. Enjoy what it feels like to breathe. Enjoy what it feels like to be on the planet today. I'm pulling cards from my Spirit Animal Awareness Deck. And this is what the cover looks like here. That there. Just leave it out there. Okay, so vulture is the first one. And I I always think of purification when I look at vulture.  And I just feel like this is a real period of purification that we are in. You know, root chakra work would be a really good thing to do if you are feeling unsettled at all because there is a lot of unsettled energy around like the Notre Dame you know, incidents and just you know, it's it's just I'm kind of feeling like there may be some more shake-ups in store for us and let's just have you know, just just like not freak out when these things happen when we have a really strong root chakra then we can just sort of like the weevils wobble if you're old enough to remember weevils. There are these little toys that that these little toy people that were like eggs and they would just sort of pop back up if they were knocked down and that's what we need to do. I mean if if you can just imagine yourself like a little rubber duck and you know, if you get pulled under the waves you pop right back up so any kind of root chakra work would be good and again also grounding into the physical body really getting into being in in the body is is going to be really really helpful both today and in the weeks and months ahead so exercise feed yourself well sea lion again, I mean the first thing coming up for sea lion even on the card is grace under pressure and we're looking at I mean they can go down they can dive way way deep down and really withstand a lot of pressure of this animal and and it has to do with breath control so again, this is part of like being in the body and really using the breath to maintain a sense of peace and calm regardless of what's going on around us and I'm sort of getting to the feeling that this is kind of a reading that is more general than just today, but it could be you know today too, but I'm feeling like today is any day, right? Today is any day. It's the present moment and if you feel like you're behind at all if you're feeling like like especially in regards to the physical body if like you haven't been really exercising or much lately or you know for a long time there's no like behind you can't don't don't think of it as as being behind oh I'm a thought of out of shape think of it as I love my body and I'm going to do the best thing for my body today and whatever that is and that could be taking a nap it could be going up for a walk in the sunshine you know it could actually be going to the gym and with lifting weights but don't like listen to your body don't listen to what your mind thinks your body should do right? You're because your mind's going to go and tell you oh I need to go to the gym and lift a bazillion weights and you know hop in the pool and swim like five miles and like your mind is going to be like oh you're not good enough and you got to do this right but your body will tell you exactly what is needed you know what what the next best step is in a way that is both invigorating and strengthening and gentle enough that you're not going to hurt yourself okay and last one is mouse again I'm getting just kind of behind yourself today be kind to yourself look at the mouse he's so vulnerable and yet he can accomplish so much but not if he's like you know so scared he can't come out of his hole because he's got to be able to move around again there's this movement idea getting out moving the body you know I'm getting a lot of movement from mouse but in a kind way so I think the overall message here is let's you know this is a very good time right now to focus on the physical body and enjoying it enjoying being good to it and feeling what it feels like the empowering things that can happen when we start respecting and honoring and loving and enjoying the body and everything that it can do really appreciating being grateful for the body you know spend a little time today saying thank you to your body because it's an amazing thing it's really what allows us to take our spiritual purpose and do something with it right and make an impact and you know it's it allows us to experiment and to create so so be kind to the body listen to it honor it and have fun have fun with it enjoy so that's today's reading hope you've enjoyed it and as always I really appreciate and I'm so thankful for your views and your comments especially if you've liked this video please like it and thank you so much to those who have reached out to me who have ordered sessions that really means a lot and it also helps to keep the channel going so have a lovely lovely full moon and I will catch you again later