Welcome back after the break. Just before we went for a break, we were looking at and studying the prophecy in Isaiah chapter 42. We are looking at three facts concerning the incarnation of Jesus Christ and his work, which foretells about the coming of the Messiah. And we looked at how Jesus as the servant, which is mentioned in Isaiah chapter 42, established the new covenant who officiates the new covenant. And also the second fact we saw that was the servant was to open blind eyes, bring prisoners out and those who sit in darkness out of the prison house. So that's what we were looking at. The second fact we were studying that the third fact is that servant was to bring forth justice to the Gentiles. We see that Jesus as the servant, as the Messiah, his ministry was not just restricted to the Jewish people, to the Jewish race, but his ministry was also to the Gentiles. It was also to bring justice and righteousness to them. And we see that fulfilled as we read these passages in Isaiah chapter 9, Isaiah chapter 8. And we see that Matthew's quoting Isaiah chapter 9 and saying that it has been fulfilled. In verses 12 to 16 where we see Jesus ministering, his ministry was basically around the sea of Galilee and where it mentions in Isaiah chapter 9, where he's talking about in the Galilee of the Gentiles. And we also see that Jesus came and ministered there and how he restored people's lives, how he healed them, how he delivered them from the powers of the evil one. And also we see that it was not just Jesus who ministered to the Jewish race, but also to the Gentiles. We also see that this task was also assigned to the body of Christ where he asked them to minister to the Gentiles. And we see that the early church fulfilled this task by ministering to the Gentiles as we read in Acts chapter 13 verses 46 to 48. Can one of you please read Acts chapter 13 please? Acts chapter 13 verse 46 to 48. Anyone? Acts 13, 46 to 48. Then Paul and Barnabas grew bold and said, it was necessary that the word of God should be spoken to you first. But since you rejected and judged yourselves unworthy of everlasting life, behold, return to the Gentiles. For so the Lord has commanded us. I have set you as a light to the Gentiles that you should be for salvation to the ends of the earth. Yes, verse 48 please? Now when the Gentiles heard this, they were glad and glorified the word of the Lord. And as many as have been appointed to eternal life believed. Amen. Thank you Rin. So here we see Paul and Barnabas boldly telling the Jews that even though they brought the word of God, then the gospel of the good news of salvation of Jesus Christ to them.  You know, but he says now we will turn to the Gentiles because the Lord has commanded us. I will set you as light to the Gentiles that you should be a salvation to the ends of the earth. So we see that, you know, they were not just doing it because they were angry with the Jews and they said, OK, you don't want to go to the Gentiles. They're willing to hear us. But it was also what God had commanded them, had foreordained for them to do it. And we see this, what they mentioned in verse 47. And the Gentiles heard this, they glorified God and we see that the gospel was taken to the Gentile world as well. So also as Jesus came and ministered both the Jews and Gentiles, it's also a command for us that we take the light of the gospel to the people in all nations around the world, people who, you know, are willing to receive and accept the gospel. OK, so this is the last prophecy that we were looking at regarding the coming of the Incarnate One, Jesus in human form. The last prophecy that we studied, anyone has any questions on chapter 4? Any questions, anything that you all didn't understand, you want me to explain again any doubts? Any comments? OK, if there's no questions and no doubts or comments, the class is very quiet today. I don't know why. There's no questions or doubts. Then we move on to chapter 5, where we're going to take some time to understand the Incarnation, God taking on human form. So we're basically going to look at what happened when the Eternal God, you know, the deity became humanity, when Eternal God became the man of Galilee. We will not look at the historical aspect of his ministry and his life here on earth, but we will look at the spiritual implications. In this chapter, we basically try to understand, you know, how humanity and deity coexisted in the person of Jesus Christ. We will look at how, you know, God took on human form and we look at various Bible references. We look at it from a Biblical perspective to understand Incarnation. OK. So we will go back to the familiar passage or structure that we've been studying from the, you know, from our first class when we began looking at Christology. John chapter 1, verses 1, 2 and 3 and verse 14. So can one of you read that again please? John chapter 1, verses 1, 2, verse 3 and verse 14. John chapter 1, verse 1, 2, 3.  He was in the beginning with God. All things were made through him and without him nothing was made that was made. Verse 14. And the word became flesh and wealth among us and we beheld his glory, the glory as of the only begotten of the Father, full of grace and truth. Amen. Thank you, Jack. And so here we see, we've already studied how the apostle John, you know, introduces the second person of the Trinity, who is God. He refers to him as the word and we looked at why he uses the word logos or he uses word to introduce the second person of the Trinity because, you know, it had a lot of significance in the Jewish background. This word logos and so apostle John is introducing the second person of the Trinity that is Jesus Christ, not as somebody who, you know, who they understood logos as a guiding reason or the principle of the mind or an intermediary being between God and the human race, but this logos himself is God. And he establishes this in verse 15 where it says, word became flesh and dwelt among us and we beheld his glory, the glory of the only begotten of the Father, full of grace and truth. So in using this title word, you know, basically the apostle John is drawing people's attention to the function of the second person of the Trinity or to the function of this Messiah who is Jesus. And he's saying that he came to reveal the glory of the Father, you know, who came and dwelt among us and we beheld his glory. That means he came to reveal the Father to us and he uses this word logos, which means word because the word is God is basically he's saying that this word is speaking to man about God. It is God revealing himself to man in the person of Jesus Christ. And this word is God manifest, which means God who is exhibiting himself, expressing himself in human form.  The word is God speaking to man. It is God revealing himself to man. It is Jesus who came to reveal who the Father is. And it is this word who is the manifest presence of the eternal God, which means it is this word who is God himself, who's revealing God, who's expressing or exhibiting or showing us who God really is or showing us who God the Father really is. So in the incarnation, the eternal logos became flesh. He dwelt among mankind.  But here it is the word flesh here is to be understood as somebody who's representing the fullness of humanity. That means Jesus was fully human. It was not that he took on just the structure of the outward form of a human body in whom deity existed or the nature and the characteristic of God existed. But only the outward form was of that of a human being so that people can look at God and understand God's nature. No, it was not just the outward form of a human being, but it was also, you know, the very nature and the characteristics of what we as human beings have. You know, so we will study about this in the next chapter where we talk about the humanity of Jesus, how he is fully human. But we need to understand that, you know, Jesus was not just outwardly in human form and insight in his nature, his characteristic, his attributes. He was completely God and had no human traits. No, he was fully human in the sense that he had the outward appearance of a human being and also had, you know, he represented the fullness of humanity, had the nature and the characteristics of human being. So the eternal logos, that means the eternal God, you know, took on humanity in the fullest sense, in all its fullness. So he, the flesh here is to be understood as representing the fullness of humanity, everything that we go through. And that is why it is very encouraging for us to know that God who became man can understand our friendlies, can understand our weaknesses, can know our shortcomings, but also raises us up to a higher level, a higher bar where we can say, hey, when God became man, he lived as a complete man, 100% man in the fullness of mankind, but yet he did not sin, yet he did not give in to the desires of the flesh. He did not give in to the desires of the carnal nature, which means that I have no excuse to, you know, to go back into sin or knowing that I'm dead to sin now, that sin has no power over me. I can understand that. I can take that as a truth. I can believe that and not doubt it because Jesus himself was fully human, was in the fullness of humanity, was dead to sin. You know, sin did not reign in his mortal body. Sin had no control over him. And in every way he showed us how, you know, being fully human, you can overcome sin. So sin is not something that is going to dominate reign in my life, overpower me, but I can say and declare and live as if to say I am dead to sin. So both of these aspects that can just come back to our mind, knowing that God understands what we go through. Sometimes we think nobody knows, nobody understands what we're going through, but God understands because he was fully human, a high priest who's interceding, who's a mediator of the New Covenant, he knows. And also it brings us up to that level that God expects us to live and placed us at the right hand of God as somebody who's righteous, the same level as Jesus Christ and God sees us in that same level that we are dead to sin. Sin has no control and reign of power over our mortal bodies. Okay. This word, the word became flesh and dwelt among us. The word dwelt, you know, literally in the Greek means tabernacle, which refers to the tabernacle in the Old Testament. You know, it was a tent of meeting even before the temple was made, you know, when the Israelites move from place to place, they had this tent of meeting where they had this, the Ark of the Covenant and God would appear to them or manifest his glory, speak to them, you know, and he's a cloud over that tabernacle. So God manifested himself, manifested his glory, which means manifested who he is and what he does among his people, even as they journeyed from Egypt to the promised land. And of course, after that we see him manifesting his glory in the temple. So we see that even as the people journeyed, you know, God lived and moved with his people in this tabernacle. So his presence was literally with the people, going with the people, because he dwelt with them, he lived with them. And we read about this in 1 Chronicles chapter 7, sorry, 1 Chronicles chapter 17 verse 5 where it says that God lived and moved with his people in this tabernacle. We also see that we read in Isaiah chapter 63 verse 9 in all their afflictions he was afflicted. So God did not just, you know, go with them, his presence was not just moving with them. But when they felt afflicted, you know, it was as if to say he himself was afflicted. That means, you know, he was so much part of his chosen generation, his chosen people, the people that he called forth, his royal priests, his priests that he set apart. You know, it's just wonderful to know that, you know, God was so holy and these people were constantly grumbling and murmuring and complaining and sinning against him. Even then God chooses to journey along with them. You know, his glory was manifested. They see his glory, who he is, what he does, his miracles, his power. And also in their afflictions, in their, in their troubles, in their, you know, difficulties, in their misery, in their pain, in their illnesses, he was afflicted. So, you know, also now we don't have this tabernacle. But, you know, as part of the new covenant, our bodies are the temple of the living God, the Most High God dwells in us. So, even as we go through troubles and difficulties and miseries and illnesses, you know, we know that God is there with us. His presence is there. He's a very present help in times of trouble.  He knows what we are going through. He understands, he relates to us because he's experiencing it himself, like he, it happened for the people in the Old Testament. So, in the incarnation, God came to dwell with mankind, just like he dwelt in the past. His very presence was there. You know, he dwelt with mankind. And that is why we see that, you know, he was also afflicted with their affliction, not only with the people of the Old Testament, also the New Testament. We see that, you know, every time Jesus was tired, he moved away to a solitary place and he was, you know, he was crossing the rivers that he could move to a solitary place. But when he comes to the other part of the shore, he sees the crowd just waiting for him. And, you know, it says that he was moved with compassion. You know, he was moved with compassion. He does not say, hey man, you know, I'm tired. I just need to get some rest. You people, just give me a break. Leave me. But you see that Jesus got on the boat and just ministered to people. When he, when you saw Mary and Martha, we view over Lazarus, he went when he saw the widow, you know, taking the son's funeral. You know, he was moved with compassion. So we see many places where Jesus was moved with compassion.  And after that, you know, I'm just going to do my job and go back. But he came to and he mingled with us. He understood our friend, these are weaknesses he ministered to people at the point of their need. And he had mercy and grace even in the crowd, you know, in that big crowd, he stops at the sycamore tree and he looks up and calls Zacchus down.   So we see his compassion. And so that is what means, the word means dwell. So when God dwells in us, you know, he's connected with us in every aspect of our lives, what we do, he's interested, what we say, he's interested. What's happening, sorry, he's interested what is happening in our lives and also, you know, what we, how we are living our lives. He's interested, he's mindful and he, you know, is very, very active. Okay, so look at what Isaiah chapter 60, the next, sorry. So we saw that the word became flesh and dwelt among us. We are meditating on John chapter one verse 14. We looked at what the word is, the word became flesh, what flesh, the word flesh meant. We looked at what dwelt meant, the word dwelt and also that we beheld his glory. Okay, now the Greek word for the word glory means doxa and it originally meant honor, reputation, reputation or esteem, which is given to a person.  The New Testament, the Greek word for glory, which is doxa is used to denote, again, honor, splendor and majesty, which is basically talking about, you know, God's honor, his glory, his majesty. So when you're saying that the word became flesh, we're saying that, you know, the incarnate one, the one who was God who manifested in human flesh, you know, is of divine spirit. Plender power, majesty and has to be ascribed glory and honor. Okay, so when Jesus walked on this earth, you know, one thing to understand this word glory is that, you know, he did not manifest the glory of God. If he had manifested the glory of God, then no one could see him. No one can look at him without human eyes, without naked eyes because, you know, the word of God says in 1 Timothy chapter 6 verse 16 that God lives in unapproachable light who no man has seen or can see.  So if Jesus came on this earth, you know, we say he was fully God, he was fully man. But in what aspects he was not, you know, he did not manifest the full nature of God is in one of these aspects, he did not reveal the glory of God, but he revealed the sonship glory. Because he revealed the sonship glory, you know, people were able to see it, people were able to see him, people were able to know who the Father is. And that is what, you know, when we read in John chapter 1 verse 14 says, who came, you know, in the flesh dwelt among us and beheld his glory, the glory as of the only begotten of the Father full of grace and truth. So when we, you know, talking about this glory that Jesus manifested or expressed or exhibited or showed when he lived here on this earth, it's not his glory of his deity, not the glory of him being God, but he manifested the sonship glory. And how did we know that he manifested his sonship glory? If you look at John chapter 17, which is a high priestly prayer of Jesus, if you just look down to John chapter 17, you know, here in this chapter 17, Jesus says, you know, Father, I have glorified you on the earth, I have finished the work. Look at verse 4 of John chapter 17. It says, Jesus says, I have glorified you on the earth. This is his prayer to the Father, so his eye is referring to Jesus. I have glorified you as referring to the Father on the earth. I have finished the work that you have given to me to do. And now, O Father, glorify me together with yourself with the glory which I had with you before the world was. And then he goes on to say in verse 22, and the glory which you gave me, I have given them that they may be one just as we are one. Okay, so here Jesus is saying, you know, I have in verses 4 and 5, Father, I have completed everything that you have given me to do. Now I'm just waiting for it to come back and to, you know, to be with you and to be glorified, which means to receive back the glory of that, you know, is connected with deity. Okay, with the glory which I had even before the world was, which means again it's referring to, so here is another verse of scripture where we can show that Jesus is God. Because he has the glory of God, which means he has majesty, splendor, the power of God, which he had even before the creation of the world. But when he came here on this earth, you know, though he was fully man in the entire sense, and he was fully God.  Why did he do that so that, you know, people can see him, people can see and know who God is, can experience God even as Jesus expresses himself and he goes around doing his ministry and teaching. If he had the glory of deity, the glory of God, then no man can see him because that is what 1 Timothy chapter 6 verse 16 says.  The sonship glory, he says, you know, I have given them, which means I have given people who believe in me, I've given the believers. Talking about them also refers to us as people of the new covenant that they may be one just as we are one. Okay, we're studying more about this in detail, but it's very important for us to know that, you know, Jesus lived here on this earth in the sonship glory, not the glory of deity. And the second thing is, you know, just look at, you know, another spiritual privilege, inheritance, a blessing that we receive is that Jesus has given us that sonship glory. And that is why Jesus says you can do greater things than what I have done because he has given us this sonship glory.  So who God is, when able to manifest the fruit of the spirit, what he does, we're able to manifest the gifts of the spirit.  The eternal word, this eternal God submitted himself to certain limitations, which for us is not very easy to understand or completely define. But he could reveal all of that or he could reveal what he could could reveal to us in the limitations of humanness and that is what we can perceive, what we can understand. And, you know, he limited himself in the terms of not having the glory of deity. And because he limited himself in that area, you know, he could reveal himself and we can see the revelation of God, we can see who God is. And, you know, and it's a ways and means in which we can perceive and understand, you know, God through our human intellect, through our fine, through us being finite beings. Yes, so God was, Jesus was fully God, fully man. He is God who became man. But, you know, he did not become flesh in the sense of seizing to be what he eternally was. So, which means that, you know, Jesus was completely God, he did not cease to be eternally who he was. But rather the eternal God, you know, took on the fullness of humanity. Okay, so he was fully God, he's eternally God, this eternally God became or took on the fullness of humanity, which means he had the spirit, soul and body. And he was fully man like any one of us. But, you know, he limited the manifestations of his deity. There were some limitations that he took upon himself so that, you know, we can perceive him, we can understand him so that, you know, he could reveal only what could be revealed in the limitations of humanness. Which means he took on, you know, he limited himself to certain manifestations so that he could reveal the Godhead or he could reveal who God is in the limitations of us human beings or in the limitations of humanness. Okay, we'll study Hebrews chapter one versus one to three and, you know, we learn some things about the word incarnate who is God speaking to us. We look at some facts regarding his incarnation. Before we move on, anyone has any questions? Any questions? I hope all of you are in class today. No one is asking any questions, no doubts. Is everything very clear? You've understood everything? May I ask you, are you able to hear me? Yes, yes, yes, Nina, John. Okay. I just wanted to ask that when he went through all the pain, because you've been saying that he did not cease to be who he is, but he limited himself to being fully human also. So then when he went through all that on the cross that he did, so we know that he was really going through all of that just as any human. I mean, would they have been, I mean, is there the deity involved there in the sense that he had the strength to bear that pain because of being who he is? I don't know, I wonder if my question is clear. Yes. So, yes, he was complete, that's why we say he was completely human. He took on the fullness of humanity, so he went through all that pain and suffering as a human being. But he did not use, another thing we need to study about this is when we look at Philippians chapter 2 verse 6 and 8. And where we read that he emptied himself. It does not mean that he emptied himself, not in the sense of laying aside his essential nature of deity, but rather that he willingly restrained in exercising or expressing his divine attributes that of omnipotence, omniscience or omnipresence. So we say that he willingly refrained, that is why we do not, in Christology we do not dare to attempt to talk about the how of the Incarnation because there are very puzzling things, but he refrained in exercising or expressing his divine attributes of being omnipotent, which means in his power he could have diminished the power of the human sufferings which he was going through. So he could have shown it physically that he was suffering, but inside he was in suffering because through his omnipotence he could have nullified all of that pain and all of those things. Omnipresence could mean that he could be present there on the cross, but he could be present somewhere else. So what we're looking at is just a form of his body there, but he's actually not going through all the pain and suffering. No, but what we are saying is when he emptied himself in Philippians chapter 2, which we read, it says that he did not lay aside his deity, a nature of being God, his characteristic, his attributes, but he willingly refrained in exercising and expressing them. So when he was hungry, he was angry, he was tired, he was sleepy, all shows his humanness and even on the cross when he went through it was because he was fully God, fully man, yet being fully God. Did that help Nina? Yes, thank you. Okay, so we look at Hebrews chapter 1 verses 1, 2 and 3, can somebody read that please? Hebrews chapter 1 verses 1, 2 and 3. God who at various times and in various ways spoke in time past to the fathers by the prophets has in these last days spoken to us by his son whom he has appointed there of all things through whom also he made the words, who being the brightness of his glory and express image of his person and upholding all things by the word of his power when he had by himself purged our sins sat down at the right hand of the majesty on high. Amen. Thank you. So here we see that, you know, it's qualifying what the apostle John is writing and introducing second person to Trinity, this Messiah, who is Jesus as the Logos and saying God who at various times and in various ways spoke in the time past to the fathers, you know, by the prophets, but in these last days he spoken to us by his son. So, you know, the writer of Hebrews is attributing and saying, Hey, this is the word. The word is the word incarnate that is God speaking to us. And it's also this word who through whom he made the worlds, you know, created everything. And he says, notice two facts regarding incarnation in this verses. The first one is Jesus is the brightness of God's glory. The second one is that Jesus is the express image of God's person. If you look at, you know, verse three, which we are just looking at Jesus is the brightness of his glory. The first part of verse three, who being the brightness of his glory and the express image of his person. If you look at this, the sentences, these phrases in the amplified Bible, it says he's a soul, soul means, you know, the one and only, the one and only the soul expression of the glory of God, and he is the perfect imprint and the very image of God's nature.   Okay, perfect imprint in the very image of God's nature. Look at what the Jerusalem Bible says. He's a radiant light of God's glory and the perfect copy of his nature. The new international version says he's the son is a radiance of God's glory and exact representation of his being and the little Greek Bible, the lexicon. Hebrews chapter one verse three says who being radiance of the glory and the representation of the reality of him. So Jesus, you know, two facts that we see here. The first one is Jesus, the brightness of God's glory, which means God's glory is manifested, is expressed, is revealed in the nature. Jesus is the manifestation of the nature and the attributes of God, which means the attributes and the nature of God is fully expressed, revealed, seen, exhibited in the person and the work of Jesus Christ. Jesus Christ is the expression of who God is what he does. He is a brightness, which means he's shining out the nature and the character of God. It's also brightness also reveals, you know, throwing light, which means revealing to us, making it known to us or it's very evident. When you throw light on something, things become very evident, things become very clear, things become very knowledgeable. We know there's clarity.  It's revealed, it's clear, can be easily understood, read and we can receive knowledge and information. It's the perfect revelation. And so Jesus came to reveal who all who God is and all who God is is shown in the person of Jesus is exhibited shines out through Jesus. He's also the express image of God's person, which means he's the perfect, complete representation. You know, he's the exact representation, the exact representation of the reality of who God is, the perfect copy, the perfect imprint of the living God. So, you know, Jesus is the perfect representation of the nature of God, who he really is. So in the incarnation, you know, we have a complete revelation of this living God, who we can, you know, we're beginning to know and understand who God is, what he is like, what is his nature, characteristics and attributes and what he does. So all of who God is, what he does is revealed to us perfectly in the person of Jesus Christ because Jesus is a brightness of God's glory. I explained that and he's also the express image of God's person. Okay. We'll just look at a little more about the image of God. Colossians chapter one was 15, the first part of that word says Jesus is the image of the invisible God. In second Corinthians chapter four was four, the latter part of the word says Christ, who is the image of God. So the word image means like we just saw exact representation, the exact revelation. It is a perfect copy, the perfect imprint of the image of God of who God is. So in the incarnation, it's the invisible God becoming visible. And this invisible God, who lives in unapproachable light, who no man can see or has ever seen, has made it evident to us as manifested himself, can be seen, can be understood, can be read through this clarity is because Jesus did not chose to lay aside his glorious deity and took on the sonship glory, which he gave to us. And that hence, he limited himself to certain things of the human nature so that we can perceive and understand God in the fullest sense. And that is why you see an incarnation, the invisible God becomes visible. And in Philippians chapter two verses six to eight, we will study seven steps in the incarnation. So again, one of you please read Philippians chapter two verses six to eight, please. Quickly. Philippians chapter two, six or eight, ma'am? Six to eight, six, seven, eight. Okay. Who being in the form of God did not consider it probably to be equal with God, but man himself of no reputation taking the form of a born servant and coming in the likeness of man. And being found in appearance as a man, he humbled himself and became obedient to the point of date, even the date of the cross. Amen. Thank you. So here we look at seven steps in the incarnation in this passage, very important passage of scripture. Christ was in the form of God. He was equal with God. He did not consider it to be robbery with God. He made himself of no reputation. He took on the form of a born servant. He came in the likeness of man and he was found in the appearance as a man. So we'll just study each of these in the sequence that it comes in this passage of scripture. The first thing we see here in verse six, Jesus Christ would being in the form of God. When you look at the Greek lexicon, the Greek Bible, it reads who subsisting in the form of God, which means who subsisting means living or existing in the form of God. Okay. Now this word form is the same word which is used in this passage that we read, the form of a born servant. It's not the same as mere likeness or appearance, which means that Jesus was in the form of God, which means that he was not somebody who was like a human being, or appeared as a human being, but he was fully human. But when we look at the same words, which the verses that we read, there's another form, another form, another word called form there. One in relationship with the form of God was two and the latter part of verse seven is as a form of a born servant. So the form of a born servant there was like a born servant in a pure like a born servant would be. That means Jesus was not a born servant. He was not a slave, but he was like a slave. He took on the role of a slave, but he was not a slave, like born as a servant. So in that sense form means like or appearance. But here when we are saying this form of God, the Greek word here for form of God, this is not the same as used for born servant when it's a form of a born servant. But here form of God does not mean that Jesus was the likeness or appearance of man. He kind of appeared like a man. No, he was like man. No, he was fully man. We can't say he was like a human being. He appeared as a human being. No, he was fully human being in the fullest sense. So we need to understand this, that the word form is not used to denote something that is just outwardly or external, but it's talking about the very nature, the attributes. So in his being, in his essential nature, in his attributes, he was fully human, just like he was outwardly human. In his very core fiber of his being, his attributes, his essential nature, he was as any other human being. So Christ, when he became incarnate, when Christ existed as God, possessing and being all that pertains to the divine nature, even as he was God, and having all the divine nature, even as he existed as a human being, he possessed all the essential nature and attributes of a human being. Okay, so we'll stop here and we'll continue next week. Anyone has any questions, doubts, any clarity on anything that was spoken or thought? No, today we went through a lot of content, you know, and I request all of you to please take time to go through the notes, to read through, to understand so that when you come to the next class, you know, if you have any doubts or questions, you can ask. And then we can also follow through the rest of what we are studying in Christology. Okay, thank you everyone for joining class. Sorry, thank you all for joining class. Have a blessed day ahead and a blessed week. The rest of the week God bless. Thank you.


