Thank you. So my name is Dave Klein. I'm a developer advocate with Confluent, and Confluent is a company that was founded by the co-creators of Apache Kafka. And so we're going to be talking about Apache Kafka today and how to use that with Python to build event-driven microservices. If this thing all works. There we go. Okay. So we'll start off by talking about what do we mean by event-driven in the sense of microservices or event-driven architectures in general. Well, I don't want to cover all that, so there's a guy already did, Martin Fowler, who's brilliant. He's got a great blog post and a corresponding conference talk that's recorded that you can check out. And he goes over four patterns that he's identified that you can see that are commonly associated with event-driven architectures. And I will mention them briefly. Wrong button, sorry. The four that he came up with were event-driven notification, which is very simply just an event happens, is posted, and something else consumes that event and says, okay, I have to do something now. It's like a trigger, basically. And then that responding application has to go then and get whatever information it needs, usually from a database to get to do what it needs to do. The next one is event carries state transfer. And this is Martin's own term, kind of poking a little fun at rest. But the idea here is that event is raised and the information that corresponds to that event goes along with it as a payload. And then the consuming application receives that event, has all the information it needs, theoretically, to do the work it needs to do and doesn't need to call back to the calling application. Then he goes into event sourcing, which is a pretty big deal. That's where basically all of your state comes in as events. And you can rebuild your state at any given time from your event store. And then CQRS, which is Command Query Responsibility Segregation, which is on the fringes of events stuff, and that has to do with having two different models, a read model and a write model, so you can optimize each. We normally try to optimize everything to do both, but this idea is that you have one model, one system for commands, which is things that are going to change your state, and another one for querying that. And that's another really big topic that I'm going to talk about today. Today I want to focus on the second one, event carries state transfer, because that's the one I think is very valuable for building microservices. Yeah, so, but we're going to be doing this in the context of Kafka. And since this is a Python conference, I figure you all know Python, probably better than I do. I won't be working for less than a year now. After many more decades, and I'd like to mention you doing Java, I have to say that working with Python has been a real breath of fresh air. But since you may not be familiar with Kafka, I'm going to give you a little bit of an intro to what Kafka is and how it works. So at the core of Kafka is the event. Kafka is an event streaming platform. And so an event is a logical construct, but what it contains is basically notification and state, like we mentioned earlier, right? So notification tells us something happened, like an order was placed, and the state is the information about that order. And that's the information that we would need to do something with that. Or temperature reading is another one. Now, the interesting thing about these are that either of these components have value in and of themselves, right? For example, the temperature reading, we might want to just have like a heartbeat where every time the temperature is red, it pings some system say, okay, my temperature sensors are all still working. We don't care what the temperature is, we just want to know that they're working. So the event is all we need. The notification is all we need. Or we might be logging temperature over time, and we may not need to know each time it's red, but we want to have an aggregation of all of them. So these things have value on their own, but together, they're even more valuable. So this is what an event might look like in Kafka. Well, actually, in Kafka, it's just bytes, which is one of the nice things about Kafka. It's a very efficient binary format for transferring the data. But in our applications, it would normally be something like this, like a JSON object or perhaps some serialization format like Avro or protobuf. There are two main components to an event in Kafka. There are other things like headers and timestamps that you can add, but the main components are the key and the value. Now, the key is generally a simple data type like a string or a long or perhaps a UID. And the value is where you have your payload. So value would be some kind of an object that's going to have fields. And again, it can be in any kind of format. It has to be serialized to bytes to send it to Kafka and then deserialize on the other end. So anything that could be serialized to and from bytes, you can use for Kafka events. Now, these events are written to what we call a topic. And a topic, it's not a cue. Some people do think of Kafka as a message cue. It's not that. It's a log. So it's an append-only, immutable, ordered log of events and durable as well. The events stay on the log. When they're posted to the log, they stay there as long as we want them there. We set limits either by time, seven days is the default, I believe, but you can go months, years, or permanently, or a day or a second, whatever you want to do. You can set the time limit or you can set size on disk. But the key thing to remember is that the events stay on the log as long as we want them to be there. So they're not removed when they're consumed. And that number you see at the bottom, that's what we refer to as an offset. So every event lands in a topic and has a specific offset. And that offset is associated with that event permanently, as long as that event's in the system. As it gets older, if you have thresholds set, it'll drop off after a while, but that number will not be reused, the number just keeps on growing. And I also want to point out, I think we'll see this again shortly, but I'm referring to showing a log here, a topic of the single log. Most topics about multiple logs are called partitions because Kafka is a distributed system. So by having multiple partitions in a topic, you can spread those partitions across different broker nodes in a Kafka cluster. And it allows you to scale horizontally quite well. All right, so the thing that writes the events to the log is called a producer. And a producer is part of the client library. The client library that comes with Kafka is the JVM library, since it is written in Java and Scala. But there are two really good libraries for Python, as well as libraries for Golang, .NET, Node.js, different languages out there, even REST, I think they're going now. But all those will have these same components in. They'll all have a producer. And the producer is just a class that you're going to include in your application that's going to do the writing of events to the topic. And it just writes them from the beginning, works on where it keeps on depending on to the end. It's immutable. You can't change these events. It's kind of like real life, right? You can't change something already happened. You can add a new event that corrects what happened, but you can't change what happened. And then it comes along the consumer. Now the consumer is also part of the client library. And this is the thing that will be reading the events from the topic and doing whatever we want with them. That's our processing. So it's important to note that the producer and consumer are completely decoupled. They don't know anything about each other, right? The producer doesn't know who or if anything is consuming the events and the consumer doesn't know where those events came from. It just knows they're landed in the topic that it's listening to. And so the consumer will read and process the events. I don't even like to use the word consume because it implies removing them, but it doesn't. They stay there. The consumer will read the events and process them. And it will periodically record the offset of the most recently completely processed event, right? And that we call the committed offset. And then that offset value, that committed offset is used in case the consumer goes down. If the consumer does go down, the producer will keep on going. It isn't affected by that. So you don't have any cascading failures or things like that. And then when the consumer comes back up, it will use that committed offset to say where it left off and it will pick up at the very next event and keep on going forward. It might do some catching up, but it won't skip any events. Two key things in Kafka that are really important. If you configure it appropriately, which is the defaults, it's very difficult to either skip data in Kafka or lose data. There are ways you can do it if you want to, but it's generally pretty hard to do. Kafka's going to be very reliable and very durable. Okay, so as I mentioned, the producer and consumer are decoupled from each other. They don't know about the existence of each other at all. But they do need to agree on the data that they're going to be working with. The producer needs to be able to serialize the events to bytes to send them to Kafka. The consumer needs to be able to take those events and deserialize them to do something useful in your application. And the best way to do that is with schemas. You could just do it all hard-coded, but that's not recommended. So usually people use schemas. And the schemas that Kafka supports out of the box are Avro, Protobuf, or JSON schema. And so if you're using a schema, then it's really recommended to use a schema registry, which is not part of Apache Kafka itself, but it is a free tool from Confluent. And if you configure your producer to use the schema registry, which is simply just adding in the address of it, because schema registry is a separate application that you would run. Or if you're using a managed service, it would probably be hosted there for you. You have a Confluent Cloud. So you just configure with the URL of your schema registry and any security credentials you need, and then it'll automatically start using it. And what will happen then is that the producer will, before it sends an event with a certain schema, it will send that schema to the schema registry. The schema registry will store it and return an ID. The producer will stick that ID at the beginning of the event. It's the first five bytes are used, the first bytes are the signals that there is an ID and the next four bytes are the ID. So that ID will be attached to every event with that type of schema from then on until the schema changes. In which case the schema changes, the producer will send an update. Really? Already? Okay. I'm going to move a little quicker. And then the consumer will see the ID and they'll call the schema registry, hey I've got a schema, give me the schema for this ID, it'll get it and will use it to deserialize it. Oh, I keep hitting that wrong button. Alright real quickly I'm going to go on this is consumer groups. Consumer groups are a really cool tool in Kafka that allow you to have multiple instances of your client applications. This is good for scale. So we can have two instances here right now. They have four partitions in our topic and the partitions are the unit of scale in Kafka. So if you want to scale really big horizontally you're going to have to have lots of partitions which is fine to do. Some applications have thousands. This one has four. So we have two going to each of these consumer instances. If we increase that to four they'll each get one. The balancing of those is done automatically and using the committed offsets it makes sure that nothing is skipped or nothing is lost. And if we scale back because things are slowed down it rebalances again automatically for us. Okay so moving on from that. I'm using a Kafka with it with Python. It said there's two libraries out there, two packages that you can use. The first one is Kafka Python. It's a community-supported library and it includes the following main classes and other stuff in it too but it's got the Kafka producer, the Kafka consumer and the Kafka admin client and you can find that there. The other one, the one I'm going to be using in my demo if I have time to show it to you, is Confluent Kafka Python. This is one that's free to use but it's produced and supported by Confluent. It also has the producer classes because it's called producer and a consumer. It's called consumer but it also has an Avro producer and Avro consumer and those allow you to use the Avro serialization format and work with the schema registry and also as the admin client and you can find that one there. Alright so now back to the events. Here's what we're talking about. Basically we're not we're talking about replacing standard request response, HTTP based communication between microservices which is a very common way to work in microservices. It's the way I've done it for years and it basically starts out with this. We have our client who's using HTTP for obvious reasons. It makes sense there, right? You've got a web app or a mobile app or something like that. It's calling our server and then our server, in this case the blue service, makes a call to the green service. The green service makes a call to the red service. The red service makes a call to the pink service. Pink service calls the gray service and then red service also calls that yellow one for some reason. And then it does this work and then it goes back to client, right? So and this works well and I built lots of applications this way and they usually start out great. Another variation of this might be that the blue service calls the green service and acts like an orchestrator and fans out to the other services. And that works too. Most of these systems will work and there's a lot of them in use. There's a lot of tools out there to help us with that things like Swagger or OpenAPI stuff like that. But I've been in so many of these projects and they end up looking more like this after a while, right? Usually before or even in production. And it's because you have so much coupling. It makes it difficult to make changes to or add a new feature. So it's like, well, I don't want to mess with this existing service to add this feature to have to change everything else that's connected. So I've got another service for it and you start is making some sometimes important decisions, but you end up often ends up with a mess. And that most of that comes back to that strong coupling that this type of connection gives you. You also have an issue of cascading failures with request response. If we go back to that picture here, if something happens and say that that red service, then everything connected downstream from that will crash too. Right? So you have a lot of cascading failures and things like that that will happen with this type of structure. So we're gonna propose using events for this instead. And it's not a silver bullet, but it does make it easier to keep our applications cleaner. So again, we start the same way still use a HP from our client to our initial server. But instead of making another HTTP call, this service is going to post an event to a topic. And that green service is going to consume from that blue topic and do its work and post an event to the green topic. The red service is going to consume from that topic, do its work and post another one down the line. And then the end in this situation, we're also our blue service is also going to consume from to produce the blue topic, but it's also going to consume from the great topic so it can get that final state. This is one way to structure there's other ways to do this as well. And then as far as community of the client, you could either have a two step process, which is what my demo have if I tend to run it. But or you could use some web sockets to really this back directly to the client. This will all happen just as quickly if not if not faster than the request response type system. It's just it's just asynchronous and it's less decou, it's more decoupled, less coupled. Also, so these things don't now these services don't know anything about each other at all, right? Now they're completely decoupled. They all they do know about is the events that they're working with. So again, they have to agree on schemas, but that so schema becomes kind of the new point of coupling. So it's a possible to have systems interact with each other without any coupling, right? You're going to have some. I think that a scheme is a much cleaner point of coupling than an API. Also with this system, you can if you ask want to add another certain there's that one too. So I want to put this in here just to show briefly that you can also mix and match. So we still say we have another service that's an external service. It doesn't speak events. So we can still make an HTTP call it to that. That's not going to hurt anything. So it's not like either or so I want to show there. But also if you want to add another feature later on, it's easy to work with that by adding another system, another application that might consume that some of that same data. And it can do that. And so this, this burgundy service is going to consume from that green topic. Maybe they have a different point than the red service does. It doesn't matter. They're completely decoupled. They don't know anything about each other, but the events are still there. So they can be consumed by multiple applications. So we can add, for example, this could be like a reporting or analytics application that we're tacking on just to read some data from that topic to do something, some BI or something like that with it. And it won't affect anything else. So we can easily add or remove applications from, from a system like this without affecting the others. So that's what we're trying to get to. And how do we get there? Well, first thing is to find the events. Now if you're doing a new application, a Greenfield application, then event modeling is a great way to go. There's a great conference video at the URL there that talks more about it. But it's basically a modeling system for doing, for doing everything, for designing your entire system event first, it treats events as first class citizens. So that's, that's for newer systems. If you're finding, if you're working with existing systems, finding your events in those can be as simple as taking a look at what starts your services working, probably an API call or something, right? That could become an event that's raised by that, by that calling application instead. And then what information does that need, service need to do its work? Well, that could be the payload for that event. And then think about what actions did your service perform? Is it doing some kind of work? Is it making something happen? That's probably an event. And then the information that results from that action could be, again, the value for that event. So they're just some ways of just thinking through, thinking through about the story of your application, what is happening, what's doing what, and when. And that's, that's what events are. Okay, next to find your topics. One topic prevent type is one option you can go with. If you do that, then you don't really have to have like a field in the event telling what the type is because the topic tells what it is. But then you need to put a lot of topics and sometimes it gets your ordering can be, can be harder to manage if you have events that are related to a certain domain. So one topic for domain might be better, like for example, an order. You might have a topic for all orders and every event that happens in order order placed order paid order shipped. These are all separate events that will end up in the same topic. And those situations you'll probably have at a field to the, to the value that will tell what the event type is there. Or you can mix and match, right? There's sometimes there's one works better for one part of the application than the other. The other thing with, with topics is partition sizes. It's a really important thing to think up front. If you ever want to expand your system, you want to aim high on the number of partitions. There's not a high cost to having lots of partitions, but it is a high cost to changing the partitions later on. And then don't forget schema. Schema is really important. You want to have a schema for every event type, whether you have them in their own topics or not. And you want to make sure you keep in mind that schemas are going to change. So think about compatibility rules. The schema registry does help you with compatibility. But you can set rules on it. Say I only want forward or backward or compatible or both. And it will enforce that for you. But the schemas do change and that's an important thing to keep an eye on. All right. So I think we have a little bit of time. So what we're going to do here is we're going to build, I'm not going to build, sorry Britton, don't worry. A random pizza generator. If you ever order pizza for a group of people, it's a real pain to figure out what everybody likes, right? So we're going to solve that problem for people that are, you know, crews that are working late or some pizza to get the job done. We're going to let them just tell us how many they want and we're going to give them a random selection of pizzas. And we're going to do this with events. So our customer is going to call into the pizza service. The pizza service is going to post an event to a pizza topic. The sauce service is going to be consuming from that topic. It's going to pick it up, add some random sauce selection and post to a pizza with sauce topic. And then the cheese service is going to pick that up and add some random cheese selection and post that all the way down through until we add our veggies. The source code for the application is all that URL down below. And yeah, so now let's take a look at it. Let's look at some code. Is that readable? Okay, great. It's not up here. Oh, I got my brightness down because I forgot my power adapter. Batteries going to find someone to make it a little brighter for myself. Okay, so this is our first service, since it is talking to the client through HTTP is a flask application. So it's got the built in HTTP server. And it's got two end, or it's one endpoint with two methods that tend as a post method and a get method. The post method just takes in a number for the number of pizzas that our customer wants. And then the get method will take an EU ID, which will be returned from that first method. And so it's by a two step call, right? One call the order their pizzas and make another call to get them. Like said, this could be replaced with something using some of that web sockets to make it more seamless to the user. And then all the work is done in our pizza service over here. So just to show you how to use Python in a flask application, we import the producer and consumer from the Confluent Kafka package. We also import this config parser. And this is for our properties that the consumer producer needs. We're going to get that from the configuration. And then we're going to create a producer instance, giving it the config. This pizza warmer is just a dictionary. We're holding some data in it for the completed pizzas. I'm not going to go into the details of how the application works because it's not time, but... So then we have the endpoint that calls it order pizzas. So we give it the count and we're going to order the... We set the pizza order which holds all that data. We give it the count. We're going to start... And we're going to loop through and for each of those we're going to create a pizza. And for each pizza we're going to post it to a pizza topic. So to post an event to a topic with a Python producer is just the produce method. So the pizza producer that produce, give it the topic name. It's basically like the address and here's the value. So the key and the value. Those two are the event and this is the topic it's going to. And that's what we call flush to make sure it gets written. And then we're going to return that order ID, which is just a random UID that's been generated. Now the order ID is going to be the same for all the pizzas that are ordered. So basically it's for the whole order. And on the git we're going to take that... We're going to grab that order ID from the pizza warmer which has our pizza order and we're going to return that as Jason. One thing I want to point out here too is that our consumer is started up down here. So the consumer we're going to create the consumer with the config. So this is really easy to work with these classes and from Kafka. It's just the consumer and the producer you just construct them and use them. The only extra step for the consumer is that we have to subscribe to a topic. So a producer can produce any topic because you give it to it and send in the produce method. The consumer has to be subscribed to a topic and it will only work with that topic. Or it can be more than one topic though because it's takes a list. We're giving a list of one here. So then it's going to pull that and it's going to keep on checking for any new events. And whenever it finds one it's going to do our logic here and add it to the pizza order. So that's yeah. So that's just the business type logic I'm not going to go into here but that's how to produce and consume from the Kafka application. And then just to show the next application here is this the soft service. I'm only going to show this one because the others are all identical in what they do. Basically this one is just a plain Python application. It isn't a Flask application because it doesn't have any HTTP. Normally in a request response based thing we probably all be Flask or Django applications. They'd all be making HTTP calls across the network. Lots of chatty stuff with lots of JSON flowing through the pipes.  They're each going to have a consumer producer in them. So the consumer is going to subscribe to the pizza topic and whenever it gets one it's going to do its work. It's going to add its magic sauce. I'm running out of time. And then it's going to produce to the pizza with sauce topic. So that's how that exchange happens. And the same thing will happen all the way down to the final one. And then as we saw over here our pizza service, the first service consumes from the pizza with veggies which is the final one. So that will get to completed pizza. And then we're just going to run this real quick and see if it all works. I think I have the other ones already running. So I hope I do. We'll find out. So we can order five pizzas. There we go. So we've got to take that. And then we can do that one. But we'll do these guys. All we do is just post that UID into this get request here. I'm piping it to JQ, which if you're not familiar with that, is an excellent little command line tool for working with JSON. And there's our delicious pizzas all ready to go. And I got one minute left. So with that one minute, I'm going to show you one last thing because like I said, it's really easy to add extra services. So what we did down to the end here is I added a cheese reporter. This application is a separate application we added later on while our other system is existing and running already. Didn't interfere with it anyway. And that's going to allow us to do is to check what's the most popular cheeses that we have. And we have that running on a different port, 50-50. So we run that. And then we see a list of our and if we were to run some more or order some more pizzas and then we run our report again, we see the updated values of our most popular cheese selections. Our cheese producer or cheese supplier wanted that information. But the point I want to show there is that you can add these extra applications on consuming from the same data but not affecting them in any way. And I think that's the last thing I had was just some resources there to leave you with. There's some video courses on developer.confluent.io which goes into a lot more of the stuff and way more depth because I didn't have that much time. Kafka 101 is great if you really want to learn Kafka better. And then there's also these other applications. There's actually 12 different courses out there now. So check those out. And there's some Python and Kafka resources. And then an excellent book of designing event driven systems just talks more about event driven architectures and using Kafka in those types applications. It's a free book. You can get that link there but it's an excellent book too. And that's all I had. Thank you so much. So is there time for questions? Oh there it is. Okay good. I thought I ran out of question time. Come on up to the microphone. I promise to listen to your question. I don't promise to answer it. Yeah. Thank you. The title mentions microservices. And I mean those often have their own database. Each service. And then we're going into the territory of event sourcing. I mean this Yeah. Example you show is more like lambdas that you couple over over Kafka. Yeah. But how I mean event sourcing is known as being complex. What is your opinion? Event sourcing is known as being complex and some people are using it are getting some great success with it. But it is taking a lot of work. And I actually had a slide in there earlier. I don't know how it got removed but actually had one last slide at the end of the talk about the event-driven stuff. And it basically said this doesn't mean no databases. This what I'm focusing on is a replacement to synchronous request response connections between some microservices. Each of those services could have had a database. And that would have been fine. In fact Kafka works really well with databases using Kafka Connect which is something that allows you to connect with external systems including any database known to man. Yeah. One of our challenges in this is actually the testing side because like you said, Kafka messages are there forever. And we have kind of trouble to put it in a nice testing framework. You have to spin up new Kafka instances to write test messages and look at the output of other Kafka. I mean, do you have anything? Well, the story is getting better. I know the Kafka team, the engineers are really working on trying to improve the testing story because they've heard that complaint a few times. So they're working on some smaller, lighter way instances of Kafka that you can run more quickly in containers to do your testing. But you also can because of the data is that way, you can have applications hitting your even production data for that matter and it won't affect it anyway. So you really can. There's some flexibility in the way you structure your tests with Kafka. There's no other questions. I want to point out one last thing. See this structure here that where we go, it's kind of serialized. But think about it. It really is an exercise for the audience for later. What you could do is this pizza service could post this topic here. I should point over here. The pizza was composed post that topic right there. And then these ones could all pick up from that topic, do their own work independently, right to their own topics independently. And then then a separate application at the end could pull from all those topics and aggregate the final result, which could be a lot more efficient and kind of fun to build. I just haven't had a chance to try that yet. And that's really all I had.


