Hi guys, this is Jason Zach from Nathaniel School of Music. In this lesson we are going to learn probably one of your favorite songs by Brian Adams if you've heard it already. If you've not, it's going to be an exciting piano lesson for all of you watching it to improve your hand independence, to understand the theory of chords which are not really major or minor. We are going to look at the suspended chords used really amazingly well in this song and a lot of other stuff along the way, a good fingering pattern to improve your strength and of course the hand coordination no doubt in different ways with accents and with pulses and so on. So with this lesson there will also be notation, there will be my handwritten notes as well available for you on Patreon so do consider heading over to our Patreon page and for a $5 subscription you will get the notes for this lesson and pretty much everything else we will ever do in the future and have done in the past. And before we get cracking it will be great if you could hit that subscribe button somewhere there I am sure you can see it, hit it right now and there is a bell icon as well, hit that as well for regular notifications which will give you updates whenever our channel releases a performance, a riff or a lesson or a song tutorial and whatever else we would end up doing on Nathaniel's school's YouTube channel. So let's start. So the song I am going to first show you the two chords which are used in this song at least in the main hook or the main head of the song where he goes So that part we are going to learn and we are going to develop a lot of stuff to improve your hand independence and fingering along the way. So the first chord would be a D shape but the way it is played in the song is it goes D sus 2.  A sus 2 chord will have the root, the perfect fifth which is D A just like a major or a minor chord. So if you take D major take D minor there we go. So a sus chord will have the fifth but it will not have the third neither the major third nor the minor third. Instead the third will get changed to the major second which is just next to the root here. You can also call it as Sa Re in Indian music we say Re.  So sus 2 sus 4 and in this song by Brian Adams there's also the third the major third in this case which will be used in tandem with the sus 2 and the sus 4 to create this beautiful riff for this nice set of arpeggio phrasing. So with these chords you also need to understand that you can invert those chords. So if you take the suspended chord which is D E A you can then invert it by going D A D or you can do A D E. So in the song Brian Adams uses that inversion which is an inversion of the sus 2 the reason I still call it a D sus 2 is because D would be in your bass it could also be looked at as an A sus 4 but then A is not in the bass right. So a sus 2 a sus 4 are related to each other they are inversions of each other so just to walk you through D sus 2 is the same or has the same notes as A sus 4 and there's one more very interesting inversion what we call as the quartal voicing you do D E A and then if you start with E you will get E A D this is a beautiful voicing there are videos of this which we've talked about on YouTube to talk about quartal chords and a lot of the other not so normal or not so commonly used chords you have in music. So we are using this voicing and building the arpeggio and the arpeggio phrase is very interesting because you might think it's a triplet pattern which is something like this but at the end of the triplet pattern we go 1 2 3 1 2 3 1 2 1 2 so if you brush up your maths or if you already know this maths it will be 4 3's or 4 3 patterns 4 3's are 12 3 1 2 3 1 2 3 1 2 3 so 3's are over or the triplets are over which is why a lot of the students who I've taught over the years even some of my bandmates call this a triplet pattern for some reason and I try to correct them with students you can with bandmates sometimes it's a bit tricky and some of you may know why so you go 1 2 3 1 2 3 1 2 3 1 2 3 1 2 1 2 so the fact that there are two hits or groups of two at the end of the cycle does not make it a triplet phrase it makes it an accented semi-quaver phrase so that would end up being 1 2 3 1 2 3 1 2 3 1 2 1 2 so if you add that up 3 4's are 12 plus 4 equals to 16 so 16 semi-quavers or 16 16th notes will make up a bar of 4 beats so if I count that for you 1 2 3 4 1 2 3 right you can count it it's it's very much a 4 by 4 song but the accents or the phrasing of the arpeggio is not normal in the sense it's not one two three it could have so easily been like this this doesn't make it unique and interesting right two three rather boring one so what we have in the song is one two one two you can count it in a lot of ways but I guess the better way is to count it as these accented groupings 1 2 3 1 2 3 1 2 3 1 2 3 and in India we have phrases which are used for our rhythmic language especially in south India we have a language called conical which essentially gives you rhythmic syllables or words which don't become tongue twisters like saying one two three one two three one two three which at least I can't say so we have a we have a couple of phrases so for three you can say ta ki ta so I'd like you to try that out I'd like you to try saying it before you actually played and keep your pianos out while you're learning this lesson it will really help and stay around till the end of the video don't don't leave it short in midway because the theory stuff is now but the actual playing and the technicality of the piano is coming up very soon so stick around get your pianos out if you wish so the way I would count that is before I even start I would say ta ki ta ta ki ta ta ta ki ta ta ka junu you can say ta ka junu or ta ka dimi at the end or ta ka ta ka you can say ta ka which is two ta ka or ta ka dimi if you want to visualize that as four or ta ka junu is also works I guess so it'll go something like ta ki ta ta ki ta ta ki ta ta ki ta ta ka junu ta ki ta ta and if you see my snapping it's going two three four ta ki ta ta ta ki ta ta ki ta ta ka junu ta ki ta ta ki ta ta ta ki ta ta ka dimi ta ki ta ta ta so once you get that phrasing in your head it'll be easy to accentuate the arpeggio because when you play music like this it's not you shouldn't be counting you should be rather moving your head to the eventual pulse of the song which ultimately you want your listeners or your audience or your fans to also do so if you are not able to do that while you play the music how will they do it how will anyone you're playing for be be doing it so you have to move your body to the pulse with respect to the song so one two three one two three one two three or ta ki ta ta ki ta ta ki ta ta ki ta ta ka junu ta ki ta ta ki ta ta ki ta ta ki ta ta da dimi ta now let me walk you through the notes your left hand is going to just hold D for now and there are two chords in this part of the song you could say this is the chorus of the song where right after he sings those were the best days of my life and that's the riff which will succeed that after best days of my life so you go one two three what's the first chord it's D suspended two start starting with this inversion A D E and starting from the top so I would like to say high note middle note low note of the arpeggio high middle low that's it and then we drift towards the normal D major chord in second inversion which I start with that F sharp there so so two threes one two three one two three one two three now that's a D suspended four in an inversion so sus two major sus four major so you're doing sus two for a triplet or group of three major for another group of three suspended four for another set of three then a major chord for a set of three let's do that first okay and the very ending the takajuna will be that's e a f sharp a that would be a kind of a broken chord but not all the notes of the chord so sus two major sus four major sus two major we don't have time to play all the notes of the sus two and the major so instead we do that's the last four hits so putting it all together slowly even slower play along with me try and try to move your head along with the pulse one as you can see my head is not going it's not going with the accents it's going with the pulse which is the body's natural response even if you now go to Spotify and listen to the song your head is going to move like that so you when you play the piano your head should also move like that then you're well you could argue that you're feeling the music or you're in the zone so to speak move your head or you can even tap your foot but the thing for us piano players is one foot is generally on the sustain pedal so it makes more sense to move your head or move your body but you could also consider moving your foot now what can start happening is in the left hand we can bring out the pulse or we can bring out the accent i'm going to talk about that really soon but before we do the left hand stuff let's also learn the next chord so it's not just D major or the D shape it's the next chord would be copy paste carbon copy but from A so it'll that that'll be A sus 2 A major A sus 4 A major A sus 2 major okay sus 2 major sus 4 major 2 major it's almost the same fingers as well see you do your thumb index in middle ring for the black note pinky for the next white note so you're giving three fingers the opportunity to play those three notes so so that's the A and it toggles D oh yeah A back in the summer of D little slow and A i'm also tempted to fool around with the accents a bit because now that you know the chords you don't have to just do three three three four you can do other sorts of things maybe we'll do another lesson just on accents so do stay tuned to our channel and there's a bell also for regular notifications which it would be great if you could hit that as well so you won't miss a lesson now coming to the left hand the left hand is going to do the roots of the chords pretty much just the roots of your two chords i like to play them as octaves so that's D D and A A D D A A so what we will now do is play these chords or play the roots first off i think this will be easier for you is to hit on the accent hit point so if it's one two three one two three one two three one two three one two one two wherever you see the number one or feel the number one you need to execute that and hit only that number in the left hand or if you're counting only the thas you would need to play in the left hand and what note do we play the root of the chord let's let's do that slowly so see what's happening here at every one at every accent hit point as we call it the accented note which has that accent sign and music notation you're going to play the roots of the chord makes the song a lot more busier and in some cases also a bit more chaotic like for instance if this was not a D major chord and if it was a D minor chord the accent is used a lot in film music in scores in themes to just make it a bit more chaotic and sometimes a bit more epic and to add that drama to the music so accents number one and if you'd like you can play the accents by toggling as well you don't have to just do root and octave D you can even combine you can combine a combo or combo the root of the chord with its octave so x and all on the accents for now that's another workout more for the mind because your right hand has to keep the the riff the pumping right which is already a challenge so the left hand now has to think of the accents and you could play it DD or you could do toggle whatever works for you let's do that the accents with D and A and then let's move into the last left hand pattern which is the pulse going to a summer of 69 oh yeah all accents with some toggling there we go so check out the notes or the notation as well it'll help you out to learn the lesson you could also watch along finish the video and the notes are there so you could give it a couple of weeks if you're not getting this right now it's always fine to digest the information a bit more so the last variation for this particular tutorial would be to try and hold the pulse which is essentially what your head should have been doing all this time on the roots of the chord for now three four so irrespective of what your accent is you'd need to play the pulse so a good way to start would be say the konokol or the sedhi summer of 69 phrase do not play it say it and be able to hold the pulse then i feel you're going to get the right hand almost instantaneously you could actually start with maybe one e and a two e and a three and a four e and a one e and a two e dividing by four with your voice and then if you want say the konokol word which is now once you are done with that remember the phrase or maybe you would have got it written down in your books you can say say the thas a bit more with a higher pitch with more emphasis so you could also say thaa only loud and the other guitars can be whispered maybe that will now slowly but surely help us to get our right hand to go we're trying our best or my suggestion to you is to try and make your hand to be an extension of your voice which is an extension of what your brain wants to do in any case so you need that portal to transfer from your mind to your fingers one way people try to bypass that is to look at this hand look at this hand and then get the sync points between the two hands now it'll work for this song eventually but it'll be a fairly rigorous process if you ask me and then it may not work for the next song the advantage of doing it this way which i recommend it is you know by accenting by getting that phrase going with your voice and then executing it on the piano you're getting kind of thick skin to help you through the next song as well so the next song which might have some other random accented phrase will get a lot more easier than this so i always like to learn music on the piano so that there is some form of exponential growth which i see as i go forward so i would always recommend spend time understanding what you have to do spend time digesting the theory write it down in your book before you play and then execute and keep repeating don't just do it once and pack it up you have to keep repeating it till you really nail this stuff right guys so that was summer of 69 let's have a quick recap what have we done first we looked at the theory of these suspended chords sus 2 and sus 4 how they are different from major and minor then we looked at the accents used in summer of 69 we learned it on two chords the d chord and the a chord we figured out a nice arpeggio pattern in the right hand high middle low high middle low high middle low high middle low high low high low and after that we had two left hand variations one was to bring out the accents and the other was to bring out the pulse which is the natural response of the body to well played music and the icing on the cake would be if you can change instantly from pulse to accent that's the accent this the pulse accent if you're more ambitious you could try and get this done pulse you could also do eighth note pulse makes it more like a rock song which it is so that's your eighth note pulse which is like one and two and three and four and one two three that's the quarter note pulse that's the natural pulse acts and pulse nothing changed at all in the right hand it was only the left hand so that's how you bring out excitement and in a way make the song longer I guess then what it actually is you can play the same riff for I don't know how long you can go on and on because it's not it's not that monotonous anymore people are not only hearing the tune they're hearing what you're doing with the tune or collab how you're collaborating with the tune with the other hand right guys that's about the lesson hope you found the tutorial useful have fun playing along with summer of 69 and let us know in the comments what you thought about the lesson and do give us your suggestions it's your suggestions which are pretty much making our content on the channel so if you have anything you'd like to learn any topic do shoot that in the comments and we'll be happy to get that done for you and do consider being our patron on patreon.com slash Jason Zach where for a five dollar subscription you will get all my handwritten notes as well as the staff notation midi files backing tracks and a lot of other things and if you bump up your tire you'll also get access to to a lot of personalized workshops where you can add your own questions to it you can discuss your doubts and so on so there are lots of tires out there on patreon which might help you and if you'd like a more structured course at Nathaniel school of music you can consider going to nathanielschool.com and checking out either our six month semester programs where you learn with our amazing faculty at our school we have branches in Bangalore there's also an online way of learning so wherever you are in the world you can still learn and we also have video courses where if you are in a completely different time zone you can access some of our video content as well right thanks a ton again this is Jason Zach from Nathaniel School of Music cheers and catch you in the next one