This show was brought to you by these lovely people. Hey there, you beautiful NPR enthusiasts! Get ready for a show you'll want to watch again and again. We have a special show for you this time. It's all about projection painting and mapping for anime backgrounds. Welcome to the BNPR show! A celebration of stylized and non-photoreal rendering. Before diving into the main course, feast your eyes on these. Now let's see what's been brewing with some beer updates. We just released the first development update of the beer front end for malt. Beer's main goal is to allow shader creation fast, easy and intuitively using the LayerStack system. Development is handled by Alice Laurie or better known as atbees.mo on Twitter. There are nine milestones for the development. Currently, Alice has finished the first two milestones with these features. Beer layers, beer materials, beer panel, mask support, solo and mute layers, the 12 common blend modes and input layers that can use either the basemesh info or prior layer as the input for the layer itself. You can test beer right now. Please follow these instructions closely. There will be more development updates and soon we'll be able to help even the most beginner NPR artists create jaw-dropping materials. And as promised, projection painting and mapping. You have seen this a few times in our shows. So what is it and why is it so cool? Let's start with the projection mapping. It's a process of projecting a flat texture to some simplified mesh. Which means you do not have to add all the details to gain fidelity. Projection mapping is fun, but not as fun as projection painting. It's the same process, but you're painting in the details. In this last BNPR show for 2021, we will introduce you to the wild and fun world of projection painting, specifically for anime landscape backgrounds. You will need a few pieces of hardware to truly enjoy projection painting. First, a pen tablet with pressure sensitivity and a GPU with four or more gigabytes of VRAM. Let's quickly set up the simplest scene for projection painting. We need a plane and a camera. Subdivide the plane so that each face is almost squared. UV unwrap the plane. Now add a texture. Depending on your VRAM size, you may want to go one, two, or even four times the render resolution. Then add this material and set the texture to get painted. And now it's time to paint. Just kidding, April Fools. Well, I know it's December, but I mean, that's why you didn't expect it, right?  One, you cannot paint because the face direction is flipped. A flipped face is red when the view part option is toggled. Two, you might have skipped the UV unwrapping of the mesh. Please do that now. Three, you may not have the correct materials assigned or the wrong texture. Often this is the hardest part to figure out. If you have copied the material shown here, create only one texture and it is assigned on the material and you select the same material and texture slot, you should be good to go for painting. If you have more than one mesh, you might have been selecting the wrong mesh for painting. If the mesh is invisible, go to Object Properties, click the bounds to display the bounding box of the mesh. And now we'll let you know a few cool tricks. Trick number one, parent the plane to the camera if you want the camera to control the plane. Or parent the camera to the plane and let the plane control the camera. Either way, it should be fine for the next step. Trick number two, since we are in 3D space, we have a lot of helper tools. Since the canvas is transparent, we can use meshes behind the canvas to aid in composition and perspective. Trick number three, if we want our imagination to run wild, try this one. Using the World Grid plane, set up the horizon line, the view height and the vanishing points. A note, each time an object rotates, the vanishing points will change, so don't worry too much about them. Use the grid to plan the depth of the scene. Also, use it to vary the terrain while you paint. Trick number four, remember to adjust the focal length to get the best result for your landscape. When you're done with any of these tricks, remember to resize the canvas to fill the camera view. For this first painting, which has only a single layer, we'll look how to paint grass. For grass, regardless of length, you don't have to paint every single blade. I mean, unless you want to. But in NP-art, less time painting is more time to enjoy the better things in life. Here's one way to paint grass very quickly. Paint the grass zones. Make the zones fluffy. Now, paint a few grass blades. Reference real grass if you want to get the grass looking unique. Next, lower the strength of the brush on a gentle falloff and slightly tint the grass for variation. And just like that, you have nice looking starter grass. Does it look greener on the other side to you? Anyway, for the second painting, we have more planes to work with. With many planes available for painting, we need to make sure we're painting on the correct plane. Just pay attention to the indicator on the outliner. Yeah, this little guy right here. Okay, let's learn how to paint clouds. Set the falloff to full. Add a cloud texture. Set the texture angle to random. Add a little bit of jitter on the stroke. And change the material transparency blend mode to alpha blend. Now paint a cloud shape. For the shadow color, set a lower brush strength. And then poof, you got a cloud. For the third painting, the whole scene is 3D now. A 3D projection painting gives the most freedom with a minimal mesh manipulation. Try saying that three times fast. One key advantage, unlike painting on flat planes, we can still change the composition later on. But a note, please pay attention to your VRAM while painting on many meshes. You don't want to run out of VRAM mid-painting or blender will crash. So make sure to save often. If you are close to running out of VRAM, save the painting, close blender and reopen the file. Your VRAM should be lower every time you do that. Let's learn to paint foliage. Add a leaf texture. Set the mapping to view plane with rack and random turned on. For the stroke, we need a little bit of jitter. With brush strength of 1 and a pressure off, we can start painting the foliage. To paint the inner part of the foliage, lower the brush strength and use a soft fall off. Turn off effect alpha. Do not paint the shadow too flat. When that is done, we will paint the bright side again. Make a hard fall off, add jitter to the stroke and add the texture with rake and random enabled. Now you know how to paint basic foliage. So with clouds, grass and foliage, these are the basic elements of any anime style painting. If you want more, we have a mini anime background painting course with all three scene source files included so that you can ogle at how these paintings were painted. You'll also get the textures and tips on getting the right brushes to handle background paintings. But we will not leave everyone empty handed in this video. Here are three very important tips to make your paint anime backgrounds quicker. One, fill a huge area with few colors quickly. Then vary the hue in the area. Two, don't paint one object with too many details and another object with too few details. Always use colors or shapes as hints when you need to paint repeating objects. And three, the most important tip, don't forget to save. You do not want to repeat a painting if Blender decides to crash. So now, open Blender and start painting those anime backgrounds. Please get the mini course while you're at it. Cyber Katsu 2 by Dylan Gu. Someone turned up their production quality a few notches. The colors. The few names working on this bought our color e-book, specifically this book. Suspicious, isn't it? Huh. Modern Siren, music video by Chunmu Studio. The shading is done via Eevee and Malt for the outlines. The ocean modifier was preferred for the ocean for its lightweightness. Meanwhile, Mantaflow was used for splash effects. In the tsunami shot, the ocean modifier and lattice modifiers were used to simplify production. Work smart and not too hard. Very nice. Blown Apart. Be Branding Blitz by Tiny Media. Oh my, Tiny Media. Whoever read the script, double thumbs up. Smooth. Go watch it if you have not. You probably know what we're going to say here. Please go to the You Got It, the show notes. We've got a lot of goodies in there. And the show is made possible by these kind-hearted people. Please thank them kindly. Before we go, one final question. Do you have an anime background that you've always wanted to reproduce?