You know that in an English sentence, the verb is the most important word. It is through the action described by the verb that the sentence becomes alive. As a result, I would say that the verb is the lifeblood of a sentence. Now among other properties, verbs tell time. They tell time by specifying when the action occurred, when the action took place. This time feature is known as tense. All verbs have different tenses indicated. All verbs have different tenses that indicate the time the sentence is referring to. Now tense as you have learned is the verb property that describes when in time an action took place. Now we shall look at another property of the verb which is known as voice. This is another property of verbs and it is known as voice. To understand voice, you must know the distinction between active and passive voice. Active and passive voice. And you must avoid this mistake of thinking that every verb is either passive or active. Some verbs are neither active nor passive but they are known as linking verbs. Now what does voice do? Voice indicates whether the subject of the verb is performing the action or is receiving the action which is described by the verb. Now there are two points that you must keep in mind. The first is that use active voice to emphasize the performer of an action. When you want to emphasize who is doing the action then you must write the sentence in the active voice. You must use the passive voice to de-emphasize the performer of the action. And in this way you emphasize the object of the action. Now if you look at I will show you a chart and it will become very clear. Sentences are either written either in the active or in the passive voice. Now let us look at the structure of the active voice sentence and the structure of the passive voice sentence. Now on the chart notice there are four columns. The first one is subject, second is verb, third is direct object and the fourth is compliment. Now an active voice sentence, the verb has an object, a direct object. The first sentence, the state management will prosecute, the verb will prosecute and the verb has a direct object. The object is trespassers, trespassers. Number two, passengers may purchase tickets at any airline office. The verb is may purchase and may purchase requires a direct object which happens to be tickets. Number three, students use computers in the laboratory. Use the verb use in that active sentence has a direct object which is computers. Number four, you should take the medicine once daily. You is the subject, look at all the four subjects in that chart. Look at the verbs and look at the direct objects. The verbs in the active sentence need a direct object, right? They may or may not take compliments but they do take direct objects. Now you notice that in these sentences the subject performs the action of the verb. In passive sentences the subject receives the action of the verb. The direct object of the active sentence becomes the subject of the passive sentence. Because every sentence in English must have a subject, passive sentences can be formed only by transitive verbs. Transitive verbs take direct objects.  Now look at the next chart which is the structure of passive voice sentences. And notice the change. Here the verbs are trespassers, tickets, computers, the medicine. Right? Trespassers will be prosecuted, tickets may be purchased, computers are used, the medicine should be taken. Notice how the whole thing is inverted. The formation of passive sentences. A passive sentence is composed of the following parts. Subject plus some tense of the B form of the verb plus the past participle plus agent. Number one, you have to keep in mind there are four things in the formation of the passive sentence. The object of an active sentence becomes the subject of the passive sentence. What is the object in an active sentence? It becomes the subject of the passive sentence. That is number one. Number two, in the passive sentence the tense is formed by the B form of the verb. Number three, the subject of the active sentence becomes the agent of the passive sentence. And number four, in a passive sentence the agent or the doer of the action may sometimes be omitted. Now, it will all become clear if you look at the verb tenses in passive sentences. Look at the present tenses in passive sentences. The simple part, jewels are bought by ladies. Are bought, right? Present continuous, jewels are being bought by ladies. Past perfect, ladies have been advised to declare their jewelry in their wealth tax forms. And the use of models, steps must be taken to educate the public about filling up tax forms. The past tenses, in a passive sentence this is how the past tense is used. Maps of the rebels, the rebels hide out were shown to the press. Past continuous, until recently handcrafted jewelry was not being designed locally. Past perfect, Pakistani carpets had always been designed by local artists. And with perfect models, the textile industry might not have been required by the government to pay taxes. And the future tenses, teaching assistants will be used to assist teachers in evaluating students' examination scripts, will be used. This is a passive sentence using the future tense, will be used. Another one, factories are going to be built in the new export promoting zone. Are going to be the going to form, which is the future. And the future perfect, by 2010 the new canal system will have been put into regular use. Will have been put into regular use. Now all these sentences were in the passive. And you were shown how the different tenses are used in the passive. The agent in the passive sentence. A passive sentence can be written with an agent. A passive sentence can be written without the agent. By agent we mean the doer of the action. Now, let us look at samples where a passive sentence is written with the agent. The agent in the passive sentence answers the question by whom or by what. The action is performed. Number one, you have to remember two things. The first thing is that the agent is named if it is important or if it is necessary to complete the meaning or understanding of the sentence. For example, take the sentence. The accident was caused by a cyclist. This is a passive sentence. The accident was caused by a cyclist. Now by a cyclist is the agent. Noise in our neighborhood is produced by trains. Here the agent is named. The man was killed by his neighbor. By his neighbor. Now in all these three sentences, they were passive sentences but they were with the agent. The agent was specified. Now let us look at sentences, passive sentences which are without the agent. Here the agent is not named. You can have a passive sentence where the agent is not named. There are certain conditions. The first condition is when the identity of the agent is understood and it does not have to be mentioned. Example, the president has been re-elected for another year. Now in that passive sentence, the agent has not been mentioned. That sentence is without the agent and the agent over there is maybe it is the council, maybe it is the voters, maybe it is the syndicate, whatever. But that sentence is without the agent. The agent is not named. The president has been re-elected for another year. Who did the election? Who elected him? It is not mentioned. In other sentence, Sheena is spoken in many parts of northern areas of Pakistan. By whom? Sheena is spoken. Now in that sentence, the agent is not named. Because Sheena is spoken by people in many parts of northern areas of Pakistan. Now the second condition when you can have a passive sentence without the agent is when the identity of the agent is unimportant. For example, Pakistan television newscasts are translated into both English and Arabic. Now over there, who translates them? It is not important. Pakistan television newscasts are translated. It is understood that they are translated by someone. So the identity of the agent is unimportant. Another condition when you can have a passive sentence without naming the agent is when the identity of the agent is unknown. For example, take this sentence. An error has been made in the computer input data. An error has been made in the computer input data. It is understood that that error has been made by someone. So you can have passive sentences without the agent. Number one, when the identity is unimportant. Number two, when the agent is unknown. Now at the end, we will talk about the uses of the passive. When you want to give your writing an objective or an impersonal tone, you use the passive. And it is very often used in scientific writing, in business writing and in newspaper reports. Why? Because it takes away the responsibility of the writer. Number one, when you want to give your writing an objective or an impersonal tone. Number two, when you want to focus attention on the receiver of the action. Now for instance, if you were writing a paper about a discovery, the use of the passive will focus on the discovery. But if you were to write your paper with active verbs, the reader might think your paper is about the person who made the discovery and not the discovery itself. So you will use the passive. In today's lesson, we looked at the different tenses of the verb and we looked at passive sentences. So with that, we come to an end. Allah Hafiz, see you next time.