Hey guys so we on a new segment talk of the town today we have a special guest Yifani How you doing? I'm good how are you? I'm doing well Okay so um so tell us a little bit about the history of your name like why did you pick that to be your artist name? Oh man um so my name is Yifani Chuku it means nothing is impossible with God and um I see that a lot of artists y'all like tend to pick a gangster or an image that they would like to portray and then they add that into the artist's tree or they raps and whatnot when most real motherfuckers come out as themselves you know what I'm saying like that's who I portray I portray myself and iffy baby everybody think it's iffy but it's like no I'm not iffy my name is Yifani Chuku it means this but and for sure you know what I'm saying it's iffy yeah I can get iffy So does that get annoying and get complicated like when you meet a new artist? It does it does I said yeah so you feel like the music makes up for all that though? Yeah for sure okay all right so tell us like how you got into music um I knew a couple people already in the industry and um it just fell on my lap so I ended up talking to a couple dudes and they sent me to Atlanta and Miami and now we're in New York and it just you know it started just falling along with the plans all right so do you remember that first studio session when you record that first song? Oh yeah the first studio was crazy um that it was um it was out Baltimore shout out to KP he did some things early in his career with um some niggas but whatever that studio was super crazy it was uh uh Sony 800 so that's the same uh microphone that JZ used and it was like a really big studio it was really cool okay yeah so that was your first studio session ever? I mean my first studio session when trying to take it.  Nah I built my confidence enough now where I'm like like I got studios they where I go so even like last night I was in the studio so I just I get in I got a process that I just you know I do and I just just stick to my process and just keep it push okay okay so what's that process like let us know like what is it like in a studio like how do you get in in your bag to record?