We got the mics on. All right. Good morning. We're going to get started here shortly. Thanks for joining us this morning. I'm Jesse Proudman, CTO of Blue Box. And I am Shamal Tahir, IBM Private Cloud Offering Manager. And we're here to talk about OpenStack for beginners and to kick off the IBM Cloud Client Day. Thank you all for coming. So Let's start with the history of OpenStack and where it originated. So a long time ago in a city far, far away, Austin to be precise, OpenStack was created and launched by a joint project through NASA and Rackspace. So in 2010 the project was created and in the beginning OpenStack had object storage and compute services. But then as the needs for those services from a, you know, elastic provider perspective grew, more and more companies and contributors started joining and contributing code and eventually we realized that, you know, SUSE, for example, announced the first public preview in 2011. By 2012 there were more and more contributors to OpenStack coming up and so the need for a foundation was created. And so in 2012 we took the project that was started by NASA and Rackspace in 2010 and we made it into a open foundation, the OpenStack foundation as we know it today. Also, in 2012 Red Hat introduced their OpenStack distribution. In 2013 Oracle became a sponsor and 2014 Helion was announced. So as you can see the trend is that we've had growing number of community and as of 2015 we have over 3,900 developers and about 31,000 members in the OpenStack foundation community. So it's interesting to me about this history is that you can see from very early on you took an open source project that had a pretty, pretty good community contributing and very quickly grew commercial support, not just from one company, like we often see in the marketplace today with other, other open source projects, but from a whole diverse set of companies. So the need for OpenStack, the need for this type of technology was evident from very early in its evolution. Absolutely and I should mention that in 2012 when the OpenStack foundation was created IBM was a platinum member from the beginning of the Foundation as well. Absolutely. So IBM was in since 2012. So I'd love Jesse to explain you know when BlueBox joined OpenStack and what the drivers were there. So BlueBox was founded in 2003 and the company grew up as a managed hosting company. So we were helping our customers deliver their applications to their clients. In 2010 we began to see a shift in the marketplace and a shift in customer demand. Customers were beginning to ask for self-service as the result of what was happening in the public cloud space. They were asking for APIs. They wanted to automate their infrastructure. At the same time we saw those customers looking for a private cloud solution, something that wasn't shared amongst the many other customers. And so in 2013 we launched what we call BlueBox Cloud at the Hong Kong OpenStack Summit. BlueBox Cloud at that time was a hosted private cloud. So it was a dedicated offering to a single customer operated out of our data centers. We had four globally delivered to the customer where BlueBox managed all of the OpenStack all the OpenStack operations for the customer and the customer just worked with OpenStack. At that time we were on the grizzly lease and the offering has been evolving ever since then. Thank you. So let's talk a little bit about what were the business drivers that customers were seeing that made them think that you know cloud is the next platform for our data center and our evolution of how we leverage technology for our business. So the data points here by the way are from the OpenStack Community User Survey. And so every release OpenStack does a survey where they ask the community operators of OpenStack and consumers of OpenStack services what do you use an OpenStack and why do you use it. And so from that perspective one of the notions that was early on within the OpenStack and OpenSource Cloud movement was it's a cost saving initiative. And it is cost related but really the true power of cloud now that we're more mature in how we're enabling it integrating into our business has become the increased operational efficiency and the agility that it provides. So saving money is good agility and being able to build better products, more scalable products and faster time to market is the real driver behind cloud. Well that's interesting when you think about saving money what does that actually mean. I think many people originally looked at OpenStack as a way to save money on VMware licenses or other virtualization platforms. And sure if you can tolerate sort of the cloud native aspect of OpenStack that's a viable replacement. But at the same time there's an opportunity to use OpenStack as a platform to build your next generation applications, your cloud native applications directly. And it is through that process that customers are really saving money. Being able to build, deploy and operate an application in a much faster mechanism because of the power of OpenStack and its APIs because of the cloud capability that it delivers. That saves customers money. And I think it saves customers more money than just trying to replace existing infrastructure. We were on a panel yesterday where we were talking about is OpenStack a replacement for VMware? Does it collide with what VMware is doing? And I think the answer is no. I'm a big believer in it. If it's not broke, don't fix it. And so customers don't want to spend the energy to move something off of VMware that's already working. But they do want a platform that can sit adjacent to that VMware infrastructure that can sit adjacent to their existing data. And they can build net new applications on top of. And that's what OpenStack can provide. So now that we've talked about some of the business drivers, let's talk about some of the actual business applications that people are building on top of OpenStack. And so throughout the years we've had, as you've seen actually in the OpenStack conferences, every year more and more users are actually part of the keynote. In the beginning it used to be the foundation and vendors and now it's actually the users that drive most of the content during keynotes. And a lot of that is because now OpenStack is being applied technology to actual business problems. And so from that perspective e-commerce is a very well-known use case. Subu Almanjaro from PayPal is the user committee lead or chair now. And so eBay is using OpenStack daily. There's other retailers worldwide that use OpenStack for hosting sites that literally get millions of hits per day. So companies like Walmart from the United States, Target, these companies have decided to base their e-commerce platforms on top of OpenStack and make a tremendous difference to the velocity of their business. Absolutely. And another interesting one that's new is this notion of agile platforms for applications. So in the last keynote in Vancouver we had a company called Digital Flimtree come on stage and talk about how they're doing a digital supply chain for video editing, production and delivery using OpenStack. And actually one of the big enablers around that is the new federate identity feature within OpenStack itself. Being able to have intraoperable clouds that have common API and common response to be able to work on applications and data sets in one cloud and be able to use those same applications and data sets in other clouds as you move from vendor to vendor in your supply chain workflow. Digital Flimtree I think is a fascinating customer in that they're using OpenStack in a way you may not think about. So I had the opportunity to go down a few weeks ago and meet with the CEO of Digital Flimtree and hear more about their experiences. Digital Flimtree edits many of the popular TV shows in the US and they collect a lot of video footage for each show that they're working on. They're able to take that video footage and it's all a file based workflow now, so no longer on tape, it's all digital files and they're using Swift from OpenStack to store that data. But they're not using Swift from a public cloud provider. They've got Swift installations that actually sit in their office where the production work is done. They've also taken Swift and put it on an appliance. So if they're shooting a TV show in the field, they could take that appliance out in the field and actually put it next to where they're shooting. And so OpenStack doesn't just mean a private cloud in somebody's data center. The technology is flexible enough that you can use individual components to change the way your business operates. And I think that's a pretty exciting component of what's going on in the OpenStack space today. Absolutely. And this is the part I love about OpenStack is, you know, it's just not doing the same existing business applications and processes. It's adding new capabilities and new processes that we might not be able to even imagine in the past. Opening up new doors that weren't available before. Exactly. And the other point I want to make about this one, as I mentioned, Federated Identity was one of the enablers for this type of a unique use case. And so BlueBox was one of the first 15 companies to commit to supporting Federated Identity to have interoperable OpenStack clouds. And so over the next year, I think you'll begin to see those product offerings are allowed from those 15 different companies. That release will begin to allow companies to use multiple vendors, all powered by OpenStack, to deliver their applications and to share a similar set or same set of credentials across all of those offerings, which makes OpenStack and all of its global points of presence, whether it's from BlueBox and IBM or from other vendors, a lot more flexible than some of the other offerings in the market. So moving on to the next use case. This is another popular one, which is HPC. And so, again, in Vancouver, we had another user, CERN, come on stage and talk about their environment. And CERN actually operates the LHC, the Hydron Collider. And they actually do research and data analytics on those collisions on some OpenStack powered clouds. And also CERN is known for their scale. Their cloud is upwards of 50,000 cores plus. And so HPC has been a long-standing use case. And we all know how intensive HPC can be. Well, and it's fascinating to look at the projections that CERN is considering as they think about all the data that they collect and analyze. So over the next ten years, the scale that they'll require far exceeds that 50,000 core count into the hundreds of thousands of cores and petabytes of data. And having selected OpenStack as their platform, they are highly motivated to work with the community to figure out how to continue OpenStack's capability to support that type of scale and that workload. And then the last workload that we want to highlight is, you know, the cloud-native workload that Jesse mentioned earlier as well. So enabling web services, enabling web applications at scale, distributed, oriented in a microservice architecture, OpenStack was built with that type of application architecture in mind. So it's naturally suited to basically build the next unicorn. You know, we see this type of deployment with a lot of our customers and a lot of our prospects. Particularly with the Blue Box Local product that we announced yesterday where we can put a private cloud in a customer's data center. This type of deployment allows customers to build their next-generation applications, but have those applications talk to their existing system of the record, their existing databases, their existing file stores. And so you're able to leverage the investments you've made today, but build your next-generation applications in a modern architecture to be able to future-proof your investments. We see this in banking, we see this in healthcare, we see this in finance. Those types of organizations may not be able to move their mainframe systems, may not be able to move their transaction engines, may not be able to move their customer data stores from where they are today on premises into the cloud, but they want to be able to leverage OpenStack. They want to be able to build new generation applications using cloud. And this type of approach solves that problem. Absolutely. And so we've explored maybe four or five different use cases that OpenStack has been applied to business problems. In reality, because of its flexibility and versatility, it can be applied to probably a hundred different more use cases that we don't have time to cover right now. The other thing to add is because it is SilverStole, it's a foundational level service, so as you develop applications like web services, you know, you get into BlueMix, and even BlueMix can benefit from OpenStack underneath it, so. Absolutely. So now that we've talked about the value, and you know, we're all excited that this actually makes sense from a business perspective, so getting started should be simple, right? Let's go make this happen and harness the power of OpenStack. Well, that's been the challenge historically, is it's not simple to start. And the challenge has been, in the past, OpenStack used to have what they used to call the OpenStack integrated release. And that meant that you had projects that were tested with each other to make sure that they didn't break each other's code as they were enhanced release to release. But because the term was integrated, people often thought that I had to download and use all of those projects together. And trying to install all those services when not all those services were needed, made OpenStack really complex from an installation perspective. And this is where, you know, basically a lot of distributions popped up saying, I can help you with the deployment challenge. But as we know, and as Jesse will expand on, deployment was not the right problem to solve, it was operations all along. So if you look at the historical approach to using OpenStack, there have been a couple of methods. The first was to go take the open source packages, the open source available in the repositories, download that and install it yourself. And you see a lot of organizations started out that way, and even some of the largest organizations today still use that approach. The challenge with that approach is that the packages and the software that is in the repositories aren't necessarily architected or configured for the way you need to operate your clouds at scale. Doing highly available deployments, those take sort of a preferential approach that doesn't necessarily come with the source code. So the next thing that occurred was the advent of the OpenStack distribution, taking OpenStack and selling it a software. So in that model, a distributor would take the open source packages, they would put their preferences and configurations into them and ship out those packages to end users. The challenge with that is that it may make installation easier, you may be able to get up and running faster, but the ongoing operations of that environment ultimately still fell on the customer, on the end user. So this is the classic at 3 a.m. when the cloud falls over, who do I call problem? And with just a Linux distribution or a single piece of software, it was less impactful when that system failed. If you had one server down, that may only impact a portion of your infrastructure. But as we think about cloud, most of your infrastructure now runs on that environment. And so when it fails, it can take down your entire business. And so we like to call this the blast radius. OpenStack and a private cloud has a much larger blast radius than a single piece of software. And so that software distribution model didn't solve that operational challenge. And so two or two and a half years ago, you started to see a new model emerge in the marketplace. Bluebox was doing this, MetaCloud was doing this, and more recently, you see companies like Platform9 offering a similar type of implementation, where the vendor does the installation and operations of the environment, and the customer simply gets to work with OpenStack using OpenStack, benefit from OpenStack, without having to worry about OpenStack itself. We call this private cloud as a service or OpenStack as a service. And we think that's the best way for most organizations to consume OpenStack to get the benefits of OpenStack. Couldn't agree more. So let's talk about three takeaways from what we've talked about so far. So the first thing is, as we've talked about already, we talked about the history originally about OpenStack and we said it had compute service and object store. At this point OpenStack, and I'm not even going to go full exhaustive list, has compute, it has object, it has block, it has network, it has message queue, it has DNS as a service, it has workflow as a service. There are so many different components, which is great because as we were talking about, this is what enables the diversity of applications and use cases that OpenStack can support. But flexibility and having this much versatility also leads to complexity. So we have to balance the benefits with the complexity and this is where the private cloud as a service model really shines. I think it's also important to remember that just because OpenStack has all of these projects doesn't mean you actually have to use all of these projects. So if you think about the way OpenStack is organized, there are a set of primitive objects, things like networking, storage and compute. Those will likely be part of your deployment. Those are the essential part of your deployment. But you don't have to when deploying those, take all these additional services. You can pick and you can choose and you can figure out which of those services actually brings maximum value to your business. So the next thing is we have an expression that says you don't want to see how the sausage is made. And so this applies to cloud as well. You can run a cloud, you can operate a cloud, but to be honest, the skill sets that you use to operate a cloud from a distributed systems perspective, from a Python language perspective, those skill sets could be used to benefit your business and generate revenue for you versus support your operations for you. And so this is why you don't want to see how the sausage is made, but you want to be able to enjoy the variety of sausage that is available. So we like to think that it's important for an organization to look at where they believe they can get the most value from the effort that they're putting into their cloud deployments. If you can get the most value from deploying and managing your OpenStack footprint, and some organizations can, many of them are technology companies, then that's a path that's worth exploring. But if you think you can take that same team and have them focus on building your applications, your applications that actually differentiate your business in the marketplace to make your business money, we believe that's a better place for organizations to spend their time. That's the whole premise of public cloud, that somebody else is worried about the infrastructure, that somebody else has figured out all the technology challenges. And so we believe that we can make private clouds have a similar experience to public clouds, but sit in your data center or be dedicated to you in a soft layer facility. Absolutely. And last but not least, as you've seen in the key notes that have occurred and the Liberty release material itself, Liberty is the first big tent release of OpenStack. And what BigTent means is that OpenStack, as long as you are a project team that will adhere to the four opens of the OpenStack community, which is open design, open source code, open discussion, and generally having open communication lines, we will welcome you into the OpenStack family of services. And so with that, that's also going to increase the flexibility and capabilities of OpenStack, but again, it is going to be exponential in terms of the impact it has on the variety of options you need to choose from. And so you can see that even at this summit. So Akonda open sourced their project Astario into the BigTent at this release, which means that we're going to begin to see many more projects entering the OpenStack project space. And so instead of just having an understanding and a comprehension of say 30 projects, that might be 60 or 90 in three to four years. And that adds a lot of complexity to the story. It also adds a lot of flexibility. So it's both a good and a bad thing. And we're looking forward to seeing how that plays out in the OpenStack community. Absolutely. And the project navigator that they announced this week, that is going to be a really great tool as you're learning about OpenStack and the capabilities it offers, I would encourage you to check the project navigator because it has a representation of what services are out there, how much adoption do they have in production, as well as how many different distributions support that service in their OpenStack packaging. So it's just a good amount of data for the maturity of a service. And so that project navigator is available on the OpenStack Foundation website at OpenStack.org. It's in the navigation up top. I encourage you to go check it out. It's a great way to learn more about all of these individual pieces. Absolutely. And then the other piece I would like to add is, as Jesse and Angel highlighted in their keynote, it's Hello World.  And so what makes OpenStack great is everyone participating in the community. And so what I would like to highlight here is generally, OpenStack does need developers and contributors. As I mentioned, we have about 3900 going on 4000, which will be another milestone for the OpenStack community. But there's business users, there's people that write applications on top of OpenStack Power Clouds, and we want all of those people to participate in the community so we can understand how OpenStack is being used to make your business better, as well as how can we make sure that the user experience in OpenStack continues to evolve. And so from that perspective, there's a ton of different ways you can get involved in the community. Whether it's joining discussions in mailing lists, IRC, whether you share, if you use OpenStack, there's a super user publication where you can share how you're benefiting from OpenStack. We encourage those shares because again, as new people look at OpenStack, those stories help them understand how can I benefit from OpenStack. And so I will be here a little bit after this session ends and if there's ways that you want to understand how you can get involved, I'll be glad to answer those questions as well. Some of the other notable aspects of what the foundation have been working on are things like the user survey, which comes out every six months. And so that's an opportunity for those who are working with OpenStack to provide feedback on what they're using, what they like, what's working and what's not working, which is pretty critical for the foundation and the developers to be able to know where to prioritize efforts. If you think about a regular product or service offering that's provided by one single commercial entity, that entity has a product management capability that's talking to customers, that's talking to the users of that offering. Because OpenStack has so many commercial offerings as an open source project, it takes a lot more effort for the foundation and for the developers to actually know what's going on. And so there's a product working group that's focused on those user requirements. And as Mark noted in the keynote yesterday, the way OpenStack is being architected, the projects that are being worked on in the future, and the bugs that are being fixed are now beginning to be directly derived from the users of OpenStack, which will make the offering much better for those end users. Absolutely. So thank you so much and with that, Jesse, I don't know if you have any closing thoughts, but I think we're done with the content. Really appreciate you all joining us this morning. We've got a whole schedule of IBM Client Day talks here in this room, so we look forward to having you join us throughout the day to learn more about what IBM is doing with OpenStack and the offerings that we have. And look forward to sharing the rest of the week with you. Thank you. Thank you.