One thing Marines are afraid of is getting dirty as demonstrated by the 18th annual Swamp Rock aboard Marine Corps Base Hawaii For over 2,400 service members families and retired military gathered for a scenic one-mile course. There's sand mud and obstacles teams of six ran the course somewhere in traditional running gear and Others opting for more creative apparel At the finish the top three teams received congratulations and medals and all were given a good washing Followed by live entertainment Reporting from Washington, I'm Lance Corporal John Tucker


Want to articulate yourself better? I'm sharing eight powerful ways to be more articulate. And before we dive in, I'm going to quickly cover what does it mean to be more articulate? Being articulate is being better at, firstly, what you say, you know, the words, the sentences, the stories and the structure used to get your ideas, feelings, thoughts and viewpoints across to other people, whether on a one-to-one basis or to large groups. And secondly, it's how you communicate what you say and using the pitch and speed of your voice, where you place the emphasis, how you create anticipation, how you use silence and pauses and how you use your body language with what you say. When you are articulate, you find it easier to keep the other person's attention and to make it easier for the other person to understand and follow what you're saying. Articulate yourself better and you'll feel more confidence and more valued. I'm covering, firstly, six benefits of being more articulate and then second, eight powerful ways to be more articulate. I share practical tips for each so you can learn the skills to clearly articulate your thoughts. My name is Jess Coles and if you're new here, Enhance.training shares people management expertise, resources and courses teaching you how to build higher performing teams. I've included links to additional videos and resources in the description below as well as the video timestamps, so do take a look at these. If you liked this video, please give it a thumbs up and subscribe. I was shy at school and I hated speaking in front of small groups. I wasn't confident in how I spoke and watching their eyes glaze over and their attention wander reinforced my belief that I wasn't good at articulating my thoughts and speaking to groups. My mindset was a big part of the problem. Many years later and with a lot more practice at articulating myself better, I know the benefits of being more articulate and how that helps you at work and as a manager. Here are six benefits of being more articulate. Firstly, being more articulate saves you and others a lot of time. Being able to articulate your thoughts clearly results in quicker understanding in others, a lot less confusion in team members and colleagues and a lot less misunderstandings. Articulate yourself better and you only say things once rather than repeat them three or four times. You save a lot of time. Second, being more articulate builds your confidence in communicating. Whether speaking on one-on-one to colleagues or presenting to a group, having people clearly maintaining eye contact, showing attentive body language and asking relevant questions to learn more all help to reinforce and build your confidence in how you are communicating. Third, articulate yourself better and enjoy increased professional success. You'll be more articulate and communicate better and you improve teamwork and your influence and impact at work which leads to more professional success. Fourth, you build stronger relationships. Articulate yourself well and be confident communicating your ideas, your feelings and your thoughts and you show more of yourself to others. By being more authentic, you increase others' trust in you. Higher trust levels means stronger relationships. Fifth, being more articulate leads to bigger professional networks. As you progress your career, your network within a company and external to your company becomes more and more important for personal support and for career advancement. The bigger and better your network, the better you do. Then sixth, improve public speaking skills. Yet being articulate and confident when speaking to groups is seen as an important prerequisite for promotion into leadership and management positions. So let's talk about how to become more articulate. I am sharing eight powerful ways to be more articulate. Knowing what to do will not, on its own, make you more articulate. You need to practice each of these techniques to get the benefits. Being articulate is a skill and I share tips on how to practice each of these eight ways to be more articulate. Firstly, avoid using filler words. Filler words are the mmm, er, yeah and other noises people use to bridge the period when they are thinking about what to say next. Swap these filler words for silence. Whenever you are speaking to others, pay attention to what you say. Every time you are about to use a mmm, try to swap it for a pause without any sound being made. It won't be long before you don't use filler words at all when articulating your thoughts and feelings. Lots of filler words are distracting. Second, to be more articulate, increase your vocabulary. Learning vocabulary is not about using bigger, more complex words. There is a lot of benefit in using simpler words as more people understand them. Focus instead on learning more descriptive words so you are able to describe your thoughts, ideas and feelings more accurately with more colour, with more life. Use a dictionary to find more adjectives, adverbs and participle and incorporate them into your everyday communication. Consciously practice using more descriptive words until you incorporate them naturally into what you say every day. Third, to be more articulate, pronounce your words clearly. This is obvious, yet of all the people you know how would you rank yourself in terms of how clearly you speak? Are you top of your list? For many people, speaking more slowly and consciously focusing on finishing each word spoken makes what they say a lot clearer. Avoid running one word into the next or missing endings to words. And for those that speak slowly, work on speeding up the words you say. Use the body language feedback from others to judge how effective using different speaking speeds are for you and how well you are at pronouncing your words. Fourth, for how to be more articulate, improve the structure of what you say. You're rambling, introducing different ideas or too many ideas not providing context and not being clear on the points that you are making lead to the other person getting bored, losing the thread of what you're saying or being confused. A key way to better articulate your thoughts is to communicate the context, present your key arguments or points and then ask for an action, a decision or provide a summary. Creating a structure that logically leads the person from one step to the next will keep their attention and increase their understanding. A good way to practice structuring your arguments is to write them down and review them. The better you get at structuring your writing, the better you'll be at structuring what you say. Keep what you write short and start with 150 to 200 words and then maybe expand them to 500 words when you get better. Fifth, be more articulate by knowing your audience. Are you speaking to analytical professionals, time poor managers or to your local builders? What language and speaking style are they using? Are they serious in their outlook or cracking lots of jokes? Adapt how you articulate your thoughts and feelings and mirror their language and styles. Pay attention to the feedback your audience provides via their body language and adapt to articulate yourself better. For example, change your style from a more formal style to a more relaxed conversational style or vice versa. Change the length of the sentence you use to simpler or more complex. Include more examples in detail or elevate what you articulate to a more bigger picture. Adapt how you articulate your thoughts and feelings to your audience. Sixth, be more articulate by varying your style and tone. People take in information, thoughts and ideas in different ways. To articulate yourself well, be mindful of four different ways people take in information and adapt how you articulate your thoughts to cover all of them if you can. The first is those that like the big picture, the high level view so they can understand the context and how everything fits together easily. Create diagrams, speak to the context and ask questions to get them thinking about the big picture. Second are those that focus on the group, on others and are altruistic. Talk about the wider benefits, the contribution to the group or the local community. Link what you are communicating into how your audience can help benefit others. Third are those that like stories are more relaxed and want a more friendly conversational style and approach. Create relevant stories, ask more questions and get more back and forth going in the conversation. And fourth are those that love data and are more analytical. So include charts, graphs, facts and figures in how you articulate yourself to cater for people who are much more analytical. By trying to balance how you articulate yourself to the different ways people take in information you'll get more attention and understanding from your audience. Seventh be more articulate by practicing speaking in private. As mentioned earlier, communicating is a skill and improving how you articulate yourself requires practice. Speaking in front of a mirror is a good way to work on your facial expressions and how you use your arms and hands to emphasise points being made. Your tone and body language and the emphasis you put on what you say will change the meaning of the words being said. When I started creating videos and podcasts I practised by filming myself and reviewing how I looked and sounded. Videoing yourself is really easy to do with your mobile. Play around with different approaches, styles, talking speeds and arm gestures. Compare what you remember yourself doing and saying versus how it comes across in the recording. This is a good way to build up your self-awareness when speaking. Eight be more articulate by practising with a group. Speaking to a group is about getting comfortable speaking to bigger audiences and managing all your emotions and fears while doing so. Seek out opportunities to speak to groups at work. Present in your team meetings. Ask to speak in company meetings, project meetings or before bigger groups. There are also lots of ways to get practice speaking to groups outside of work too. Four ideas include firstly joining Toastmasters or similar speaking groups. Second could be taking a public speaking course where you're going to get lots of practice in the course. Third you could join a stand-up comedy course. Or fourth you could take acting classes. All of these will give you plenty of opportunity to speak in front of different sized groups and give you practice to better articulate your thoughts and feelings. So in summary, put some effort in and you'll articulate yourself better. I've shared eight powerful ways to be more articulate and now it's up to you to put these techniques into practice. There is a lot to be gained by being more articulate at work and outside of work and we've been through six big benefits of doing so. Please put just a bit of work into improving how you articulate yourself and see the difference it makes to your confidence and how you are perceived by others. Then put in more practice and get more of the benefits of being more articulate. If you have any questions on articulate yourself better, eight powerful ways to be more articulate, please leave them in the comment section below and I'll get back to you. Thanks very much for watching and I look forward to speaking to you again soon.