All right, it's already eight o'clock. If other people join, fantastic. Either way, let's go ahead and dig into this. Sure. The reason why we... Where are we keeping notes? Oh, there is a cloud events SDK design proposal, Google Doc, which I'm gonna paste into the chat room right here. I didn't know if you were gonna use the normal one. Yeah, I'm not sure if I have, I guess I could add a whole bunch of suggestions on to it, but I think this is fine for now. Okay, cool. And we were just joined by Carol. Hi, Carol. Hi, everyone. It's Carl here. Carl, great to meet you. We're just kicking it off right now. And I just pasted the Google Doc where we're putting notes, ideas, everything into. Yeah, yeah, I see it's being abated life right now. Yep, that's right. Cool. So to start from the beginning, the reason why we're doing this is because we came out with this great specification for coming up with a common envelope for event data. And it's gotten a lot of attention already, but we need to make it easier for people to use and a natural next step is usually to create some SDKs. When polling the serverless working group and the cloud events group, it seemed like a whole bunch of people were already making SDKs. They were just going off and kind of doing it in isolation.  And maybe we can collaborate on these things together. So that's the premise for all this, the why. I think we should go ahead and do a quick round of intros. So, anyone want to go first? Sure, this is Mark Geek, I'm with VMware. I've been involved in the serverless working group since it started and cloud events. And I am the lead head honcho of dispatch, which is an open source serverless framework that sits above other fases. Great. Maybe I'll jump in real quick. My name is Austin Collins. I'm the author of a piece of software called the serverless framework, pretty popular open source project and also the CEO and founder of a company called serverless Inc. Been involved for the serverless working group for a long time as well. And, you know, our company works on vendor agnostic abstractions to help people build serverless applications across any serverless infrastructure provider. We care a lot about standardizing some of the popular concepts within serverless architectures because we believe a lot in vendor choice. We want to make it easier for all developers to use serverless infrastructure across providers without having to kind of get familiar with all the platform quirks, become respective platform experts. They should just have this common experience for deploying, you know, serverless functions or using other serverless infrastructure across providers. And that's one of our big goals. That's why we are big fans of cloud events and some of the other things that we're just starting to talk about now in the serverless working group, like coming up with standard function signatures and whatnot. Yeah, and that's me. All right, I could go next. So I'm Carl, I'm also with VMware and I also work on project dispatch like Mark. I was involved in the event's work for dispatch and I actually implemented the first version of cloud events in dispatch. What I'm looking forward to is SDK helping with, first of all, tracking the spec of course to be able to, you know, version the SDK with the spec. So I don't have to follow the changes. Well, I will have to follow the changes anyway, but to be able to pick up the proper version SDK and yes, make it easier, make my life easier as a developer, consuming, producing and dealing with cloud events but I'm really happy that this thing came alive. Me too. I can go next. My name is Mathias Wessendorf, I'm with Red Hat. Today I have two co-workers here because we are at a face-to-face meeting. We started looking at cloud events from messaging perspective. One of the motivations was so that in the Java Enterprise ecosystem, there's the Micro Profile Initiative and they're going to start a new messaging specification that's not JMS. And one of the idea goes, there was as well that for eventing, it could be modeled after the concept of cloud events. Yeah, when we were digging into this, we were starting to play with some API and stuff like that. So that's why we are very happy that we can participate here and I added some proposal already to this document that we currently all staring at. Yeah, I saw that, great work. Thank you. Was that everyone? Probably not, I joined late. Klaus here. Hey Klaus. My name is Klaus Dysen, I work for SAP. We are contributing to Q-plus and I'm currently starting to play around with cloud events for Q-plus and of course I am. Yeah, I suppose everybody playing with cloud events right now is starting with the same thing. So somehow working with those attributes we defined so far and so on. And maybe that's quite repetitive. So, yeah, I would be happy to see that if some common libraries somehow evolve. Great. Howdy, this is Scott from, Scott Nichols from Google. I'm still ramping up, so I'm here to listen. Great to have you Scott. What team are you on? What product are you focused on over at Google? Sister team to App Engine. Yeah, cool, thanks for joining. Is that everyone? Mike Roberts, did you go already? Hey Austin, no I didn't. Yeah, hi everybody. I haven't been on any of these calls before but I've been following the group for a while. And I bumped into a couple of the folks from Google two weeks ago when I was over in Velocity. So I thought I'd finally join in and just lurk on the sidelines. All right, great to have you. I think that's everybody. Let's go ahead and jump into the agenda here. And I'm wondering if anyone has feedback on this agenda. Here's kind of how I thought this could work. We list out the use cases for the SDK. There's already a pretty healthy list going on the Google doc. And then we go through and we kind of stack rank those. We figure out what's the most important, what are the most important things that this SDK needs to do to actually put the cloud event specification into developers hands tomorrow. And so we go through, go through the exercise of stack ranking these use cases, see where our priorities are. And from there, we can start breaking this down into some potential milestones and the scope of each milestone within respective cloud events, SDK versions. And so on the Google doc below the potential use cases that put it in a milestones scope section with different cloud events, SDK versions. And we could just put bullet points under each in terms of that describe what we think that version should seek to accomplish. From there, it's gonna be up to us to figure out how the work actually gets done. I think there's no requirement that all of us here in the room go out and do this work, but we do have to figure out who might be focusing on what. So yeah, I figure we take it from there. The outcome of this should be getting some milestones and scope down for the SDK versions. And then we'd like to go take that to the main service working group call this Thursday and just present them with kind of what we're considering and get some feedback from them. And from there, I think we might be able to get a few more ball of the tears to help actually implement all this. Anyway, does anyone have any thoughts on that agenda? Does that sound okay? Or do you have any other ideas? Sounds good to me. Okay. Well, let's kick it off then. There's a list of potential use cases. These are all numbered, but they are not yet prioritized. That's our next challenge. So first off, before we go in and prioritize all this, does anyone have anything that they feel should be added? I'm just pausing because it's likely a few of you are reading this for the first time. And I can go through a couple of these. I added in a few of them, so maybe I'll provide some context onto each one. The first one here is instantiating Cloud Events easily in code. This is simply being able to require in the SDK and do some type of, it could look like class-based instantiation where you're just creating a new instance of the Cloud Events class. You're actually kind of crafting this Cloud Events and setting the values of the event itself. This seems kind of table stakes if you want to actually do anything with an event. You have to build it first. So that's what that is. Instantiating Cloud Events easily via event schemas. Not entirely sure how this would be implemented, but perhaps it could look something like JSON schema, which you're able to pass in a JSON schema and create instances of that due validation against the schema and the rules that are baked into that schema. Bringing an event schemas, I think could help out a lot to solve problems around testing events, solve problems around validations, transformations, and even generating mock events to help test out your serverless and veteran architectures. Number three, assembling Cloud Events from various transports. So there are different transport specifications that are being included as siblings to the Cloud Events specification. This is how you handle Cloud Events and HTTP, for example. Ideally, if this SDK is going to make developer lives easier, it should be able to create Cloud Events from various transports. We got to figure out how that could work. So a quick question there. When you're talking about transports, but what about the encodings? I think encoding should absolutely be included in this. Maybe I'll add a quick update. How about assembling Cloud Events from various transports and encodings? Which are slightly different things. Yes. Additionally, validating Cloud Events by including a schema. I already discussed that briefly. Transforming existing events into Cloud Events via transformation mappings. This one's kind of an interesting one because it's the early days for the specification. It's very young. And we want to make this something that people can start using right away regardless of industry adoption. We've been fortunate enough to have some of the industry influencers involved in the Cloud Events conversations. And a lot of them are implementing this already, which is amazing. But we want to move faster and we want to kind of make sure Cloud Events fit nicely into all the things that people are using already. So being able to simply transform popular common events on different platforms, whether it's AWS, whether it's Google, whether it's popular webhooks from Stripe or GitHub or something like that. Being able to transfer those things into Cloud Events, I think would help make this, I think would greatly help adoption here, especially if Cloud Events has some great experience around being able to do those transformations almost automatically. So there's, that's what that's describing. Do you see though that as a, strictly as an SDK issue or is that like a separate repo perhaps containerized drivers that would then be able to transform those events? How would you see that working with the lens of this SDK effort? Yeah, great question. I'm not entirely sure yet. If I'm just throwing ideas out there, could we investigate some type of language agnostic way of defining these transformations that the SDKs could require it? So when they receive some events in its kind of native format, and you're expecting that and you could add in this module that already has the transformation mapping into the SDK and it should be able to use that, that knowledge to do the transformation automatically. Yeah, because a lot of the times the way I think about it, you're having to pull or wait for an event to come in from some of these foreign sources, which is a little bit more than just transforming the actual Cloud Event. And so by itself, having the transformation is useful but not sufficient to be able to actually get the event in and be able to sit on that then. Yeah, there's a few phases to solve that problem. Getting the event into your runtime, where the SDK is, is kind of what I've been focused on specifically. If the SDK can help beyond that, I'm not sure how it would, but open to investigating it. But talking, having this conversation, these are other adjacent conversations that are happening within the working group around event sources and whatnot. I think all those things need to be factored into this, but right now, I believe the SDK is only gonna be able to handle kind of what gets into that, what gets into the runtime. Did someone else have a comment on that? Yeah, I was gonna ask, and then this may be because I'm a newbie and I didn't realize this was a smaller group than the main group, but yeah, I guess for this whole area, there's even a high level, is this sort of solved on a component slash architecture basis or is this on a language basis? So just purely thinking about it in terms of AWS, like is the vague idea at the moment to deploy a component that does the translation or is it more around having, doing it programmatically within each Lambda function? I think that this is more a concern of maybe something else similar to the event gateway idea so that understands there are certain incomes from HTTP, Kafka, MQP or whatever, and then you can use a component that does the filtering or transformation and then it would convert it into the proper format and then your SDK is just be your SDK that you work with the object with. I think the transformation is likely more a component sitting next to it like in order to trigger the process and to get like the full payload out. I'm not sure if it's directly concerned for the SDK itself. I would see it more as a separate thing for applying filters or transformations in order to extract something from MQP or whatever into a cloud event object with the proper metadata. Okay, it's super interesting to me. Yeah, I think that there's a few ways we're probably gonna have to go after this problem in general but here's a simple use case that I think you'll be familiar with, Mike. That is AWS Lambda receives an AWS S3 object-created event and that's in Amazon's native format. Being able to just take that native event which is already in JSON or being able to take that pass into the cloud events SDK and out of that, we're just using one method on the cloud events SDK, you get the cloud event flavor of that, the cloud event AWS S3 object-created event. Yeah, that sounds, to me, sounds brilliant because that gives you the whole cross-platform nature then and then you just take 98% of your code and put it in Microsoft and you're good to go. Exactly. Now for other event sources and other places where events are coming in, there's probably gonna be some more complications involved. Yeah, I was about to say because the example here is actually really good because it kind of draws a picture. System that can generate the event and send it versus, for example, a system that generates events but isn't able to send it by itself and you need to do some polling and then some sort of a component enters a picture that will poll for those events and generate actual cloud events and this component is then able to send them further which is like a different use case but I think in this case, it's not the role of SDK but the component will use SDK to produce those cloud events but it's additional work to actually get those events in some custom format and then convert them to cloud events. Yep, that's right. Okay, just gonna move through the rest of these real quick. Receiving cloud events, easily encode, compliment the first bullet, Iran has mentioned defining an API to access the properties of a cloud event. I think Doug Davis added this one in and I believe what he was talking about is something similar to just having the cloud events kind of be an instance of some type of class that has getters and setters for accessing the data. I believe that's what I saw in Iran's early examples of this like six months ago but it's been a while so I'm a little fuzzy on this. Next step was generating mock events from a cloud event schema. Chat about that briefly already. Cloud events extension SDK add-ons and modules. Now this one is pretty interesting. In the cloud event specification, there's this extensions concept where you could just put in a lot of different custom properties essentially and the reason why this extensions concept was created was because we don't know what should be in the cloud event schema today. It's too early. We need to get this in the hands of users and we wanted to create this area where users and vendors could come up with their own properties within the cloud event envelope to help facilitate anything to do with event dispatching and processing. So that's what- Sorry, I was trying to interrupt. I just have a question because I'm curious, do you guys see this extensions thing being used for things like for example tracing or it's a wrong place to put things like that? Like a tracing ID or something like that. I'm curious if you've seen this being used this way or do you see it as the proper place for something like that or? Absolutely, yes. Tracing is something where in this world where events are increasingly being transported across environments, being able to trace where this event has been is gonna be very, very useful. This might be something that we put as a first class citizen within the cloud event schema in the near future, but in the meantime, this extensions area gives us a sandbox to test out some of those ideas. So tracing is something that a lot of people in the working group are very interested in and I think it's probably gonna end up as an extension for a little while until we get some real user and kind of market feedback in terms of like what people prefer. Now, the interesting part with respects to the SDK is because the specification has this place where you could put in kind of any type of data that you want, this creates an opportunity for the SDK to almost have like an add-on or kind of modular experience for working with that extra data that's set as an extension. So for example, if you're a company that is providing some type of event tracing service, you can have your own, you could have some, you could work off whatever the tracing extension is that people are using or come up with your own and design a module with the SDK to help you do some more processing on that event or to help people, I don't know, maybe just pull in tracing information off that event really easily and port it right into your system or your dashboard or something like that. So this is just, this is a very early stage idea. We really got to flesh it out, but I think that there's a lot of opportunity here for the SDK as well as for vendors and end users to be able to extend the specification and do that through the SDK via some type of add-on and kind of module experience. Does anyone have any questions on that? Okay, moving on to the next one, transforming lower level events to higher order events automatically. There's been a few people in the working group who have requested this idea of getting away from like provider platform specific events and trying to come up with some higher order events for things that the providers, for events that the providers and platforms have in common. For example, in the big demo that we did at KubeCon, we had everyone create, I think it was 11 different serverless functions to process two different types of events. So these functions had to be written to process two types of events. And those events were an AWS S3 object created events and then a Microsoft blob storage object created events. And because the functions had to write logic to handle both these events, yet the events kind of had the same properties, the same ideas in them, what emerged from that was just requests for, hey, can we just create some general storage object created events? That's not platform specific, but maybe an SDK or something could take in a Microsoft blob storage event or an AWS S3 object created events and output this kind of general storage object created events, which has goals around, just being easier to write code around without having to worry about, what specific platforms are including in their event data and also might get us a bit closer to portability one day. So don't know how the SDK would be involved in that but throwing it out on here. Yeah, that's actually very interesting to me. It sounds, I mean, if this work, they'll be great, I would say, because I'm being able to generalize events like that. I'm just curious how, maybe I'm going too far for now, but I'm really curious how that will work because each platform has some like its own ways of accessing the actual object that was created and doing something with it and probably some specific identifiers and so on. So I'm curious, what will be the use case of the general, like you probably wouldn't be able to access the object without a specific platform SDK. So I'm curious, what's the use case of having a generalized event like that? How it would work is something that, we'd have to figure out if it's possible and what that implementation would look like. Going back to the S3 example, I believe you could take Cloud Events SDK and if it had that transformations concept in it, you could just build in a transformation that takes AWS S3 object created and converts it to a storage object created event. As long as you kind of receive that event already and you're able to process it in code, same goes for the Microsoft version as well. But it's early days, just throwing the suggestion out there, but there's definitely a lot of interest in this, especially just to help people write more portable functions to react to anything. You could see how storage object created, that pattern could be applied for database record created or something like that. And these things cover a broad surface area, but anyway, the idea is out there. We could dig into it to figure out how to work and if it could work. In a lot of ways, this and five should be combined, because this is really a subtopic of the general transformation. Great, I will put that as a sub bullet point here. I was literally just about to ask how this is different to five. Well, it is different, but it's very similar because instead of taking the native event and transforming it straight into a cloud event, it's actually transforming it into a totally new cloud event type. Yep, that's correct. Okay, almost through these, configuration extension for adding middleware the SDK can use to publish events. Yes, that's right, there's a few people who are offering middleware for cloud events, infrastructure to help with the general dispatching and routing of events to wherever they need to go. Our company does that, we have a product called the Event Gateway, Microsoft, who's represented by Clemens in the serverless working group. They have the event grid, we have dispatch, a lot of the serverless open source compute platforms are doing the same thing, and it would be neat if there was a way to just include the middleware or whatever you're using to help facilitate event delivery into the cloud events SDK, so that what the developer gets, what the experience that they get is simply being able to do cloud event dot publish, they call the publish method or something like that, and because the configuration is already stored within the SDK, that cloud event will immediately be sent to wherever it needs to go. This could be kind of native configuration or it could be implemented as an extension if we add in that functionality for extension add-ons or modules. Is this where something like Microsoft's bindings feature might kick in, because that's one of the things I'm really interested about seeing from this kind of open standard. Highly likely, yeah, that could be included in here, I'm sure it could be baked into the SDK in a number of ways actually. Myself and John Chapin, we've always thought that that bindings feature that Azure Functions have is one of its clear differentiators over Lambda. Yeah, we've heard the same. A lot of people really appreciate that feature, and there's definitely a lot of opportunity to leverage that and even replicate it perhaps in this SDK, but I think we're a little ways out from that. Last up, version SDK with specification. That's simply, as the specification gets changes, we're gonna come out with a new version of the SDK. Pretty simple, pretty simple use case. Okay, that's everything. First off, are we missing anything? Does anyone have any further ideas in that we've been through all those? I think there's also more meta logistical issues with respect to, do we want to think about how we would formulate these SDKs into GitHub, naming structures, how we would extend that, language, how we would, what would we want? Generic names, do we want language specific bindings to make it flow better within a language? I think that there's a whole bunch of meta issues beyond just these. I totally agree, and we'll have to figure all of that out. I think perhaps the first step will be to figure out what this thing does, what it's focused on, and then figure out how we're going to coordinate logistics, figure out the implementation details, figure out where this thing is gonna be hosted at the end of the day, which I imagine is just gonna be the cloud events at GitHub repo. All right, do we want to go through the exercise of trying to stack rank these? Does anyone have any strong feelings as to what should be number one? What should be the first priority? I would say basically creating cloud events with the proper version of the SPAC and creating the objects like the must have for the SDK, because that's where you start. But I would start with this. Can two and four be merged? Yes. Okay. Personally, I think schema is the most important thing. Schema's the most important thing, okay. It seems, okay, so that was one vote for what I think is just instantiating cloud events easily in code, but there was an additional comment in there. With the version, with you. So is that nine? Yeah, with the nine, exactly. Yeah, I would also see that as a first code accessibility there. Okay. And I wasn't able to see who made the comment around schema, why that should be first. But I'm curious if you could follow up with some additional details as to why you feel that way. Yeah, sure, if you have the schema in there, this is Scott, by the way. You don't necessarily need the easy in code part because you can easily look at what the meta is supposed to look like. Like you know the shape of that event. And that gives you things like defaulting and validation and programmatic lookup of what is actually in the message object. Yeah, those are good points. Scott, how do you, given this is just an MVP initial version, do you have any ideas on how we would actually implement this? So I've done a lot of JSON schema work for OSB. Oh, great. So I would assume something like that. You can also, using that, you could inject like form schema and things like that and generate UI so that you can have a producer that makes your events that you can test your application based on what it's expecting. Yeah, our company makes the serverless framework and helping out developers just generate events easily, test them easily, validate them easily is something that we really wanna solve because that's a big part of the workflow over there. So this definitely resonates with me. I'm not personally sure if that's the first priority I'm still leading toward is danshing and cloud events easily in code. But Scott, do you think this could actually work with JSON schema? I need to read the spec more. So let me get back to you. So I'm wondering what exactly is meant by events schema. Is it the payload? Is it the attributes? I mean the event context or what is covered? If I had a vote, it would be the entire object. Yeah, when we talk about the cloud events specification itself is kind of the schema for the envelope. And then here I think this was specific to the actual payload, the information it contains. We already have in the cloud events specification a schema URL, which I believe is focused just on the payload. Okay, I'm just wondering if there isn't already enough tooling around for taking something like a JSON schema and validating something against it. So is this really cloud event specific? You know, what we put in that schema I think will be somewhat cloud event specific, but in my opinion, being able to leverage anything that's out there in the ecosystem that's already popular and solves this problem really well is definitely in our best interest. I would say it's probably not specific to the spec, but SDK might be as a helper. Obviously, there's an art of not overloading the SDK with tools and features, but it might be worth adding just as a helper. So I'm leaning towards number one as being my number one pick, but Scott, I would like for you to be able to look at number two and come back with a proposal for what you think the event schema would look like. Yeah, sure, I can do that. I'm gonna echo what Mark said. I really like number two. I just would love some clarity as to how we could actually get that done, whereas number one seems like an action item that people can kind of go run with. And then maybe number five, actually receiving the events. Yes, receiving event cloud events easily in code. Yeah, I'm not sure where to put this. I guess would this be like a number, a number three, a separate item? Maybe number two, I agree like schemas is important, but not the number one important thing. And you think this is, I have to confess, I'm still trying to figure out what they're trying to capture in this. Yeah, isn't there receiving a little bit related also to the actual implementation? Like you say something down there in your proposal with middleware from a note perspective, but if you transport it to other languages, you could completely have different mechanisms of actually receiving them in a system. For instance, we have a Java API that basically implements the spec of one. That's just a very tiny jar file. It is easy to combine that with Java based eventing. So I can just very simply create observers using some Java eventing framework, then I have a way to actually receive them in my system. Right. Yeah, I think there's some language specific use cases for that which are not, you know, general things, but should be concerned of SDKs for different languages for like things that, you know, can deal with events in different languages that are not general but language specific. That's right. That's gonna be a challenge we deal with as we go to implement all this functionality across the languages. Could we rewrite this possibly? Would this be a little bit clear? You know, from what I remember from your own specification, unfortunately he's not on the call, was that he wanted a way, he wanted simple getters. So it kind of follows these two things. And what you get are, you know, an instance of a class or something with a simple kind of getter and setter method so that you can get data out of the event pretty easily. That's how I read it. Maybe we could rewrite it to say something like getters and setters for CloudEvent instances. I'd actually make those simple with a one. Yep, I agree with that. And it's really, what is the API look like within SDK and part of that is do you have getters, setters, et cetera? Why setters? Isn't an event something that is immutable? Well, if you're creating a new event. Yeah, yeah, okay. I have a builder for that then, okay. But in my Java example, for instance, there is an interface that just defines the different and they create it from the builder. So I have the event itself immutable. Right, I mean, that's an implementation. Yeah, right, language specifics, okay. You know, until an event is actually emitted, then you should be able to modify it. Yeah, yeah, this is also, this is something that's being discussed and has been discussed for many months within the Cloud Events Working Group. What can be changed? What can't be changed? And I don't think we have a definitive answer yet. Largely leading towards immutability as much as possible, of course. But then there's a few different parties that interact with events potentially along the way and giving them the opportunity to set information. For example, middleware. Should middleware be able to kind of put some information in the event or modify anything? That's a point of contention within the group. Okay, pretty straightforward so far. Can you remove number nine? I think you encompassed that number one. Yep, number nine is gone. Okay. So for me, number four and five. Carl, what was that? Carl, it sounds like you dropped out for a second there. Oh, sorry. Yeah, I'm having some electric work at home. So my wife will be behaving well. Let me just switch to cell phone. So I was going to say that number four and five are equally important to me because they define how I'm going to consume events and how I'll be able to receive them or create new Cloud Events from non-Cloud Events. Not events that are not Cloud Events yet. So I would say they're both really important to me. So I'll put them both as the next next item. Well, I sort of feel the same way. Okay, but before we add these in, does anyone have any other thoughts on what number three should be? Doesn't sound like it. I guess to me, what I would value most is something quick and easy from an existing, that I can incorporate into an existing platform, either Azure Functions or Lambda. So whatever gets me to that the fastest is what I care about. Even if it's a prototyping and being able to give it to some people to say, how does this feel? I'd actually say number three should be number two. Okay, interesting. So in other words, I think that we do have some questions about the schemas and how that would interact operate, but assembling Cloud Events from various transports and encodings is pretty fundamental for being able to take the actual event and getting it into the system. Yeah, I certainly agree with that as well. Okay, I think that's a good point. And by the way, I know this is set in stone. We're gonna take this and propose it to the surplus working group on Thursday. It gets some feedback from them. Just curious, Mark, what do you think our first step should be on this priority, assembling Cloud Events from various transports and encodings? Well, we need, it's really understanding the scope of what that truly means. Is it taking an input stream? Is it taking a blog of data coming in, say, HTTP and being able to parse it, et cetera? I don't have a good answer for that. Yeah, that's what I'm trying to get from you, but, because I don't have the answer either. So you take a MQP, more of a binary protocol coming in, we know that we need to transform it and it's probably on a protocol basis, but it's gonna be very specific to that. But it's gonna be very specific to that transport. So we need, I'd say, identify the transports, which are the ones that we are currently defining. And then look at what would be the generalized decodings and encodings that we do for each of those. And the transport specifications that we have currently, it's HTTP, AMQP, NATS, we also have a webhook specification. Right, yeah, that's true. Do you know what the status is of that? I don't. Okay. You also have MQTT. Oh, yes. I was just pulling up the site to make sure I didn't forget anything. Okay. But again, so why would we do this? And it's primarily to have consistency into gain adoption of cloud events by having an off the shelf. Here's how you would implement a name, QP source going into cloud events, into a cloud event. Yes, that's right. Okay. Yeah, we just need further clarity as to how we're actually gonna go about this, which we can present to the working group on Thursday and get some feedback. Okay, we have four priorities so far. Let's spend the next couple of minutes, just maybe sorting the last four items here. I think one of them we already covered, so number three. Does anyone have any feelings on number five? The fifth priority should be, I think some of these can also should be bullet points. So generating mock events from a cloud event schema, that's, I believe that's a sub point, number three. And you could also say that on number one, we would want to be able to test it. And part of that test would be creating, and encoding, decoding, et cetera, a lot of events. So in other words, we would need mocking of events for test purposes there. I agree. Do you think that's a bullet point in number one, or is that its own? It's a bullet point. Okay. Mocking of cloud events for the test. Okay. Last, we have cloud events, extension add-ons and modules, and then configuration extension for adding middleware, the SDK can use to publish events. All similar, isn't it? Yeah. So what if we put cloud events, extension SDK, add-ons and modules is number five, and then the middleware has a simple point of that. Sounds good to me. All right. We got something. Cool. Okay. We have 10 minutes left. Let's see if we can break these down into cloud events, SDK versions. We've got a version 0.1, 0.2, 0.3. What should we put in SDK version 0.1? All right. Question first, which is, I assume that these versions are independent of the actual cloud events back versions? I believe we're probably gonna have to... Decouple them. Increment the, well, yeah, I guess so. Unless we decide just to increment the version every time the new specification comes out, and we update it. We could start out of the gate and have a version awareness built into the SDK so you can always be backwards compatible. So you ask the SDK, generate me a vo.1 event, and it spits that out. Yeah, I love that. No, no, no, no, no, no, no, no, no, no, no, no, no. And these milestones could be release candidates or alpha, beta, whatever, so that, for instance, the first alpha version or first beta version of version 0 would be, for instance, item number one, compliant with the specification 0.1, and so on, that 0.2, or would be then like the next release candidate matching the same 0.1 specification. Is that something that could fly? Perhaps. I like the idea of being able to work with the different versions of Cloud Events. It's going to increase the amount of work we have to do, of course, but it is something that people are going to want. It almost sounds like a totally different priority to me unless this is just baked into number one. I think if you build in that functionality into the library to start instead of try to add it later, it becomes easier. Yeah. And then people have to follow that pattern versus try to shim it back in once we've passed that point where it's non-trivial. Yeah. Okay. Do we think this is a totally kind of separate priority? It's probably a bullet point on one. Yeah, I agree. Okay. So in that vein, you could get the SDK to have some sort of negotiation where you can ask it, what's the biggest, or what's the compatible versions it produces. And then you can follow correct JSON semver with the SDK. I guess what I'm trying to say is that maybe the version doesn't really matter but the milestone, like an abstract number, there could be multiple releases between each milestone. Oh, yeah, right. These semver versions. Okay. Yeah, we'll present this to the working group and we'll get some feedback and see. How they think we should handle all this. All right, so putting this into milestones, how do we feel about just putting number one as Cloud Events SDK version 0.1? Yep. Like the two. So it's giving us a good quick start. Yes. Yes, yes. Do we want to bound the languages that we would support for the 0.1? And it doesn't that we have to name those languages but yeah, we want to support three languages. I'd love to do that personally. I think we're subject to the voluntary effort that we'll have kind of on hand. So. Right, I'm just thinking about ensuring that we're going down right now. We could implement in the same language but it wouldn't give us as much data about usability or how you would encode it into other languages. Okay, well, how about we just set a goal for three languages, supporting three languages? Okay. We'll see if we have the help to make that happen. If we do, fantastic. Okay, so what if, because we only have four minutes left, what if in version 0.2 we put assembly cloud events for various transports and encodings? Any objections? And these are, this gives us some sense of priority. Obviously there's, each one of these things could be a lot of work. So we're going to have to put some limits on this. But at least it gives us some sense of priority. We could present this to the working group, get some feedback. And then maybe cloud events, instantiate cloud events easily via event schemas. Can we put that in 0.2 or 0.1? Or should that be 0.3? I think it'd be interesting to get more scope on it to 0.2. Yeah, let's put that at 0.2. Cause it seems like something we could lean on for, we could lean on other popular tools to help implement faster. However, of course, all these things I think we need to work clearly to find the scope. But at least we've got some priorities. We've got some areas where we, which we think we need to focus on first. We'll present this to the working group on Thursday. At the same time, I wanna ask, there's a few people who've already started like Mattias and you guys over at VMware, you've already started designing some cloud events SDKs. Are you interested in continuing this work within a specific language? Yeah, for our case, for sure. And Mattias, you're doing a Java implementation, correct? That's right. Yeah, for dispatch, we're doing go. Okay. Yeah, I'd love to work on that within a cloud events group. And it goes without saying that I would, I assume we would put an applicable license onto it and put it into the cloud events repo. Yes. Does anyone have any objections to doing that? Well, I think in order for it to be a quote unquote official cloud events SDK needs to be part of the repo. Yep. I'd also say on the assembling cloud events from various transports and the coatings on 0.2, perhaps we could say implement at least N number of those transports and N to be decided, meaning, do we just implement one of them? Do we implement all of them? Yes. Okay, I'll put this as a comment, a quick comment. But we only have a one minute left. We have three languages. We have Red Hat working on Java, VMware, Dispatch working on Go. Our company would love to contribute to the JavaScript implementation. Is anyone gonna work on any other languages? Didn't someone already start a Python? Oh, someone did start a Python. If I remember correctly. Yes. I'll add them. I'll add them to this later. Cool. We've just had the time limit. So we've got a good sense of priorities here. We'll present this to the working group on Thursday and we'll have a longer conversation around this and hopefully narrow in on a more clearly defined scope for some of these SDK versions. Okay, in the meantime, before we wrap, does anyone have any other comments or major outstanding questions? No, thanks for putting this on. What are next steps? We're gonna talk to, we're gonna present this to the Cloud Events team on Thursday and then set up a subsequent call. That's correct. We haven't had a weekly call as of yet. We're going to pitch, we'll pitch this to the working group and figure out how to move forward based on that conversation. Probably we'll schedule another call in which I'll reach out to all of you. Great. So I grabbed the Python version out of the Manlin list from GitHub and put it into chat if you want that. Fantastic. Thanks, Mark. All right. Okay, everyone, chat with you on Thursday. Thanks for your help. Bye-bye. Bye-bye, guys. Bye. Bye-bye. Thanks. Bye.