It feels really nice to be part of Jury, I think it's a great opportunity to witness some of the finest, some of the most creative work that would have happened over the last year. Definitely in India as well. TV share of the total advertisement spend in the world has been seeing a declining trend over the last few years. Maybe just not yet in India. India has done a good job. India TV market has done a great job in terms of just holding on to its share for now, but I think it's a matter of time. It's just been a flat curve for the last few years. It's not been growing at all. I think it's a matter of time that this global trend sort of catches up with India as well in that context. I think this initiative from Exchange for Media to recognize, to encourage all the great work, I think it's a great initiative. And I'm really looking forward to, with a lot of curiosity, to see all the entries and let me wish you all the best with all your respective entries. May the best campaign win. Thank you.


Dear students, in this module, we are going to talk about the social significance of the life course. The life course refers to the different stages and transitions that people go through as they get older. So life course is not something that has to do with your current age or current stage of life. It is a lifelong process and an individual goes from a lot of different stages throughout the life. So, sociologists study how the stages and transitions are shaped by social factors such as culture, institutions and historical context, childhood, adolescence, adulthood and old age. These are different life stages and a life course can have very significant consequences for the later life of the individual. So life course is significant because it helps to shape people's identities, social roles and their relationships. In life courses, opportunities, events, all these things are decided together or defined that in the next life, how you are going to behave, what your personality will be, what opportunities will be for you and overall how your personality will be. So it also affects people's access to resources and opportunities throughout their lives. So keeping in view that different stages in the life are going through or are passing through different processes of socialization. So life courses are important to understand for the sociologist or for the sociological analysis.