Namaskaram Sadhguruji, I'm Divyanka Tripathi Dahiya and it's a privilege that I can ask you something. My question is that why are all the forbidden things so enjoyable and how to stay away from such temptations?  So this, what is forbidden and what is allowed is not a part of this culture.  Adam and Eve I'm talking about. So when they did not know what to do with each other, they ate that apple, they had only one apple and they thought they were in heaven. So after eating that apple, they fell and the forbidden tree, what people have forgotten is the forbidden fruit was the fruit of knowledge. So God said it seems, do not eat the fruit of knowledge because knowledge is forbidden because life happens out of awareness, not knowledge. Right now we have accumulated stuff in our life in such a way, something is good, something is bad, something is virtue, something is sin. Because of this kind of divisions, because of this kind of discrimination from one activity to another, now we have these problems.  Right now Divyanka, if I ask you not to think about monkeys for the next ten seconds, can you not think about monkeys? You'll think only about monkeys. So the very nature of the mind is such that in this mind there is only addition and multiplication, there is no subtraction and division. That is, you cannot take one thought out of your mind. If you make efforts, it will only multiply.   So drop this what is forbidden and what is not forbidden, what is your natural inclination that you do joyfully, there is really no harm in that. And when you take time to recognize what is your natural inclination, believe me, you will not do anything in excess, you will see that everything falls into place as it should be. Right now small things have become big things in people's minds simply because they're trying to avoid it. This is the nature of the mind. What you don't want to think about, that's all you will think about.