Hello! This video will show you how to use the program called OnTrackEaseRecovery to restore documents lost after formatting a USB drive. To do it, connect a USB drive containing documents to your computer and format it. After that, start OnTrackEaseRecovery and in the SEP 1 window choose MemoryDevice. Next, in the following window choose the USB drive and click on Continue. Select the case of data loss. In our case it is FormattedMediaRecovery, which means recovering data from a formatted media. Check the settings you selected and click Continue to start the scan. Wait for the scanning to be over. OnTrackEaseRecovery showed all files found on the USB drive in folders according to the file type. Search for the files you need. As you can see, the program only found some files that existed on the USB drive before it was formatted. There are two PDF files. Select them, right-click and choose Save As. Specify the folder to save the recovered files. And now the files have been recovered. Now let us scan this USB drive using Hetman Partition Recovery. Choose Full Analysis and wait for the disk scanning process to finish. As we can see, the program has found the files missed by OnTrackEaseRecovery. Though their names were changed, they are placed into folders according to file extensions, and you can find the necessary file after viewing it in the Preview window. In summary, we can say that OnTrackEaseRecovery is quite a good piece of data recovery software with a good set of functions. However, as it is often the case, the list of supported languages could be more extended. Still, on the example of data recovery from a formatted USB drive, we can see that for some reason it failed to bring back all files, unlike Hetman Partition Recovery. It is most likely because this program lack the signature analysis algorithm of Hetman Partition Recovery, which recovers files based on their contents. When finding a certain sequence of bytes on a disk, the program reads it and displays its contents for the user to see. That is why, if you formatted a USB drive and you need to recover the lost files, it would be better to use Hetman Partition Recovery. That is all for now. Thanks for watching! I hope this video will be useful for you. If you liked this video, click the Like button below and subscribe to our channel to see more.