Hey everybody, what's going on? I am Greg Sussman joined today by our own game, Marency. She's got a six pack of picks for you. Hopefully they continue to be as hot as they have been. What's happening, Gabe? Well, let's crack the six pack open, Greg. Last week, we took Ditka's crew against the Norsemen and we see no reason not to go back into the woods once again this weekend as both the Bears and the Raiders head overseas second consecutive year that the Raiders play in London. It didn't end well for them last time. They lost 27 to three. I don't know what it is with the Raider organization. The more things change, the more they stay the same as they've been jumping from city to city in their entire franchise history and they seem to like to hire coaches that hate to fly. Of course, John Madden famously traveled the country in his RV, grew it and hates flying. Hates flying. He flew to Belarus for his son. You know, his son's a power lifter, right? He flew to Belarus for a powerlifting championship. He had vertigo for like a month after, no joke. Gruden has already some problems, right? Gruden can't sleep as it is. He's got a lot of little quirks about him and he hates flying. The overseas trips freak him out. They got tattooed last time. I see no reason it doesn't happen again. And oh yeah, you know who's on the Chicago Bears? Khalil Mack. And oh yeah, it's very refreshing that Khalil Mack's not saying that it's just another game, that he's saying yes, I want to terrorize them. I'm out for revenge. I don't like the way that it was handled. And yes, I have this game circled. If he has it circled, I have it circled as well. It props to the Raiders for winning last week in Indy, but they're not covering two weeks in a row on the road. They're three and seven against the spread in their last 10 trips away from the black hole. And we'll wrap it up with this guys. These London trips are interesting and the better team generally wins. And when I say generally wins, like almost always wins. Favorites are 24 and one against straight up and against the spread, they're pretty damn good as well. We always talk about how if a team's gonna win again, they're probably gonna cover the spread. So let's cash this 18 and seven against the number and the 25 trips favorites are to England. Let's make it 19 and seven as the Bears get it done and the Bears cover the number. John Gruden hates flying. He's got these weird quirks as Gabe says. He also doesn't love winning because he doesn't do it all that often. The Raiders not gonna get the job done in London this weekend. Another one of Gabe's favorite bets is in regards to Teddy Roosevelt himself, Teddy Bridgewater. Gabe, you've been talking all week how this guy's a winner. He may not be flashy, but he has the Saints on his back winning football games. That'll be the case again this week. I think we're getting some value here with Teddy Bridgewater and the New Orleans Saints against the Tampa Bay Buccaneer team that everybody just saw hang 55 on the Rams. You know what else happened in that game? They also gave up 40 points. They also gave up over 500 yards in passing. And this is a trend right now. And in fact, if you look at the Tampa Bay Buccaneers on the season, they've given up 31 or more in three of the four football games that they played. We saw Danny Dimes light them up a couple of weeks ago. A much will be discussed about Tampa Bay going into New Orleans last year and winning. They were different teams. It was Drew Brees versus Ryan Fitzpatrick. And you think that the Saints don't remember that game as well. If Drew Brees was the quarterback in this game, we'd probably be laying six and a half, seven points, if not at least a five and a half. We're getting value here. Say what you will about Teddy Bridgewater. We're not playing fantasy football. We're playing a reality football. And you know what? In reality, Teddy Bridgewater's got a better winning percentage than Drew Brees does. Now, 25 and seven guys straight up as a starter in the National Football League. I'm not getting in front of that. I like the New Orleans Saints. We'll lay the three points in this contest. Saints win and go marching into the winner's circle once again. Jumping on the back of the New Orleans Saints has made us some money thus far this year. Let's keep going. Teddy Bridgewater's a winner. It's all the Saints this weekend. He's been all over Danny Dimes here this season over the first two games. Now the Giants are hosting the Minnesota Vikings and Kirk Cousins. Defond Diggs out of a feeling. A lot isn't right in that Minnesota locker room game. Are you backing Daniel Jones again? Oh, I want to do it. Oh, I want to do it. Danny Boy. Oh, Danny Boy. Danny Dimes the man. You know, this is a stat from the Marency database. You know what Daniel Jones is? He's undefeated. He's 2-0 straight up and ATS is a starter. That's right. He's covered both games and he's played in. I'm not going to lie to you. I'm going to have a small piece of the Giants in my pocket on Sunday afternoon, but I'm going to give you the over of this football game. I always tell you about the Vikings dominance against non-division opponents. I really don't want to get in front of this, but at the same point in time, do you trust Kirk Cousins laying five and a half points? The good thing about freedom is you don't have to bet on every side and total. We can pick our spots and we're picking the total in this football game. I do think the Minnesota Viking offense is going to get on track a little bit here. If you look, they put up 28 against the Atlanta Falcons. They put up 34 against the Raiders. The two games that they struggled in were road divisional tilts. And to truth be told, to Kirk Cousins' defense, a lot of quarterback struggle against the Chicago Bears. Life's going to be easier. And it's good news, bad news for the Giants. Great news that Danny Dimes looks like the real deal, although this is going to be his first big test. Bad news is, Saquon Barkley goes out as soon as Danny Dimes arrives on the seed. Ogletrees still hurt. Now Conley. Conley was a key part of their linebacker core. Linebacker core, they're quite frankly, it's not that good to begin with. Dalvin Cook should have a pretty big day here. I expect the Vikings to get into the high 20s. But the New York football Giants get Golden Tate back. And you know what? Golden Tate is a veteran player. He's also a very good blocker as well. He just brings some physicality to the Giants' offense and some veteran presence into that huddle. I like the addition. I think they're going to go back and forth here. I'm not talking full track meet, but hey, 24-21 gets us the over. I'm going to give you the over in this game. I'll probably sprinkle on the Giants, but our official bet will be over 43 and a half. I think the number's just a little bit too low. We're getting value because people are down on the Vikings' offense right now. People have been all over the Vikings' offense, gave that they don't throw the ball enough against this Giants' defense that is certainly vulnerable in the past. We expect Kirk Cousins to get it going with Adam Field and Staphon Jakes. We already know what Daniel Jones can do with the Giants. 24-21 is not a lot to ask for. Hopefully we get it on Sunday.  And the questions are really going to start to be asked. Massive game for Kirk Cousins here. Give me the over. Give us some points. Up next, game we go. Well, of course, it's a Buffalo where the Buffalo Bills are going up against the Tennessee Titans. Josh Allen's availability is still a question mark right now. You buying Matt Barkley? You know what? I'm going to buy the total once again in this football game. Although I want to take the Buffalo Bills in this spot, if there's one thing we know about the Tennessee Titans is they're inconsistent and erratic. Every time you think Marcus Mariota has turned the corner, Marcus Mariota will have a subpar football game. Every time Marcus Mariota plays terrible, he plays great the next game. They're very, you know, they're almost easy to figure out in a sense. We have some real data here between these two teams. All right, guys, as they played last year, they played in 2015. I think they played in 2014 as well. And long story short, the last three times these two teams have played, the games have been decided by exactly one point every time. Let's use last year as an example, 13-12. You know what the total was last year? 38 and a half, exactly what the total is here in this football game. 38 and a half is really low for 2019 in the modern national football league. But generally you'll make money if you bet the highest total is over and the lowest total is under. It's under for a reason. As I mentioned, it was 13-12 last year. They're pretty much the same football teams for the most part. It doesn't really matter who the quarterback is or the bills, their offense won't be that much better or worse either way. And I'll tell you what, the bill's defense can stop anybody as we saw them shut down Tom Brady last week. Sometimes let's not overthink things, guys. The Buffalo Bills are 4-0 to the under on the season. The Tennessee Titans are 3-1 to the under on the season. They played last year and it was 13-12. The time before that they played, you know what the score was? 14-13, give me the under 38 and a half. Feels like the Osmakers just giving away money here. This game always is under between these two teams. Buffalo and Tennessee certainly not know if they're offense. This week we expect it to be under once again. Tennessee's defense has been really good too. They're only giving up 15.8 points a game. Ironically enough, the exact same number of the bills defense is giving up. It's gonna be an old-school smash-melt football game. I like the under, guys. Up next, Sunday Night Football. Kansas City Chiefs and the Indianapolis Colts. Colts lost at home last week to Oakland or big-time dogs against Kansas City on Sunday Night. The game, you're buying the indie bounce back. Well, I'll tell you what, exactly. One of the reasons why I like the over in the Minnesota Viking game is because we're getting a very low number. I'll tell you what, Wall Street is right down the street from us and I'm not a finance major, but I understand about buying low and selling high. We're getting to buy low right now on the Indianapolis Colts. They're getting just a little bit healthier. Keep your eye on T.Y. Hilton in this spot. They got a buy week coming up, so it'll be interesting to see whether they take the cautious route. But the fact of the matter is, I think they're gonna be able to trade points with the Kansas City Chiefs. Just a few too many points when we get into the double-digitness of this.  And the fact of the matter is the Colts offense has been fine. The fact is, they haven't had any luck parting the punt on the defensive side of the football. Offensively the Colts are putting up 23 and a half points a football game. Problem is they're giving up 25 and a half points and 25 is the key here guys because the Kansas City Chiefs have scored 25 or more points in 25 straight games. An NFL record. So we almost have a starting point here, don't we? Well, we know the Chiefs are gonna get to 25. The Chiefs are probably gonna get to more than 25, aren't they? Chiefs are probably gonna get to what? 34, 37, then therefore we're really not asking for all that much to go over the 56. In a track meet of a football game in which both teams go back and forth, I want the double-digit points. I think the game goes over the 56 as well. So give me the Colts plus the 11 and over 56 guys. A lot of points are gonna be scored as they always are when Patrick Mahomes takes the field. This week against Indianapolis we'll see if Jacoby Percet, leading the league in touchdown passes can do his job. Percet just needs to hang in there to cover a massive, massive spread. A lot of points are gonna be scored in this one as they always are when Patrick Mahomes takes the field. It's the other side that we're concerned about. Can Jacoby Percet, who's near the league leaders in touchdown passes do his job? That's a question that remains to be seen. But 11 points is a large number. All the Colts have to do is survive and of course do their part to go over. That's gonna do it for us here on the Fan Real Hurry Up game. It's been a blast. Let's keep winning. May the winners be yours. Have a great weekend, everybody. Enjoy the games. Gabe and I will be back on Monday to preview Monday Night Football.