Salams, you're watching the International Daily Roundup brought to you by People's Dispatch where we bring you some of the top stories from around the world. Let's first take a look at today's headlines. The report finds US sanctions fueling rising poverty in Iran. Syrian Defence Forces announced a recapture of Al-Sina. Another woman dies in Poland after being denied an abortion. And Colombia passes a controversial citizen security law. In our first story, we look at a new report on the impact that US sanctions are having on Iran's economy. Soon after the Trump administration withdrew the US from the nuclear deal, it proceeded to enforce a so-called maximum pressure campaign. Sweeping sanctions were imposed on Iran's key sectors, including oil and banking. A report by the Sanctions and Security Research Project argues that these measures were a weapon. They triggered high levels of inflation, which led to a marked increase in poverty. The Iranian real has plunged to around 270,000 against the US dollar. Meanwhile, the prices of necessities like milk and eggs have risen by over 150%. According to the report, while wages have remained steady, they have been unable to cope with the inflation. As a result, even if many goods are still available, they are simply unaffordable to most people. This secondary impact of sanctions has been prominent in the prices of food. The cost of health care has also soared by close to 125%. The health crisis has also worsened due to over-compliance with sanctions by third parties. UN experts have found that banks and businesses have refused to engage in exempted and authorized humanitarian trade. For example, a Swedish company has stopped critical shipments of bandages to Iran. The product offers the most effective treatment against a life-threatening genetic skin disease. As per reports, around 30 Iranians have died since shipments stopped in 2018. The Kurdish-led Syrian defence forces have announced the recapture of al-Sana prison in Hasaka. The facility was attacked by the Islamic State terror group last week, leading to a week of intense fighting. The STF stated on January 26 that the last of the IS terrorists had surrendered. At least 181 people have been reported killed during the violence. Nearly 50 STF soldiers and seven civilians were killed in the operation coordinated by the international security forces. Al-Sana is estimated to have held over 3,500 suspected IS members. Fighting broke out after the group's fighters rammed two vehicles into the prison. The STF stated that inmates took prison employees hostage and used children inside as human shields. According to a UNICEF statement, almost 850 children are in detention in northeast Syria. Most are being held in Hasaka. The majority are Syrian and Iraqi boys while others belong to over 20 nationalities. As per recent reports, the status of these children is not clear. However, SAVE THE CHILDREN has stated on Monday that it has received reports that the children were among the injured and the dead. The STF's operation in and around Al-Sana was accompanied by US airstrikes. The Syrian government has condemned the civilian casualties and infrastructure damage caused by the attack. According to Middle East Eye, the fighting has also displaced close to 45,000 people in the area. The STF stated on Wednesday that 1,000 IS members had surrendered. It added that sweeping operations were still underway in Hasaka, Deryazor and Raqqa. Outrage has spread across Poland following the death of a woman who was denied an abortion. 37-year-old Agnieszka T was pregnant with twins and admitted to hospital on December 21. According to her family, the first fetus died in her womb on December 23. However, the doctors refused to remove it. Poland already has one of the world's harshest abortion laws. In 2020, a tribunal ruled that abortion, in the case of fatal fetal abnormalities, was also unconstitutional. Agnieszka's family has said that her health deteriorated rapidly after December 23. The heartbeat of the second fetus stopped a week after that. Doctors still waited another two days before terminating the pregnancy as late as December 31. Agnieszka's health continued to worsen for the weeks after until she finally passed away on January 25. Her family suspects that she suffered septic shock. However, the hospital has not confirmed a cause of death. A protest and vigil for Agnieszka outside the Constitutional Court was being held in Warsaw. It was among a series of mobilizations under the slogan, Not One More. Agnieszka's case follows just months after the death of a 30-year-old woman named Isabella. She died of septic shock in the 22nd week of her pregnancy after doctors refused to perform an emergency abortion. More than 1,000 women have approached the European Court of Human Rights to change Poland's abortion laws. And finally, rights groups in Colombia have denounced a new law which they say will criminalize protests. Far-right President Ivan Duque sanctioned the citizens' security law this week. The law permits the use of weapons in self-defense against unjust aggression. People enacting such violence are protected from criminal liability. The law also increases penalties for attempts against security or transport infrastructure and police or military installations. The initial sentence of four years has now been increased to as much as 12. It also introduces punishments in case of recidivism. As reported by Brazil Defato, social leaders or activists can be arrested for inciting violence. President Duque has also introduced a disciplinary statute and a patrol car statute for the police. The citizens' security law was introduced after the month-long national strike uprising in 2021. As such, it has targeted specific forms of protest seen during that time. This includes the prohibition of roadblocks which were widely used by indigenous protesters. The new law has raised fears of a further crackdown on social protests. The national strike itself has been marked by over 4,000 cases of police violence. Varying estimates have placed the death toll at over 70 people. That's all we have on the show for today. For more on these stories, visit our website peoplesispatch.org and give us a follow on all the regular social media platforms. Thank you for watching. Goodbye.