Listen 3.39. I will receive whatever I request. No one desires pain, but he can think that pain is pleasure. No one would avoid his happiness, but he can think that joy is painful, threatening and dangerous. Everyone will receive what he requests, but he can be confused indeed about the things he wants, the state he would attain. What can he then request that he would want when he receives it? He has asked for what will frighten him and bring him suffering. Let us resolve today to ask for what we really want and only this that we may spend this day in fearlessness without confusing pain and joy or fear with love. Father, this is your day. It is a day in which I would do nothing by myself, but hear your voice in everything I do, requesting only what you offer me, accepting only thoughts you share with me. Amen.


In order for us to fully discuss electronics, we're going to do a quick review of the atom and we're just going to discuss some parts that pertain to us as electricians. So let's talk about the three main parts here. First and foremost here, and not foremost, but first we've got this middle guy here. This fellow right there, and we're going to give him a name. We're going to call him the nucleus. So let's get that. Nucleus. So that's the nucleus. It's comprised of protons and neutrons. It's got a net positive charge because your protons have a positive charge. Your neutrons have a neutral charge or no charge. Next up, we have these guys that are orbiting around these. We've got these three guys here. These are called our shells. Now our one closest to the nucleus will have two. The one next to it will have eight, and it goes on and on and on outwards. What we are mainly concerned about with is the third part, and we're going to call this guy right here, our valence. So let's talk about that, our valence. Now our valence is important to us because it is the electrons that are on the valence. These guys right here that are important to us because those are the ones that can break free and certain moving. And that's what current flow is. Current flow is just electrons that move. And so if we can break these guys free and get the moving, we are going to get electron flow. Now looking at this guy here, the one atom I've got drawn, I've got an aluminum atom. You can tell that by the AL, which is aluminum in the periodic table. The aluminum atom will have three valence electrons. That makes it a good conductor. So let's just discuss a little bit about the conductors. Now before we get too far into conductors, you'll notice here on this drawing I've got, I've only got one shell. That's because like I said in the previous slide there, we don't concern ourselves with these inner shells. We are concerned mostly with this outer shell, the valence shell. Now in this one here I've got one valence electron. This guy here, he is easy to break free because he has no friends holding his hands. It's like a gamer red rover when we're talking about the valence shells. If a force is pushed on this guy, if you give him a little bump, he will easily break free and flow. Which is what current flow is as I discussed before. So when we look at these guys, and this one here is a copper atom. It has one valence electron, which means it can break free. Aluminum will have three. Which means that if we have any atoms that have between one and three valence electrons, they are good conductors. So it's just good to note that one is copper. Let's just get that written in here. Copper and three is aluminum. And those are good conductors. Between one and three makes a good conductor. Now if we have got a good conductor, what's the opposite of a conductor is going to be an insulator. So let's take a look at that. Now if one to three valence electrons were a good conductor, then we're looking at this guy here. If you notice, if you count up his electrons, and I'll count them up for you, one, two, three, four, five. He's got five electrons. Like I said before, like a game of red rover, these guys are all locked together by some nuclear force. It is harder to get them to break free. They kind of hold each other there. It is possible if you exert enough force on it, it can break them free. But for the most part, they're going to hold. Now with that force, it's going to kind of stretch the atom out and it'll turn into more of an elliptical type shape. We'll talk about that when we talk about capacitors. Now right now, we've got this guy here, which is out of five. Now if we look at these ones anywhere between five and eight. So anywhere between five and eight valence electrons makes a good insulator. So one to three is a good conductor and five to eight is a good insulator. If we've got one to three and five to eight, we're missing a number there. It's four. So let's take a look at a semiconductor. So a semiconductor is going to have four valence electrons. We've got the one, the two, the three and the four there. It's not a good conductor. It's not a good insulator. Basically on its own, it's almost useless. But what we're going to see in the next video is if we get a bunch of these guys together, these semiconductor atoms, they're going to form what's called a crystal. And then depending on what we do to that crystal, it can actually either act like a good conductor or a good insulator. It becomes almost an electrical valve. I don't want to get too far ahead of myself. So this is your semiconductor. Now, semiconductors are made of these two common types. There's the silicon and the germanium. The most common type is the silicon though, which the reason why we like silicon so much is it can resist heat a lot better than germanium can. And we're going to talk about negative temperature co-efficiency in another video. But as this guy heats up, it ends up having its resistance go down, which is kind of the opposite of every other kind of substance out there. And when that happens, the current goes up, it heats up, its resistance goes down. You start to see what I'm saying, it starts getting out of control, then cascades out of control. Silicon's better with standing heat than germanium. Also, silicon forms 27.7% of the earth's crust. Only oxygen is more common. So you can find it everywhere. So we can take this stuff and we can turn it into a crystal. And as we'll see in the next one, if we dope it, we can put it into a diode. So that's what the next video is going to go into. We'll see you in the next one.


And I want to make it clear, we have no issue with the government of Taiwan, nor we have issue with the film that the film involved. We have absolutely no issue. The government has no issue with them. What the government has issue with is the way the government of St. Lucia handled these affairs, which puts on due pressure on other people because of their actions. When these transactions are done, there is need for a clear path. So the payments come directly from the contractor to the subcontractor. So OECC, they have not done one spade of work on St. Jude. Subcontractors have done that. So to give the impression that workers done by OECC is not true, it is done by a subcontractor. Very important. OECC is a reputable firm. They've worked everywhere in the region, a reputable firm. But the fact is, it's not a matter of reputable. It's a matter of ensuring that the finance act is followed and the assets of the people of St. Lucia are protected by making sure that there is no room for anything improper to happen.


Okay, so we're going to be talking about boosting aerobic capacity, Chapter 16 of the textbook. Presenting today is Nathan, Jordan, and Chris-Ann. Hey. Hi. Some of the topics we'll be covering are assessment, planning, and training. Several factors should be taken into account to establish a training program. During this presentation, our main focus will be the initial level and more specifically on the assessment of the athlete. This is Killian Jornay. He's a ski, mountaineer, and ultra-runner. He has one of the highest-recorded VO2 maxes in recent history at 90 milliliters per kilogram per minute. I want you to make that cool. So something interesting about Killian is he actually has a lung capacity of about 5.3 liters. I've recorded mine in our physiology lab at just about six. But as you'll see, that alone is not enough to determine the aerobic capacity or fitness of an individual. Aerobic capacity is most precisely evaluated by determining VO2 max, and it's often assessed with the use of a breathing mask to measure gas exchange. This method is effective, however. It can be time-consuming, complicated, expensive, and inaccessible to most. An easier method for measuring aerobic capacity is through the use of maximum aerobic speed. So that's what we're going to talk about. Laguerre and Mercierre were able to show that MAS is closely correlated to VO2 max by the use of this equation. In 1984, they studied about 130 subjects, and they measured their full VO2 max using the mask and everything. And then they also did a simple treadmill test. They then compared the two results, did a little bit of math, and came up with this equation. So if you take the MAS that they found from the simple treadmill test and you multiply it by 3.5, you roughly get their VO2 max. So to measure MAS, you'll begin running on a treadmill with the initial speed set between 8 and 12 kilometers per hour. 8 kilometers is for someone who's untrained, and then 12 is for more elite athlete. You run each step at two minute increments. At the end of the two minutes, speed is then increased by one kilometer per hour for the next two minutes. This step-wise progression continues until the athlete can no longer maintain that speed. The last completed step is then used to determine the MAS. Here's a chart showing on the left the velocity, and then on the right the comparable VO2 max. So we decided to run this ourselves, and here this shows one of us. The MAS was 14, that was the last step they were able to complete, and then using that equation, VO2 max was 49. So here are our VO2 maxes that we calculated from doing the simple treadmill test. The use of MAS allows you to determine the different training needs of each athlete. You can see here that the three of us would not be able to train together at the same pace, and that we all have different specifications for training based on our experience and goals. To date, Lake Air's equation is one of the best alternatives for prediction of VO2 max throughout the wide range of development. So the next factor to determine aerobic endurance is planning critical speed. So critical speed is defined as the threshold intensity above which exercise of sufficient duration leads to attainment of VO2 max. So to be able to calculate critical speed, all you need to do is perform two different distance runs at max effort for greater than three minutes in duration. By dividing the distance over the time, you generate your critical speed as shown on this slide. So we decided to take Nathan's information and determine his critical speed. So the first run was a 1,500 meter run and he ran it in 480 seconds. The second was a 3,000 meter run, sorry, and he ran it in 1,000 seconds. We did the math and were able to generate his critical speed at 11 kilometers per hour. So this is his calculated critical speed. The speed signifies the pace at which he needs to train to improve his aerobic endurance. So aerobic endurance represents the ability to sustain a high percentage of VO2 max for a long period. So to be able to estimate critical speed, the MAS test is also useful. It allows us to estimate the pace you would have your athlete to train to improve endurance. Critical speed is generally between 70 and 90 percent of MAS. So in a training program, aiming to improve VO2 max, the intensity should be higher than the speed. So if you remember, Nathan's MAS was 16.5. So if we use 70 percent of his MAS, we're able to estimate his critical speed to be about 11.5, which was within that range of calculated critical speed, which was 11. Now I'm going to talk briefly about an alternative method to determine your training pace. And it's called the MAFETONE method. Dr. Phil MAFETONE is a chiropractor who became quite famous because he has trained some athletes that were very successful using his method. One example is Mark Allen, who's a six-time Ironman world champion. And he used the MAFETONE method to train and beat his competitors. The simple way to calculate this pace is this 180 formula.  And this gives you a heart rate at which you're going to train. So I did this last year when I was training for a 50-mile run. So 180 minus my age, 33, and then minus five, because I had been injured and sick more than a couple times that year, gave me 142. So 142 is the heart rate, the max heart rate that I can achieve when I'm training, meaning I have to stay beneath that. So the range that I trained in was 132 to 142 beats per minute. I did that for three months while I was training for this run around Mount Hood. I also studied my flashcards while training. And I did a couple of trials, so you can keep track of how you are improving. Instead of looking at training by pace, you look at your pace at that particular heart rate. So when I started, I had a mile pace of 521 seconds. That's somewhere around eight and a half to nine minutes per mile. And I began training using the heart rate method. And over the first three weeks, I dropped about 40 seconds off of my mile time. Over the next couple of months, it went back up a little bit. But by the end, I was able to lose over 30 seconds off of my mile pace. So that's just by running at this slow but long pace. And other athletes have reported very similar benefits. Maphatone kept data on athletes that he trained. And for 233 of his athletes, 76% of them were able to run a personal best in their 5K distance after about three to six months training like this. But this isn't without controversy. This data was going to be published in a article recently. And Tracy Hogue was the doctor that was going to present it. She presented the data. But this data was from 1980s. It wasn't well-controlled. This was before personal heart rate monitors. Phil Maphatone was using this one that weighed like a pound. And so athletes weren't necessarily using heart rate every day. Also, there's still a battle between this idea of long and slow versus the more high intensity, like the HIIT training, the high intensity intervals. So which is better? In a study by Murious and Koalchuk in 2010, they were able to show that the slow, the long, and low intensity training provides central adaptations in the way of greater maximal cardiac output. So you're changing stroke volume is because of the Frank Starling law. But if you do high intensity training, what you're going to see is a peripheral adaptation that's measured by bigger arterial venous oxygen difference. So assuming that the muscles are better able to take up oxygen and mitochondria become more productive. So that's the difference between low intensity, long endurance versus the high intensity bouts. And that wraps it up for our overview of chapter 16 on boosting aerobic capacity. There's a lot more we didn't cover on more specific training protocols. You can check out Cisco's video for that.