All right, good morning, Cyber Traders. Welcome back on this Friday. How's everybody doing? Good to see you, Steve. Jeff, Dennis. All the Cyber Traders in the room. Everybody on YouTube. Everybody's doing great. See you on Facebook also. Looks like we're having a decent morning so far. What a nice run on the SPCB. We got a huge pop. That went from a buck fifty to three twenty five. And let me tell you something.  Holding pretty strong here. Good to see you, Randy. Always nice to see you. Exaggerate, you know, Fausto. I think he even spelled it right. F-A-U-S-T-O. There you go. Well, listen, I'm excited. It's the end of the week. I love Fridays. Really nice day going on right now.  We had an unbelievable trading day with this one stock.  Hold on. Let me just scroll this. Let me just scroll this up here. Bring this up over here. And before we go through the watch list, because there's a couple of them moving. We got this one. We got FSR. That is just doing phenomenal. You all know about this stock right here, the electric car stock. And there's a couple other ones, too. I'm going to bring up. We'll talk a little bit about them both. But I want to start off talking about the, the JFIN. So, JFIN yesterday. Let me just bring this up over here really quick. So, this stock yesterday, okay. Let me just zoom in here so you guys can get a better perspective of what we're looking at here. Look at that. Look how gorgeous that stock was. Alright, so hopefully everybody on YouTube Facebook sees it. But look at this stock right here. I sent out an email, okay, to everybody in the cyber group room. And I guess some of the YouTubers probably here, probably didn't, I don't know if you saw us, whatever. But we killed it on this one stock. And you had so much time to get in it. You know what? What did we have the day before? We traded. What was that stock? T-Cat. Remember T-Cat? T-K agent. Well, look at that. I says, listen, don't worry about it. Don't worry about T-Cat. You missed it. You missed another full 500% mover in a day. You're going to get another one. And then all of a sudden this stock right here just came from nowhere. This JFIN kept going up. And let me tell you, there's some really good feedback from a lot of you. And remember, cyber traders, you know, in the cyber group room, listen, there's a lot of bad actors out there in our industry, okay? And, you know, and I just, we always just want to educate people, just tell them what they're getting themselves involved before they do it. So I asked everybody out there, I sent out an email regarding about, I said, listen, if you're making money, you're doing well. Just let everybody know how well you're doing and what, you know, what the difference between, you know, what your experience is. Cyber Traversity. So I sent everybody a Google review. You could just be so kind and fill that out. If you need help, our staff will help you, help you, you know, getting in there and how to do it. Because I know some of us are not the most crazy super tech savvy people. But please go out there, recommend us, write a nice Google review on us because we really need those reviews because a lot of people just don't understand this. Some really bad actors out there, they're telling people about what's great and then it looks bad on the industry and we don't want that to happen. But you also know that if you're new at Cyber Traversity, we always tell everybody, listen, just at least come and see because it is not for everybody. We know that. It's like, you know, not every diet is for everybody. Not every workout is everybody. Not every car is for everybody. Not every town that you want to live in is for everybody. But you know what? You won't know until you check it out. So please, I appreciate that. If you guys could do that, it means everything tells you to do that. But anyway, Jeefin was great and if you missed it and you weren't here, don't worry about it. They're there. We get like maybe two or three of these a week. And I'm talking about like a stock that goes up $2, a $5 stock to go to almost, goes up to $14, a $9 move. Listen, we get them all the time, all right? So I always get people still hampering over what's going on with GameStop. Listen, GameStop, let me ask you something. What did GameStop really do other than it ran, okay, granted, it ran from $17 to almost $500. But like, listen, you can't harp over this. We were looking at this thing way before it even took off. They're there every day. All right, just this is the most extreme. But anyway, let's go over and by the way, there's one other stock I do want to bring up that was pretty wacky was WKEY. I want to bring up that last stock. That was another wacky little stock that had a nice move. You can see this one right here. That one just added nowhere at one o'clock. It just literally ran from like $7.30 all the way up to about $15. It was almost, it was, it was almost this, you know, it was nice to have the japan. At least that thing went up nice and slow. But this thing just like boom, went out of nowhere. And you know, sometimes we get these stocks in the middle of the day. And it did get halted a couple of times, which freaks people out too. But that one also was a pretty good mover. But anyway, that's the best tomorrow. I mean, that was yesterday. Let's talk about today. So we got a couple of, got a couple of good stocks that are moving. Listen, today is Friday. Just be, let's be very careful. We know Mondays and Fridays are days' pays. Not days for home runs or doubles and triples. Okay? So don't get too cocky today.  You write down your days. You, because you know, I love a desk calendar because you can go back and you can look at it. How do I do on every Monday? How do I do on every Tuesday? How do I do on every Wednesday? When you get to the end of the month, you know, boom.   But let's go through the watch list because there are a couple of decent stocks that are moving. I want to start off the FSR. So FSR, you know, looking at it right here, it's got a, you know, it doesn't have a huge iceberg order, but I'm going to bring it up over here so you guys can see it. But you could see it had a really nice run around 830. And then all of a sudden the big iceberg order started showing up around 2230, 2250, 2270. And it's having a tough, look, another guy just showed up right here, right around the 2235. So if you're wondering why stocks break, don't, you know, don't break resistance levels. Well, I can only tell you what I've learned being in New York and you've seen, you know, over and over again, because these guys are having a tough time breaking it. It's, you know, because of those orders out there.  Don't try to overanalyze things. Okay. Try to follow the money. A couple of the stocks I want to, there's about a few of them. ZKIN, another one. Great pop. Had a great run-up. There's another stock you could see here. Stock has done phenomenal. Not only on a day trade, but also as a swing trade. And this is basically, I always tell everybody, how do you become a good swing trader? Well, you got to be a good day trader first. How do you become a good option trader? You got to become a good swing trader first. If you go from options to swing to day trading and doing it backwards, okay? It's 10 times harder to do one versus the other. Start doing the easy stuff. That's day trading. Because if you saw that happen, go consistently going up, you probably would have jumped into a swing trade and boom, now you're waking up. Stock went to 14. That's how you do it. But anyway, as a day trade, she's kind of flat right now. I'll see how she opens up. Not really seeing too much action out there on the iceberg orders, but that pretty much does that. SPCB, it's another one. So I'm keeping a close eye on this one. This stock has been having a tough time. A lot of you here know this because we've been watching him all morning. So we had that big run-up right here around 820. And you see that red line? There's this guy even sitting out there for about 90,000 shares. He's been holding it down. But then you have another guy here for 65,000 shares that's supporting at 280. So unless that guy gets executed, which it looks like it wants to do it. You know what I mean? I'm just debating it. They're probably waiting until the market opens up. But he looks pretty strong. A couple of other people just showed up there for 30,000 and 20,000 between 312, 315 and 318. But that guy gets done. I mean, this stock could be off to a raise. Listen, I don't see anybody else out there. 340, $4. Look, $5. Look, there's nobody out there. There's nobody out there. 16, 17, there's nobody out there. So we're going to keep a close eye on that space B. That one looks pretty good. S-N-E-C. Yes, I'm sorry. This one also. Good move on it. 81% of stocks up. Nice little trend from 5 in the morning, but then it kind of died. Most of us are probably not even jumping in here until like 740, 7, 8 o'clock in the morning. But she's kind of like dead right here. So let's see how she breaks out. She's got good volume, 21 million shares. Not really a nice trend like the other ones, but we're going to keep an eye on that one too. We also got this L-K-C-O. Now, I've got to mention, this stock actually did well yesterday. There's another stock that we did trade yesterday. Let me bring it up and show you what it looked like. Nice little move. She did a little, she popped, she did a little bit of shake, does this crazy pop, did a little shake, popped in a shake. So this one was kind of hard to trade. So please don't misconstrue $2 stocks that they're easy to trade. But she's got good volume, 23,000 share. Buy it right now. Hovering just below.  It's got big support levels around 2. If it holds here, the stock could go up. Nice beginner stock. If you're someone that's just starting out and afraid to jump in, you're one of those deer in the headlights, this might be up your alley. IDRA. This time out. Crushed. Crushed. Look at this thing. Pharmaceutical stocks. Cyber traders. What do we know about stocks that get really beat up that are pharmaceutical stocks? What do we know about them? What do we know? Exactly. Amy, Lita, who else? Come on guys. Everyone knows the answer to this. They don't come back. They don't come back. So I feel bad for the person that owned it and was depending on this company who's going to do well. But listen, they don't really come back. The only thing you've got going for yourself since April until November, it's holding here pretty strong. That's the only thing. Okay. All right. Another one that we got on here. So that we got that. We got that one. And last, I'm going to bring one more. Not a really big list. SOS. So that was also, I've got to mention, was another nice runner yesterday at 10 o'clock to stock ramp from $760 to $9. And then you can start seeing, you know, the icebergs orders started coming in making lower highs. And then obviously came right down to $740. Listen, you can't go broke taking profits. There's a lot of opportunities out there to trade. Don't be misconstrued at somewhere faster than others. But when it comes to, when it comes to trading, there was, there was a lot going on as of Thursday, which is perfectly normal on a Thursday. All right. So anything I'm missing, I did not call out. DR, Wayne says, Trace Station has DRA, I-D-R-A on the short list. Well, listen, it traded 11 million shares here all morning. So if it holds here, I, you know, how much lower could a $2.0, maybe $2.0, but I don't know if that would probably happen. I think worse it might drop down to maybe a dollar, but, you know, there's a lot of support here. I probably would say it, you know, it probably stuck here for a while. Anything else? I think that pretty much does it. All right, listen. If you're new here to Cybertrain University, listen, we had over 200 people, over 200 people yesterday attend the open house that we did on Thursday, which we do every Thursday at 12 o'clock. I have to thank all of you guys for coming. I know that some of you are watching on YouTube. I know a lot of you here registered and want to jump into trading room and do that trial.  We don't tell anybody what to buy. Your goal is to watch the other traders and see if they make money doing it. Okay? That's your ultimate goal. It's not about me. It's not about my fellow instructors, Josh or Rich or John or anybody. It's all about, you know, can you do this and all the way you could do it is watching if they could do it. So just be very careful. Talk to the education advisor. Let them do your walkthrough. Let them give you a little, a little bit of an orientation, what to expect in the room because you want to go into it and get discouraged. Okay? And if you're new here and you watch on YouTube, Facebook Live, if you want to come and join us, you're more than welcome to. Always like us, friend us. Click on the bottom. Click on that little bell to get our alerts. And, you know, the worst thing that could happen as you find out it's not for you. That's the worst thing. Okay? Nothing to lose. I just want to do one more trade. One more stock. I want to look up. Trader K just came up here. He says the CLVS. So the CLVS has got a nice little push in it. It's up about 90%. It's up a dollar. It's not a bad looking stock. I like it. I'll give you that one. You know, she's pretty slow. Stocks took a big hit from 1120, which is what I like. Okay? So, yeah, I'll put it on there. And with all the swing trades, everyone, the market, I forgot to mention it before we leave. The market got really beat up yesterday. I mean, we saw that it got really, really crushed. So listen, we had a huge run. We had a huge run in the market. Come on. Seriously. We really did. As a good day trader, though, we're very conservative. So just be very careful. Tech stocks, inflation. And if you don't know what inflation is, you might want to look it up. Okay? So, we borrowed a lot of money from two administrations to fight this coronavirus. And you know what? Someone's got to pay for it. And inflation is obviously going to go up. It's one thing the market does not like. Okay? So if that happens, there's some really good news. That means we can make a lot of money going short. And I know some of you are scared of it, but you think shorting is scary. You should be more petrified to trade an option. It's the same exact thing. Okay? Just remember, whatever goes up comes down twice as fast. Jeff's saying a good short and plug. Yeah. Well, let's see if it breaks its support level. But look, we had a nice listen. We had a run and plug from November, $10 to 70. Come on, seriously. What is that? 700%? What are you going to make that? You know? And you're crying now. Oh, it's going down. But listen, if it holds, plugs holds right around 31. That's good. If not, this thing is dropping into 20s. All right, guys. Good luck. Happy trading. We'll be starting commentary here in the room, in the cybergroup room, in the next, like I said, we've got about 10 minutes. And everyone here on YouTube will be back here at 2.30 for the afternoon. Good luck, everyone. Happy trading. Be safe. And then I'll see you. Enjoy your weekend. Okay. Have a good day.