Since 1775, 48 million Americans have served in the armed forces. From the battlefields of the American Revolution to the mountains of Afghanistan, men and women have served and sacrificed their lives defending the Constitution of the United States. Today we continue to honor those who have served by celebrating Veterans Day. On the 11th hour of the 11th day of the 11th month of 1918, an armistice was declared between the Allied Nations and Germany in the First World War. On November 11th of the following year, President Woodrow Wilson proclaimed Armistice Day, remembering the heroism and sacrifice of those who served. I think that it is a very important holiday and that we should always take the time to stop and say prayer for all of the troops that are overseas fighting for us every day. November 11th became a legal federal holiday in the United States in 1938. In the aftermath of World War II and the Korean War, Armistice Day became Veterans Day, a holiday dedicated to American veterans of all wars. We're standing here right now. I'm heading to the Gulf Course having a good time. And if it wasn't for all the veterans that served through all the wars, we wouldn't be here right now having a good time. And that's what it means to me. It's great.


This is the hardest form of heat transfer to block. Even vacuum can't block it. What you do if you really want to stop this form of heat transfer is use mirrors. So for example, often you will see clothes, say ski jackets, will have silvering on the inside. That's so that the radiation from your body bounces often back into you, rather than getting out through the clothes. Likewise, a thermos flask typically have two layers of mirror inside with a vacuum between them. So that means the heat inside has a lot of trouble getting to the outside. It can't conduct because there's a vacuum. It can't convict because it's a vacuum and it can't radio very much because the mirror surface reflects most of it out. So that's the third form of heat transplant. It's a very important one, heat transfer, because it keeps the earth warm. But it's also a very hard one to stop.