International Youth Service Corps have been advised to see beyond the white collar jobs by engaging in schemes, acquisition and other entrepreneurship programs to be self-reliant and boost their economic status during and after their service year. The call was made at the opening ceremony of the 2026 Corps members of the 2024 Batch A-3-1 Orientation Corps in Kadrona State. The state coordinator of NYSE, Hassan Tara, said the scheme has made provision for a skill acquisition, ICT, an entrepreneurship program for Corps members to learn and improve the assistive livelihood in various areas, noting that white collar jobs are no longer available to accommodate all graduates. He charged Corps members to desist from a discipline and area to film the tannishies images of the scheme and their family. Excellency, the Executive Governor of Kadrona State in 2024 have almost doubled the budget for Corps members in the state and by God's grace we are going to assess all this money that he has given to these Corps members and all their welfare safety is being guaranteed by the state governor. Also, the Kadrona State Governor Ubasani Uri was represented by Commissioner of Human Services and Social Development Rabi Salisou said the government has put adequate mechanisms to cater for the welfare as well as security to safeguard the lives and properties of citizens and Corps members deployed to the state for national service. My dear compatriots, consider your posting to Kadrona State for the one-year national service as a rare privilege to experience a different social, cultural environment in the view of the customopolitant nature of the state. Kadrona State is a home of peace and is a home to you all. I encourage you to contribute your quarter to the development of the state by extension and our dear nation at large. I assure you that the state governor will continue to work relatively with security operatives in assuring all the residents of Kadrona State including Corps members who are going to serve in the state maximum security. You can sleep with your two eyes closed. Also, speaking on the economic hardship in the country, the state government reiterated its commitment to increase social budget allocation for Corps members to cushion some of the economic challenges. Clearly at first, as they posted me to Kadrona, I was even scared of the environment and my friend motivated me to advise the United States as to just go and visit them first. I would like the environment. So actually, as I drop the welder and the environment, I love everything. Coming down to the camp again, seeing the camp environment, I enjoy the camp environment, everything, the securities and everything is intact. I've had a very, very nice time. The instructors are nice, the officials are extremely nice, the maintenance in camp actually take out times, take care of us. The meals are actually really nice and the roads are good, contrary to the roadblocks that we've been expecting. It's fine. It's going fine. It has been going fine so far. The place is nice. The place is okay. I love it here. I love it in the camp here. Hello. Hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