Welcome dear learners to the second part of the video on the topic human resource management. My name is Chainika Senapati and I am from the discipline of Maniram Devan School of Management, Krishnakanta Hondikoi State of University. In this part of the video session, we will discuss about the functions of human resource management. We will also discuss about the role of HR executives and lastly we will discuss about the challenges of human resource management and also we will discuss about human resource development. So dear learners, let us now discuss about the various functions of human resource management. So on the basis of various functions which the human resource management generally undertakes, there are many functional areas that we can discuss here in this video. First is the organizational planning, development and task specialization. Which is a very vital point for the achievement of predetermined goals in an organization is concerned with the division of all the tasks to be performed into you know manageable and efficient units and the human resource manager should perform the planning you know development and designing of an organizational structure through the fixing of the responsibility and authority of the employees for achieving the organizational objectives. Then comes the staffing and employment. The staffing process we all know is a flow of events which results in a continuous manning of organizational positions at all the levels from the top management to the operative level that is the bottom level management. This process includes you know manpower planning, authorization of planning, developing sources of applicants, then evaluation of the applicants, employment decisions like selection you know then offering like placement, induction, then orientation, training, transfer, maybe promotion, demotion, so all these things comes under staffing and employment. Now training and development is also very important for the employees in an organization. However it is a complex process and concerned with increasing the capabilities of the individual and groups so that they may contribute effectively to the attainment of organizational goals. So under this area the training needs of the company are identified, suitable training programs are developed then operative and executives, the employees are identified for the training and they are given with the training programs. Then let us discuss about the compensation wage and salary administration. It basically it is basically concerned with the process of compensation directed towards remuneration of the employees for services rendered by them and motivating them to attain the desired level of performance. The components of compensation wage and salary may be you know job evaluation through which the relative worth of the job is determined, you know developing and operating a suitable wage and salary program, then non-monetary incentive compensation plan have to be developed for encouraging the efficiency of the employees, then evaluating employees performance at work through a system of performance appraisal and motivating employees by creating you know condition, good working condition. Then comes the employee service and benefits. So these are mainly concerned with the process of sustaining and maintaining the workers or the employees in the organization which includes the policies, the techniques and procedures for the safety and health of the employees, then employee counseling is also important, then medical services which includes the provision of curative and preventive medical and health improvement facilities, then suitable policies and programs are framed and efforts are made to administer the recreational and welfare facilities, then there should be fringe benefits and supplementary items should be made available to the employees. Then let us discuss about employee records. In employee records complete and up-to-date information is maintained about the employees so that these records may be utilized as and when required at the time of making the transfer or promotion or giving them merit pay or sanctioning leave etc. Then is the personal research and personal audit. This area of human resource management is mainly concerned with the systematic inquiry into any aspect of you know broad question of how to make a more effective and organization's personal program like recruitment, selection, development, then procedures and policies and findings submitted to the top executives, then data relating to you know quality, that are related to wages, productivity, if there is any grievance, then absenteeism if it's there, then labor turnover if there is strike or lockouts, again the personal research and in the personal audit comes the Moral and Attitude Survey also. Now dear learners let us discuss about the role of HR executives and HR executive perform all the basic functions relating to human resource starting from recruitment till the wages and salary administration. So HR executive is the key member in the HR department and plays a very vital role or very important role. So some of the major roles may be recruitment, then understanding the manpower you know requirement of each department, then understanding the requirement and then accordingly you know drafting a job description, then getting it approved from the concerned department, then securing candidates that you know match the desired skills, then communicating the employees, employment status to the you know applied candidates, maintaining records, updating the database of the candidates, then doing a background verification of the shortlisted candidates. Again they are concerned with induction and onboarding you know like for example giving offer letter and issuing appointment letter to the selected candidates, then communicating the policies, procedures and culture followed by the company to the employees, newly recruited employees, then introducing the new journey to the team and the supervisor or the manager, then introducing them with the HR policies and HR manuals and so on so forth. They also keep records of leave and attendance, you know keeping a track of the attendance of the employees, feeling the leave forms or keeping the track of the leaves taken, then they are also concerned with performance management, you know they helped the appropriate authorities in doing the performance appraisal of the employees, then you know they maintain a record and track on employees turnover and exit rate, they take necessary steps to engage and involve the staff of their work. Again they are also engaged with the workforce management, some of the major roles played by HR executive in HR work management would be you know handling the staff properly, handling cross-cultural things, then you know monitoring that there is no groupism in the organization due to which dissatisfaction arises. Also they are you know engaged with conducting exit formalities also, you know conducting exit interviews of the candidates, those who are resigning, trying to get proper feedback for the company and trying to you know take and implement corrective measures, helping the person to be released properly, then issuing releasing letter and letter of experience, so these are the things which comes under conducting exit formalities. Again they are also engaged with compensation and benefits, you know designing the salary structure or helping employees save tax by advising them on tax benefits, so these are the things that they are engaged and human resource executives plays a very vital role in an organization. Now let us discuss some of the challenges of human resource management. First here I would like to mention about integrating organizational planning with human resource requirement, so organization planning must be closely integrated with human resource requirement of the organization, you know attention to be given in human resource requirement and their development, then human resource planning which enables the management to make forecast the human resource and to design the policies for their procurement in the you know broader interest of the organization, then acquisition of human resource which includes recruitment, selection, then managing performance, yes organization has to make a clear way for you know career advancement for the talented employees as well as you know hard working people in the organization. Also the human resource should be you know treated with utmost care and they should be motivated you know motivation of the employees become essential for an organization so that the organizational objectives can be achieved. Then compensation and benefits which are that I have already discussed it is an activity that determines salary and wage structures and other rewards and benefits to be paid to the staff of an organization and there is also health and safety provisions plays a is very important and making adequate you know provisions for health and safety for the employees build a strong workforce. Again human resource development and organization development when we talk about human resource development it is regarded as a process of increasing knowledge, competence, capacities, intelligence you know talents of members of the organization or employees of the organization in a in particular and all the society in general. So moreover it builds the confidence among the members of the organization to face challenge of modernization of the technologies that are coming in nowadays and in overall human resource development you know it facilitates organization development. Now let us briefly discuss about human resource development. As I have already mentioned in my earlier slides human resource development is regard as the process of increasing knowledge, competence, capacities, intelligence and talents of the members or the employees of the organization and it builds the confidence among the members of the organization to face challenge and in overall human resource development facilitates leads the organizational development. In every organization maybe it being or small there is a you know human resource department headed by a manager and in when we talk about a large organization more specialists are employed and when we talk about small organization there may be one person has to perform many specialized jobs in human resource departments. So all these managers are delegated to perform the activities assigned to them by the human resource managers the human resource department has to be you know continuous touch with the other departments for spoon running of the functions of organization. So dear learners with this we have come to the end of this video. The concept of human resource management has been divided into two videos that I have said in the first part we discuss about the concept and evolution of management human resource management and in the second part we discuss about the functions the challenges of human resource management also we discuss about human resource development. So human resource as I have already said are the vital elements of an organization which means an asset or wealth that can be drawn upon for aid as and when required. So dear learner thank you so much for watching this video we'll come up with some other videos with different concepts in human resource management.