This is Moshumi Parvin from Bangladesh. I work with a project under Ministry of Disaster Management and Relief. I am a group member of the government group network for working on climate change mainstreaming, planning and budgeting process. By informing with the group, I have learned a lot. I'll highlight here four key points that I have benefited from myself as well as my country. First of all, by sharing ideas with the group, I understand the cross-cutting issues around the world, particularly across the member countries. Second one is, it helps me to pick good ideas from the member countries. For example, Gambia is promoting public-private partnership by promoting tourism companies to come in the climate change investment process. The government and the tourism company make a good partnership and they are implementing very well. I have learned we can replicate the ideas in my countries in Bangladesh where public-private partnership is not that much effective. Another point is, by exchanging ideas, it helps me to showcase the good practices that exist in Bangladesh right now. For example, we have showcased some good practices like climate finance landscape in Bangladesh and we have suggested to introduce and adopt and implement climate-fiscal framework in Bangladesh. I have got ideas by exchanging with the group members, so it helps another way. Last point I made that by exchanging the ideas with the group, I can get the impression what good practices are moving around the world. So I can raise the issue with the policy makers. Often I will get a chance to attend a meeting with the policy makers, the government officials, NGOs and other stakeholders. So I will get a chance to raise the issues and raise the voice to introduce the good practices. I have learned from the group.


Combining satellite-based passive and active microwave sensors has the potential to improve global scale estimates of surface soil moisture by adjusting them to the same range and preserving their dynamics. The methodology developed rescales volumetric soil water content from AMSRE and degree of saturation from ASCET against a reference land surface model data set using a cumulative distribution function matching approach. Merging these different satellite products increases the number of observations while minimally changing the accuracy of soil moisture retrievals in transitional regions, delineating the boundary between sparsely and moderately vegetated regions. The combination method developed can be applied to existing microwave satellites as well as new missions, enabling the development of a long-term global soil moisture data set that enhances basic understanding of the role of soil moisture in the water, energy, and carbon cycles. This article was authored by Y.Y. Lu, R. M. Paranissa, W.A. Derigo, and others. We are article.tv, links in the description below.


Well, Nancy and I leave tonight for the Economic Summit in Bonn, and our state visits to the Federal Republic of Germany, Spain, and Portugal. And I'll also have the opportunity to speak to the Parliament in Strasbourg, France, to mark the 40th anniversary of the end of the Second World War in Europe and the beginning of an unprecedented period of peace and prosperity. Forty years ago, World War II was nearing its end, and much of Europe lay in ruins. The destruction and terrible human losses were matched by fear and doubt about an uncertain future. We leave tonight for a Europe that is rebuilt from the disaster of war and morally restored from the despair of 1945. The strong, confident alliance of free people who've done this can take satisfaction in their achievement and look to the future with confidence. So we leave in this journey infused with pride and hope. We're proud of our Atlantic partnership that anchors the freedom and democracy which our nations have created from the rubble of 40 years. Our hopes for the—or 40 years ago—our hopes for the future are high, despite the hectic pace of change in today's world. We know that by allowing the freest expression of individual human aspirations, we can surmount our challenges and build a more secure and peaceful future. We know this because of a simple truth which makes our society strong—freedom works. The Economic Summit Conference, now an annual event, spans the free world from the Federal Republic of Germany to Japan, providing the clearest possible symbol of our modern economic independence. At this year's summit, we will strive for agreement to meet the challenge of greater growth on which our good fortunes depend. In doing so, we will work to ensure cooperation among our economies. We approach this challenge with vigor and vision and optimism. We visit Europe determined to carry forward the spirit of peace and reconciliation among old adversaries and the power of our democratic ideals. The friendship between the American and German peoples—a great blessing that has grown rich and strong over our three centuries of shared national experience—is dramatic proof of how former enemies can be brought together again. What better example of the success of democracy could we find than the strong new democratic systems in Spain and Portugal? We are pleased to salute the accomplishments of these countries whose contribution to the new world was so great. The partnerships that we have built in Europe, the Atlantic community and across the Pacific are the underlying foundation for the freedom that protects peace and security and strengthens the prosperity for hundreds of millions of people across this planet. So we leave tonight eager to see again our European and Japanese friends and confident that together we can meet the challenge of expanding freedom and of preserving the blessings of the peace that we share. So thank you all and we'll now say goodbye and God bless you all.


Brady in the end zone, takes the snap, looks, fires, passed, batted up in the interception and returned for a touchdown, Titans, Logan Ryan! That's a great chance for Logan Ryan too in this place. Just take about the irony of all of that. He dropped one earlier in the first half that would have been the same thing. This was even better.


I want to hear your voice. You want to hear my voice? Okay, here it is. I'm going to do it for Bob's Talk 101. Here it is.  UGK heard Aldi's album Okay And he was going to do some stuff with Scrooge Okay, PMC? Yeah, PMC was He was going to do some stuff with Scrooge So he says, Scrooge, man, who's this guy Sound like the Hosley brothers So Scrooge said, that's my goddad He said, no, man He said, yeah, can you get him? He said, yeah, call me, come on over As a matter of fact, he just left Wow He said, man, I got a song So he played the song And I've been good to you by the Hosley brothers Okay And I listened to it I said, yeah, I know that whole song, you know So he said, oh, man, I got a track That I want you to do And he had sampled To live it up Song, I mean, ain't I been good to you And I said, yeah He said, you think you can do something with that? I said, sure I said, well, don't play it Because I don't want to get in trouble Ronald I said, we'll come up with the right words And, you know, I can kind of, you know, do it He said, okay, so it took me about five minutes And I sung what I thought would go on the track Yeah And they loved it, UGK loved it I said, man, let's record it Let's go to Skip Hoffman in the morning and record it So I said, okay So when he said Skip Hoffman I'm thinking it's just a studio in the house Or something like that When I got out there, it was a million dollar studio Ooh So now I get nervous I'm like, whoa, man, what is this? Man, this man had a mixing console Probably wall-to-wall in there Probably over 150 tracks on the board So I'm like, okay, this is the big lead Wow This is it This is what they're shooting for Yeah, man, so now I kind of get a little cocky And I say, so, all right So I'm singing the song So everybody's telling me how to do it So now I realize Now, this is the one This is one day Yeah So I realize that, man, UGK's sing UGK's sing, y'all trying to tell me how to sing Exactly So Skip Hoffman said, I like that Can everybody get out of the studio Let him do what he do She said, that's the best thing to do Let him do him I like that So I did the song And it was like in probably about three or four minutes I finished the song That's cool And they was all going to lunch And when they came back It was a wrap I was sitting outside by the pool And I heard all this screaming in the hall And then jumping, man And all come outside I said, man, come over here I said, what's going on I said, I don't like it He said, no, it's a hit We love it So I'm like, okay I guess it's going to be official Well, some kind of way that song got out Okay You know, because they mounted it right then Some kind of way that song got out And me and Pimp ride And we going home And the song come on the radio That same day That same day That's the one thing I don't know Renetta was saying something like that About which song was it Bar-Baby Bar-Baby Bar-Baby came out like that too Nobody does that anymore Not in the same day How does that How is that possible? Man, these guys were professional They knew how to do them play Call a playlist now And Pimp was just incredible in the studio Working with him So he already pretty much knew what he wanted Oh, so And him and Bumbie Was incredible That's all I could say about those guys Especially Bumbie He was the type of guy He could write his verse And read it And ball it up and throw it in trash Go to sleep And wake up Pimp said, Bum, go lay your verse And he go one take and it's done So he was one of the guys That first seen do that And I was like That young man is amazing That young man got a gift So I always said Bumbie was for his time Because he was so good with words And he could write stuff and just Kill it Man, kill it You want that one day? You want me to hit that one? Please One day? Y'all, you want to hit it? Acapella? You want to hit it?