Hey, welcome to my talk of how this ability drives observability. I'm Mateus Aguilera, I'm a software engineer at CubeShop and a working trace test at OO. I'm passionate about testing observability and the vault and here are my links for LinkedIn and GitHub. If you want to reach out to us questions, just I'll be there and we talk. So let's start with what's observability? Observability is the ability to measure the internal states of a system by examining its output. Assisting is considered observable if the current state can be estimated by only using information from outputs, namely, sensor data. That's the definition from Splank. So what does that mean? Well, we have sensor data and the main pillars of observability are metrics, traces and logs. So in this talk, we're focusing on traces. But what's trace? When we talk about distributed tracing, it refers to methods of observing requests as they propagate through distributed systems. So it means that when you send a request from a system that has tracing enabled, it will be able to give you a map of everything that was done within that request. So if it had to reach for a database, that will show up in the trace. So what's a trace? A trace is a group of spans with parent-child relationship. But what's a span? A span is a data structure where it contains a unique identifier and you can attach data to it as a key value structure. The nice thing about spans is that you attach information that is related to the operation that's being executed. So if you are executing a HCP request, you would have HTP information there, like what was the status code of the response? What was the URL that we're trying to reach? What was the methods? What was the headers and all those kind of things? Another thing is that our span has two timestamps, one for its start and one for the end. So for each span, we know the duration of it. The nice thing is that because the span is related to our operation, the time of the span is basically the time of the operation. So if you know the duration of the span, you know how long it took for that operation to run. So this is an example of a trace. So what does a trace look like? I got this image from the internet. And the nice thing about traces is that even though I'm not sure about which system is that, I can't know what's happening based on the trace. So I know that someone is trying to purchase something using the order of service. In order to do that, the order of service needs to verify the user and for that, it uses the user's service. After verifying the user, it updates the stock of the product, saying which cart it's going to be used. And for that, it uses the stock service. After that, it tries to find an order inside Mongo. And that trace is incomplete, but you can understand what it's happening. So that's great, a great way of understanding systems. So let's talk about how we usually instrument our code. So first of all, we start by developing the product. So we are adding features, we are logging, user registration, and all those things. But then we deploy the application and we figure out that we don't know what's happening production. We can't know. So we need a way of observe it and see if everything is fine. So what we do, we add instrumentation. So now we know what's happening. We know traces, we know metrics, and those things. We keep executing this loop, but sometimes we find bugs. And every time we find a bug, because we have instrumentation, a part of the instrumentation purpose is to help us understand what's happening, we are going to use instrumentation, the telemetry to help us find a bug and try to fix it. But now we have two possibilities. Here, you find a bug and you can solve it because you have good telemetry and you knew exactly what was happening based on what the telemetry was telling you. So in that case, that's awesome, your telemetry is good, in a good shape, so great. And then you can go back to your cycle so you can just keep adding features. But what happens if you don't find the problem based on instrumentation? That's bad because you invest the time and resources into adding instrumentation and trying to get it right, but in the end, it didn't work. It didn't help you find a bug. So you have to keep adding instrumentation and try to improve this instrumentation. But that's okay because observability is hard, it's not easy to get it right. And part of the problem is that adding instrumentation and the development cycle are in different stages. We do not care about observability when we are designing our code or when we are coding something. So this makes it kind of hard to get the instrumentation right. Maybe because when you finish coding and you start adding instrumentation, you take a look at your code and try to ask yourself, well, what can be instrumented? And that's a tricky question because you are trying to instrument everything that you can. But should you? Maybe that's bad. Just as over-logging things is bad, over-instrumenting code is bad as well. So you should be asking what you should instrument before instrumenting things. The other part that makes it very hard to get observability right is that we cannot test it. We only find out that something is missing or that telemetry doesn't help at all. When we have a bug, we try to figure out what's happening and we can't. That's the problem. So wouldn't it be nice to be able to test your telemetry before deploying to production? It would be great. You could solve a lot of problems doing that. But now you have another type of test and that's a burden. You have to maintain another type of test and you already have contract tests, integration tests, end-to-end tests, unit tests. Well, that's a lot of kind of tests to maintain. But wouldn't it be amazing if you put more than tests for your application telemetry and you could actually merge some of your tests together? So here I present to you trace-based testing. You might be asking what's that? So basically trace-based testing is a test method that leverages your tracing data to make it accessible to our tests. So we can use that information to assert the behavior of the system. Okay, but what does that mean? How does that compare to my existing end-to-end tests? Sure, but let's take a look. So imagine that you have an end-to-end test. You have a test runner. So it can be a simple function written in JavaScript or it can be an external test runner such as TestQ. And so the first step is to trigger your test and that will trigger your API. We're going to send a request to our purchase API. We're trying to buy some product. For that, the API will reach the database, do some checks, and it will reach the product API. Product must be available, right? And the DB will be accessed again. Next, probably we have a shipping API. We need to create an order for shipping. So, okay, how do I do that? Probably run into the database and probably I do not ship myself, so I have to reach another external service that I do not control. So I hired a company to send the package for me. That's great. It works, but now how do I know that the test passed? Because, well, I might have a 200 status code in the purchase API returning to my test runner, but is that enough? Because we don't know how that communication works. Is that synchronous? Is that asynchronous? If it's asynchronous, that 200 status code doesn't mean nothing for us because that might be successful, but we have a queue and we have something executed in the background and it fails. And that 200, it's a false result for us. So to ensure that everything's working, we have to add complexity to our test. We end up with a lot of secrets and a lot of setup to reach for each one of those dependencies and see if they're right. Like, did the product stock changed? Did I get a shipping order? Did a company that will ship the product got my order? That's the kind of thing that we try to test because that's the only way of ensuring that everything's working, but that's a lot of complexity.  Imagine that you just got hired and you have to write an end-to-end test. That's impossible because you don't have enough context. You might be from the team that maintains personal API, but you might not know a single thing about shipping or product. So that's very, very hard. To be able to write those kind of tests, you have to be an expert in almost everything. Or you have to have a team of experts writing those end-to-end tests. That's not good. That's like we're concentrating knowledge. But OK, but how does trace-based testing compare to end-to-end tests? So let's take a look at how that looks like. So we still have a test runner. Same thing. Can it be a function? Can we external runner? And we trigger the API. OK, that would trigger a database operation. But the difference here, now every time an operation runs, I send telemetry to my trace back-end. So I have a new trace. I have spans going from my application to my trace back-end. OK, and the flow, the flow continues. I brought in the API's hit. Database is executed. Then I have new spans going to the trace back-end. Same thing for shipping. We do everything, and we have everything working. Nice, that's great. Now, we kind of know what's happening because we have the trace. We have the blueprint of the entire operation. The last part of the trace-based testing, fetching the tracing and executing the assertions. So that's exactly what we're doing. We are going to get the trace from the tracing back-end, and we are going to run all the assertions that we have against it. So OK, but what's the advantage of using that over my existing end-to-end tests? First of all, you test your telemetry. And that means that when you have a bug in production, you will not get a surprise when you take a look at your telemetry. You know how it should look like. That's great. So again, how does that work? That's runner, triggers system, systems do some work, send traces, and we get the trace back and execute the assertions. So every time you execute that operation in your system production, we know that trace should look like that. So have a way of searching that. It creates a feedback loop that makes you write better telemetry to be able to write better tests. What does that mean? Imagine that you're trying to test something using the trace. If your trace doesn't have enough information, you cannot test everything you want. So you have to improve your telemetry because otherwise you have bad tests. But as soon as you improve your telemetry, you can improve your tests. And by improving your tests, you can improve even more your telemetry. So it's a loop that it creates. And it reminds me when you start learning about DDD and you start writing tests for your code because you want to think about how to design your code in a testable way. That's the same thing. We can apply to the DDD here with this strategy. So for example, let's say you have an application, you don't have any telemetry at all. And you want to start writing tests and use telemetry. So what would you do? First of all, you write a test. You expect to have telemetry. You expect to have a span named getDataFromDatabase. Nice. But it's failing because you don't have telemetry place. So what do you do? You add telemetry to your code. And now your test is passing. But probably it's not the best code that you ever wrote. So you should be refactoring that before merging. And then we can repeat the cycle. And we can write a test with things that we don't know about. We don't have telemetry for that yet, but we have an understanding of how we want to see that in telemetry in your trace. So we write the specs for the telemetry and then we implement it. That's a nice way of adding telemetry because if you've set off looking at your code and thinking, hey, what I can instrument here in my code versus what should I be caring about in this function? Like I'm testing a user registration. What should I care about in this flow? As soon as you write a test about it, you have a plan. You just defined a plan of how you wanted to make your traces look like. And you just have to implement that. You don't have to think about what should I implement. And you have a specification for that. That helps a lot. And it enables deep assertions test results without assessing internal dependencies such as microservices or databases. So as we saw before when we were writing our end-to-end test, we had to set up the test runner to be able to access the external dependencies, other microservices just to make sure everything worked. But that's like a lot of complexity. It's huge. And just thinking about that, it's overwhelming. And that's overwhelming for someone that's working in a company for a while. Imagine that you're just starting. It's impossible. You have to be an expert to understand all the requirements and all the relationships between the services. That's very, very hard. So if you have trace-based testing, you have the trace. You have the blueprint of your whole application. And you can just take a look at that blueprint and understand what's happening. You don't have to be an expert and know that the product API creates orders because does that make sense? Probably not. But who would guess? Maybe it's only the people that work in the product API. So the fact that you do not have to have understanding of the whole application to write end-to-end tests, that's amazing. You can start using trace-based testing to understand your system. And as you go, you can add more and more details to your tests. So you don't have to create a huge test at first. You can just use that for exploration. So I think that's one of the most powerful things about trace-based testing. Okay, now an example. Take a look at this trace. This is a trace from our demo API. And even though it don't have any context of how that is implemented, you can have understanding of what's happening based on the trace. So we have the trigger of the trace-based testing. Then we see that we just triggered a HTTP that is getting the list of Pokemons. And in order to do that, it executes in the database a findManyPokemon and then accountPokemon. Both of them are in both graphs and both of them generate select statements. So I know that when I trigger this endpoint, I'll have two select statements, one for finding all the Pokemons for me and one for counting them. I have no idea how the code looks like, but I already know how it works. That's a ball of trace-based testing. Another thing is that traces are data. So if you generate the telemetry the same way across our environment, you can run the exact same test in where. So you have to test your createUser endpoint, for example. In production staging, Dev, they work the same. You might have like, you might use a mock the Dev environment, but the telemetry should be the same. And because the telemetry is the same, the trace would be the same as well. So you can use the same test because we do not rely on connecting to different services or connects to database or those things. You don't have to care about secrets. You only care about the data and we are just testing that data. So you can start using tests across multiple environments. I think that's very powerful. So about the demo that we're going to show now, I'm going to use trace test to execute it. It is a API to manage Pokemons and it has dependencies on Postgres, Redis, Rabbitin, Q and Poke API. Let's say API that returns Pokemon information based on the Pokemon ID. And about trace test, it's open source. It's license, it's MIT. It has a web UI that allows you to create and manage tests. And if you are not a fan of CLI and test files, you can use that to create your tests in random, just as both as the CLI. And then you have the CLI and test files that you can use to store your tests inside your Git repo story. And because you have CLI and test files, we support CISD. Nice thing about trace test is that you can start using the UI and then migrate to the CLI with no effort because the UI is able to export the tests as a test file for you. So you can write all their tests in the UI and then just export them using the UI. So that's great. So let's go to the demo. So now we are going to try to achieve three things in the demo and for that, we're going to use the Pokemon API demo that we have. First thing is we're going to write a test for the Pokemon important endpoint. That endpoint is already instrumented and let's check how that works. So I'm already running the API and trace test locally. So I'm going to create a new test. Well, the API is the ACP API, so it can just create a ACP request. Name, it's a import Pokemon. And description, import invalid Pokemon, nice. So now I can feel the details of the request. So it's a post request to, I'm running the Pokemon API on port 2001 and it's Pokemon slash import. There is no organization. The content is JSON. Let's go to body. So ID, let's choose a Pokemon, 25. I think that's Pikachu and let's create it. So as soon as I create it, trace test will send the request to the API and wait for traces. As soon as the traces are complete, it will show them to us so we can start writing our search treats. So here we have the whole trace. We can see, we can zoom. So that's the trace, nice. So let's try to write a test for that. For example, for every integration test, I expect that the response that I get has ACP status as 200. So let's assert for that. So ACP status code is 200. So that's an insertion. Here we have a selector. A selector is a way of selecting which spans are going to be used to run those assertions. As is a very specific selector, we get just one span out of it. So let's keep like that. So it's the Pokemon post-Pokemon part. Status code equals 200. That's exactly what it means. We have that fuel in because trace test auto completes the values using the values that we have here. So let's add the assertion. So we can see that best. That's amazing. So let's go to another, let's add new assertions. Like, I know that there's another HTTP call here, the HTTP that we send to retrieve data from that Pokemon. What if we check for that as well? So it's the status code. Let's make sure that same thing. I'll not change the signature and status code equals 200. Let's change and we have it passing. But we have a pattern here. Like we are searching for all the HTTP status code. So why don't we write a custom assertion that checks only for trace test span type. I want that to be HTTP. If you see that will give us two spans. The post, that's the triggering span and the other one because both are HTTP and I can check for the 200. That's great because now we have two assertions. Let's delete this one and this one. Oh, okay. So we have, I edited this one. So that's why it changed, but that's great. We have now a better assertion. So let's just publish that. So we have this assertion. The other ones appeared because I have deleted that. So we have this assertion that matches two spans and we ensure that both spans should have HTTP status equals 200. That's great. Another thing that a lot of people like to do is, okay, I have this trace and I want to check for a synthesis, high synthesis of how would I do that? So let's check. Like one thing that we know here is that the Pokemon API, it sends a message to a message queue and then that message is consumed. And then it's imported. When it's imported, it get the Pokemon from Pokemon API and then save that into the database. So let's check the duration of that span. In trace test, we have some attributes such as trace test span duration that measures how long that span lasted. So let's add an assertion for that. This is a long selector. We can make it simple because we know that the span name is unique across that specific trace. So we can just use the name of the span as selector. Nice. So I want to make sure that the duration is less than, let's say two seconds, one second. Nice, it passes. Now I can see that one seconds, that 596 milliseconds is less than one second. That's why it passed. I can publish that test and we have the V3 because we applied V2, containing the two as the ACP assertions and then V3 containing this assertion. Okay, okay, that's great. Oh, we're ready to do that. We can assert other things as well like how long it takes for database operations to run and those things. Now that we created the first assertions, we can start running the test and those assertions that we created, we'll be executed right after the execution of the triggering transaction. So right now, trace test is trying to send a request to the service and waiting for the traces. Okay, so we got the trace back and if you take a look here, we can see that the assertions got executed and everything passed. So we know that the status code is 200, the Q that the message from the Q was executed within 500 milliseconds, so it's less than one second and the other ACP request was executed as well. So that's great. And let's take a look here like in the part Pokemon. If you hit all, you'll see all the attributes of that span. And if you notice, most of them are the default one from the open telemetry. We just have like a name and a service name. And that's bad because that means that this span doesn't contain any information at all, just the basic stuff. So we should fix that. Like imagine that we're trying to do something and for some reason we don't get the rest of the trace. We're not sure like what Pokemon we're trying to report. So we're going to write a test to test for the attribute Pokemon.id. But for that, I'm going to use the test definition. If you go here, test definition, you can see how you write a test using trace test. So I'll copy this file and simplify it a bit. Now that we have imported the test, let's change it. So we have a selector. We have, we want to select the span name import Pokemon. And we want to make sure that it contains the Pokemon ID equals 25 because that's the value that we are using in the body. Okay, let's try to run that test now. So trace test, test run, definition file is API, trace testing, test, let's wait for results and add color. Okay, let's see what happens. We can check the result here as well. So press the page, we see that there's a new test running. Let's wait here. Okay, we can see that we have a failing test because now the import Pokemon, it has a Pokemon ID equals 25, but the actual value is an empty value. So that means that our test works. The only thing that we should do now is to fix the application to reflect that test. So let's try to do that right now. Let's try to find here, import Pokemon. So we have here, create span import Pokemon. And we have the Pokemon ID here. So let's try to set attribute. Let's call it Pokemon dot ID and the value is Pokemon ID. With that, that should pass. So let's try it, let's stop. Let's rebuild the application. Now we can try to rerun that test again. Let's do it, let's wait for the result here. Okay, now we see that we have no test failing because the import Pokemon now has the ID 25. And if we go to that span, we will see that ID here. So this is a nice way of improving our telemetry because before you even add the code, you create a plan, see what's missing, create a test to cover that, that case, that scenario and then write the code for that telemetry. One thing that's worth mentioning, we use trace test to test trace test. And when we were adding telemetry to trace test, the way that we did was by writing tests. So first we wrote tests, everything was failing and then we started instrumenting the API. Doing like that, it made that process way easier than it was. For example, when we were building this Pokemon API, we tried to build the API and then build all the instrumentation without any plan, just looking at the codes and try to implement it. But it wasn't very clear what the application was doing. It was hard to read the trace. As soon as we stepped back and thought about what the instrumentation should look like, that was way easier and we don't have any instrumentation to make it more clear. So that's how you can use trace test or any other trace-based testing tool to guide your instrumentation. So that's all for the demo. And if you want to know more about trace test, here are the main links. You can check the code and open issues or PRs in your GitHub handle the story. And if you have any question and want to discuss with the team, we have a support channel that you can join and ask the team for how gain feedback is more than welcomed. And now I'll save some time for questions. Have a great day.


I thought they'd never go on. Well, Nancy and I are delighted to welcome you to the White House. We're pleased and honored to have all of you here tonight. This room is often used for state dinners honoring visiting heads of state. And it's fitting that we too share this room in recognition that you are also heads of sovereign states. Our federal system of sovereign states is today as vital to the preservation of freedom as it was in the time of Jefferson, Adams, and those other far-sighted individuals would be revered as our founding fathers. They envisioned a system that would secure the greatest degree of liberty while at the same time be functional and efficient. They knew well that if too much power and authority were vested in the central government, even if intended for a noble purpose, not only would liberty be threatened, but it just wouldn't work. Jefferson warned, were we directed from Washington, when to sow and when to reap, we should soon want for bread. I think during the last decade and before we've gotten a taste of just what it was that Jefferson was warning us about. So much power had centralized in Washington that frustration and stagnation ruled the day. The federal government taxed away the available revenue and set up a confusing web of regulations and bureaucratic controls to be complied with in order to get these resources back. Furthermore, the rules and restrictions to a large degree were coming from far away, unelected officials. This neither worked nor was it consistent with principles of American freedom. Over the last three years, we put a stop to this ever-increasing centralization of power. Through our block grant programs, through our efforts to get control of federal spending and taxing, we've halted what I consider to be a very ominous trend. People are no longer looking to Washington to solve every problem. As a result, we're seeing a renaissance of direct involvement, whether in the local schools or in neighborhood watch programs, and the reemergence of state and local government as significant forces in determining the future of our country and the quality of life of our people. This has been accomplished with close consultation and cooperation with you and with other state and local officials. I want each of you to know I deeply appreciate the responsible, and in most cases, nonpartisan way that we have worked together to ensure progress in the area of federalism. There's still much to be done, and I hope we can build on the working relationship that we've already established. Technology today is opening up new opportunities at the state and local level, state government as some of the most competent and hardworking employees to be found in government at any level. And in the last few years, we've seen creativity and innovation as never before in the state houses throughout the country. Today, that vision of our founding fathers of a federal system of states is as viable, if not more so, than at any time in our history. So let us continue working together to keep faith with that dream. And now, would you please join me as I toast you, the governors of the states of the Union, and you can toast each other, and we can toast also to our freedom and to strong and efficient state government. We elected you, too. And though you are formally now engaged in a contest to retain that office, we still look upon you as a brother. And we're glad of the opportunity to come with you once a year in this formal setting. And I must say, in my experience, and perhaps in the experience of every governor in this room, you have extended the hospitality, the warmth, and, most importantly, the interest of your office to us, your brothers. On so many more occasions, whether in the Oval Office or in our states, then we might reasonably expect, for we know you have to deal with mayors and legislators, county executives, business people, and labor people, and just all sorts of people that it's somewhat remarkable how much time you spend with governors. I think perhaps there is a bias there. At least we hope so. The issues which concern us, Mr. President, and about which even we differ among ourselves and within our states are only as good as the men and women who enliven them. There is justice or no justice depending upon the passions and the caring of men and women, not just on the pages of a book or in the words on those pages. There will be a better education for our children than we had for ourselves, not only because that is important, but because it is necessary, but only achievable if we care to make it so and invest the time and the resources to achieve it. And whether it's the infrastructure of our country, our roads, our highways, our bridges, our dams, our buildings, sewer systems, our water systems, or it's our responsibility for the safety and well-being of our fellow citizens through law enforcement, for public health, or care for abused or neglected children, or infant mortality rates, words are words, pages are pages, and laws are laws unless we, the governors, infuse them with our care. We know how hard it is to be a president and a First Lady. And because all of us in this room have experienced at least a portion of that which you live. We know there are many nights where you must feel frustrated, tired, mad, but many more where you feel satisfied, glad, challenged. We do too. Or we would not be with you tonight. When we leave this city and go back to our states and try and infuse our political, governmental, and personal lives with renewed vigor and caring, in part because we were here, we will remember you and Mrs. Reagan, and wish for you the same. And we know it will be achieved. And so tonight, Mr. President, from your brothers, and I am pleased to say from one sister who has now joined the ranks, on behalf of the governors, I propose a toast to the lady who guides you, sustains you, passionately loves you, and to the President of the United States.


Hello everyone, this is financial author Amit Dan of amitdan.com On this channel you'll find financial travel and more videos just like the one you're watching right now If you like what you see, please give it a thumbs up and consider subscribing Hello everyone, so we have come to a place which is famous for different types of tea And we'll be ordering some teas and I'll show you the menu which looks like there are about 20-30 different types of teas And this is a very famous street food tea in Dhaka So we'll try it out and see how they taste like So let's look at the menu and then we'll pick some tea from the menu So the name of the store is Green Garden and then looks like they have juices Which has malta, orange juice, apple juice, papaya, banana and all sorts of juices And then we have tea, yogurt tea, chocolate tea, malta tea, orange tea, honey tea, masala tea And on the right side you can see the prices which are 20 Dhaka, 20, 15 Dhaka and some of them are 30 Dhaka So in terms of dollars these look like about 25 cents to 35 cents Then we have a lassi here which there are 5 different types of lassi And then they have regular coffee too, ice coffee, peanut coffee, cinnamon coffee, all sorts of coffee So a cup of coffee is 30 Dhaka to the highest one, I can see 70 Dhaka which is 1 dollar, lesser than a dollar And then there are different types of shakes So here is the store so once you order them then they will make it right here And then we'll try our tea Hello everyone, so we have our teas and coffees ready and then we have 4 different varieties here So the first one is peanut coffee which is a cold coffee And then we have the malta tea and this is the hot tea And then we have here chocolate coffee which is a hot coffee And then we have here regular coffee So I'll just try the regular coffee and the malta coffee and then we'll see how does it taste like So the regular coffee is very sweet and it tastes like instant coffee but there is a taste to it So definitely the taste wise it is a good coffee but it has lots of sugar in it And let's try out the malta tea So the malta tea tastes like iced tea but it has lemon and it's very sweet But taste wise definitely it's a very delicious and good taste But it looks like all of them have lots of sugar and it's got lots of flavor So that concludes the video of the green garden street tea and coffee shop I hope you enjoyed the video If you like what is steep please give it a thumbs up and consider subscribing And there is going to be a next video coming up so I'll see you shortly Thank you


And this is Daniel, Miguel, and I am Zebranta. And we need to present to you Taliesa and Propolups, which is an educational program that aims to promote cultural inclusion and diversity through the remixing of traditional music from around the world. But before we get into that, then we briefly present to you what is Propolups. Propolups is an artistic project which combines musical remixes with data visualization. Oh, sorry. Started by Ruben and I six years ago. Ruben creates new songs remixing traditional music from fragments from around the world. And we also try to open and share in different ways the process of the musical remix and everything concerning the musical sources. And the Propolups emerges from the simple idea. For example, let's take one fragment from a song from Jakartia in Siberia. From a song from by Franko, who wrote this musician, without changing the pitch, which is one of the compositional principles. Then we can maybe add to this fragment, to this mix, a fragment of the traditional song from Galicia in Spain and call expressions from distant places and cultures, playing it together in something that is old and new at the same time. And Propolups seeks to celebrate what is common and what is different. So we ask ourselves, how could we better communicate this idea? How could we share and open this process? And that's how we came up with what you see on the screen, which is an application that I made with processing that shows what Ruben is remixing in a live show. Using OSC messages, this application and here, which fragments are in play and display and locate them in a map, it also shows us some MP3 metadata, like the album covers or the titles, and also some musical parameters, like the volume at which the fragments are in play or how long the fragments are, which is translated and how fast the circles are spinning. In some festivals, people started asking us about doing workshops. So we began to ask ourselves, how could we translate this creative methodology to an educational context? How could we use this visual and compositional approach as a tool to work with cultural inclusiveness? So we started designing workshops that could last one day or maybe one week at most. When we heard of the Daniel and Nina Arcarasso Foundation, that had an open call to fund projects of about three years duration on average called Art in the Community. And that was another scale altogether of what we were thinking, but we thought, OK, why not? So we asked for help. And that's the whole team that are developing this three-year experimental educational project that we called Anthropolubes Workshops. So this pilot experience is being developed in the Macarena District in Seville, and this is our first year. We are working with this last September with fifth grade kids. And the kids in the school come from more than 30 different countries, and the school leaders and teachers have been already doing a great job at working with cultural inclusiveness. So it was a perfect fit to work with them. And what are we doing? So we are developing educational processes that try to combine three dimensions, the pedagogical, the musical, and the technological one. We three here are in representation of the technological part of the team. And our main goal is to be able to produce open methodologies, resources, and tools so that this experience could be replicable in other contexts. And now we are going to let the kids themselves explain what we did in the first session. This project consists of the first session called the Neocolubes Translations. This school that you see here represents our school. And if we play the school, and this little song here sounds like music, like a ball, so that it sounds like music from other countries we need help. And if you want to learn more about music, you can learn how to improve things with the help of your colleagues and friends. Spanish. And when we start to think about translating the anthropologist project to a workshop, we focus mostly in two areas, two challenges, or two questions. The first one is how to translate a musical performance, an individual musical performance, into a collective one. It was a big question, we discussed about it. And also how to create a meaningful experience, a musical experience with all the people. Because so we know what happens in musical, electronic, musical concerts. All the people are dancing, but we don't know what is going on. We don't know what's happened before, behind the screen. So when we think about making electronic music and remixing, we don't want this. We think how to avoid children looking at its devices. And instead of doing things more like dancing or whatever that makes kids interact with each other and also the people we see in the show provide some good information about what they are doing. So the solution we found, or we are exploring is to create new hardware that allows to interact with the software and allow the kids to interact with the software. The other main concern we are exploring is how to make this revolution. There's a friction between the high technology that we all like because it's wow, but they cannot be reproduced after in the school with pictures that may have low technological levels. It's a big concern for us. We will develop free and use free software and the solution. We want cheap hardware, so we will use Open Source hardware too. We want to reuse the actual hardware schools have. They have Android devices, mostly old and Linux computers. We want to have a new setup. So that's how we approach this workshop. Miguel and I will talk about these things and we will come back with more peculiar questions. Okay. First of all, I would like to thank you all and also to say that it's very good to be in a place where we do the project. So we are in Sevilla, we do the project in Sevilla and we have people from all around the world or Europe and it's very good to talk about something that is from here. Okay. So which are our values and our philosophies? Which is the point of view where we see these things and we try to avoid that. So we see technology as this reinforcement of human values. So we insist on bringing technology as something that helps this humanity and our relationships. Then also, as Daniel was saying, we insist on bringing tangible interfaces to make that the objects and the body will be the ones which trigger interactions and then it will be very intuitive to do it. So very human. So we bring the digital world into the analog everyday object world. And we try also to allow these new relationships between components that are not related in normal life. For example, making a photography interview to speak.  So we also try to design setups where the unknown is there and facilitate the experience of discovering without knowing what is going to happen because in that moment is when we step into a reality which is new. And if we have a few of us making this together we can find things which are not found when we are alone. So this is also another concept that we try to bring when we do the steps in the classroom. Also, when we do this new technological, music, educational environments we think also about these keys which are not interested about the normal classroom. So they are really shy or they are not interested. And then we say, okay, so how can we manage that to change it and to make that these kids are interested? And we find that making this kind of new interaction that you already saw, some of the kids which are usually shy, they become really active and they change their behavior. And this is very important for us. So now, with what do we do that? So you also, you already saw as they were showing this video about they were touching each other with these kind of components. So we have these kind of things that we start in the classroom. It's very low-tech, but we try to make them also available and adopting many things that we use in the classroom. We do the raspberry pies, the Maki Maki cables all over, okay? I will explain a little bit more about it. And where do we use that? So we use it in the classroom mostly. So until now, it has been used in the classroom. So we have to think about, okay, this is going to be, this Maki Maki here will be in the classroom. So if you put it in the middle there, there will be like 20 kids around. So we have to be careful. You have to think about that. And also we have to think about how to change in real time the configuration of this. Because we found that sometimes we think about the setup and when we are doing this, we see that it's not working. So we have to change it quickly. For example, this one has these parts and they'll have the first and those parts are too far away from each other because the kids are short. So we have to change it quickly. So we also have to think about, okay, so this is the important thing in the classroom. Then we also, we will make also installation which is very different. So that's a place where we put the things and then people are going to visit and touch things. So this is very different from the classroom. What do we explore? So we explore this capacity touch which was what you saw, like touching somebody and making music with it. We use mostly this Maki Maki which is now there. This one has a prototype and also has something that goes very well. It's very easy to use. Pressure and cognitive touch also using Raspberry Pi, Maki Maki or other devices. We also try to use, we will use objects, everyday objects that transform themselves into something that is making interactions and we are also exploring computer vision which is filming something and watching faces, skeletons, recognizing people, ITs, rotation. Then, because we are now in this meeting about graphics, let's talk a little bit about that and you already saw some graphics that we do in Anthropoleus but also this is a kind of graphic which you will see a video about how they did that. But this is something that is like an extension of a graphic because it's made in the physical world, it's not digital in that way, it's made in the physical world and also it's tangible. So when you touch it, things happen. You will see what happens. So what have we done? So we began in September 2017 and it was always in the classroom until now and we are going to present to you two cases, two little videos about it. So the first one is Sonic Granger Landscapes, Life Histories, and they will explain to you, the kids will explain to you what is it about, ok? So let's hear what they say. I'm going to use the songs. Look at how this works. My name is Adam. Do you see it? I'm going to use the little one. Have you seen it? Come on. Two for one. I'm going to introduce our families. We asked our parents or our mothers when we were little. We brought memories, images, objects, they took a photo and we cut it. Then the teachers did an interview and they took photos so we could include them in the collabs. Look, for example, you have to touch this one, but keep holding it. Look, touch this one. Give it your hand. Give it your hand. Give it your hand. And you? Touch this one. Touch this one. Or that one. And it's a Bolivia music from my country that my mother used to sing with her family and dance. The bachata was a music to dance, to sing. And my mother was like 10 or 15 years old. She used to listen to the bachata and remember her husband. It was the moment when she fell in love with my husband. And if you can't play, stop playing. It's a con to Mr. and that was the end of the presentation when they were presenting that to kids which were 5 years old. So you saw the interaction between them. This is another project which we are doing just now, these days, these last weeks. And it's a shorter video. I will explain a little bit about what it is. So now we want to create this kind of set-ups with paths that the kids can touch on the floor and when they touch it, it makes music. So sounds are music. Sometimes interaction is touching parts of the body or is touching objects or things like that. So we want to do like a physical instrument to make them remix music but also to make gymnastics or things like that. So you will see a little bit more. It's done again and I don't know if it was later, but we have here because you already saw them I think in the video. So Ruben and Nuriya who are the music and other things but you almost have so many things and communication and the educational parts. Okay, we are finishing the talk. Talking a little bit about the software and we'll talk about the hardware part. Anthropolutz originally was two models, the visuals and the audio engine and the other tone and users and they communicate each other using OSD protocol, the standard and we want to move away from that because we want to use free software and all this contrast. So we decide to rewrite everything using HTML5 to rewrote the visualization software I did the same part with the audio. So with the HTML5 we can distribute the software easily using internet or electronic or whatever and use the current hardware more or less and we try to include all the stuff they have. And we also decided to use web software to communicate each other so we imagine a network of several devices some of them with hardware connected to hardware and communicates using a wifi network the network will be created by the phone of the teacher because some schools doesn't have internet access and it was important to allow this configuration to work without internet so this helps and we add a little first component to the original setup is a remote control that is connected to that wireless network and allows to connect some hardware to that remote control and make the music sound and the visuals works. So we bring a little demo here it's the first time we show it outside our houses even in the school we just finished the first prototype so we want to share with you what we've done we are doing the goal is to make music together it's the goal of the demo so the idea is that you connect to that wifi it's open there's no password I'm using your browser from your mobile to open that URL and we will let you some minutes if you want to practice we'll talk about it with your mobile you can trigger the sounds and the idea is that the teacher will connect to the phone a Macimac or whatever so he can setup this inside the classroom very easy and well we are exploring way of interactive making music together it's not easy the one you triggered we are using this setup experimenting on how people can play together using the same instrument and we are not yet sure how it will work or how we will do it so this is more or less some technology so everyone can think around it so we are open collaboration and ideas and a kind of feedback we will bring that online very soon so we can use from internet I was wondering for the reason if you search like some with similar reason I mean like they don't have same timing and I don't know how we choose the samples so they have the same tempo so we just take that samples and launch them synchronize with the tempo we don't make any time changes most importantly we don't make any rich changes so the fragments are chosen because they combine together although they are from very distant places but they already match in the pitch we don't change that that's what I thought because if you take very random music there is a lot of work in choosing the fragments and looking for the information related to this we dream we build solutions to make music archives archives mixable so find ways to analyze the music to see if they match on tempo and key and automatically select them to provide a mix tool and the archives are available in the web there are a lot of them but I mean they are they are not available but we have for example we follow like 200 blocks from where we mainly download the music and there are people who are digitalizing old records that are out of the market more or less and we have this visualization where you can see all these elements and you can explore our sources but this is something we maybe we will do in the future what we are thinking now is to provide some presets for example this one will be online and it already has some fragments and in the future maybe you can add your own fragments to this tool the future also of this one about the phones is to make the teacher have a phone but then block their and some elements as this one and then when you touch that you are mixing so make them also accessible with physical interactions make it easy for the teacher to configure thank you very much


All right, what's up everybody? This is Alex from Xtrades. And welcome back to another educational video. Doing something different this week. We are coming out with a little crash course on how to find reversals in the market. I put up a vote or a survey from Google Forms and the Discord, and a lot of you voted for this reversal video. It won 50% of the vote compared to 25% and 25% for the other two options. And not only that, there was actually 30 people that voted on it, which is a lot more than I thought would vote. Thank you for finding the time to vote and thank you for taking a second out of your day because it does help my creativity block. I've been kind of having trouble finding more educational topics to cover because I've covered so many. I've done a lot of videos for the community. So it's a little bit hard to keep thinking of ideas for education and trading. When I've taught a lot of what I already know. So this is a topic I haven't really covered too much, I guess maybe we've talked about reversals and other videos, but this is a video specifically dedicated for reversals. And we'll do a couple of different parts. So we'll do part one today. We're going to be going into how to read candle structures to find reversals. So this is kind of like the basics. If you're new to reading candles and technical analysis in general, there should help you a lot. And we'll do this in different parts. So this is part one, we'll have a part two because there's so many different ways to read reversals and use reversals in a strategy. Like if you're using it off support and resistance. If you're just using candle structures to find reversals, that is the video we are covering today. And we're going to dedicate the whole 10, 15 minutes just to this. So I hope you enjoy and let's dive in. When it comes to the market, there's usually two types of patterns inside the market. There's usually continuation trades and there's also reversal trades. So continuation is a topic of its own and reversals are also a topic of their own. So usually with reversals, you're going to see some type of extreme selling or buying some type of trend. And the reversal point is usually the end of that. Now a lot of people kind of struggle with reversals because you are trying to either call a top or bottom basically. And the important thing is to wait for confirmation. And reading candles is one thing you are going to do to find confirmation. And just straight up reading candles and marking a couple price levels is basically just reading into price action. So we can see this is a upside reversal. We're going to go over upside first and then we'll cover downside later. And you're going to see one thing a lot of them have in common, basically all of them have in common. And these are recent market conditions. These are all very recent. So you can know you can find these in recent markets still. This is actually from yesterday. This was CPI day, by the way. So this is an event day. There was volatility. There was a lot of volume and you're not going to get that every single day because we don't have events every single day that bring in a lot of volume. So you got to keep that in mind as well. But here's a classic upside reversal. You got really strong sell pressure right at the open. We have a gap up faked out all the longs. They took it down, filled the complete gap. And usually once gaps get filled, you're going to see that potential reversal to the upside after the gap is closed all the way, which is probably this 437-40 or so. Now the important thing is to wait for some type of confirmation. And usually you're going to find that in a candle. So with reversal candles, you're usually going to find like a doji or a bullish hammer, something like that. Something with a lower shadow wick showing by pressure to the upside. It could even be an indecision candle as long as it has that lower wick. It's showing a little bit of by pressure. But the thing is you're not going to see that confirmed until it takes out the previous bar high. So here's your doji candle. Here is your next candle taking out the previous bar highs. Once it takes out that structure high, we have a really big pop, have a little bit of consolidation, and it runs higher. Once it takes out that high of day at the gap up, it was over with. It still continued. So this is a classic reversal. This is not a continuation of a trend. This is a big reversal off of selling. And what you'll see in all these examples when we go over, they all have the same thing in common. They're either taking out a structure high or low, depending if you're looking for upside or downside. So I hope that makes sense for the first example. Let's go into the next. All right, example number two, you can see that reversals and looking for the ideal structure is not perfect. You can see in this first example here, we have a previous low. We have the previous candle high as well. So here's your previous candle. Here's the attempt right here. We have a close over the previous bar high. It tries, it falls back within the structure. Normally, this would be okay to stay in, even if it falls back in, but keep your stop loss at the previous low or your previous bar low. So this is your structure low. And you can see it took out the low, so you would have been stopped out here. And this goes to show just because it breaks the previous bar high and you do get that confirmation of a potential reversal. There are other factors at play.  Maybe the nine and 21 EMAs were in the way, making a lower high to set up for a move down. So no strategy is perfect. It's just important to know your risk, have a plan. Your previous bar low or just your structure low in general is going to be your stop loss. If you were going to attempt a reversal right here, you would have gotten stopped out and you would have had to wait for something else to set up. Well, here's where it sets up. We would keep the same previous bar low right here, obviously, because it was an obvious flush level and also an obvious short-term bounce level right here. Now we're starting to get more clear doji candles. This was not the best reversal candle for your previous bar, but either way, it was kind of setting up for that break over the structure high. So you did need to consider it regardless of this ugly candle right here. These are a little bit more clear. They're obviously dojis, lower shadow wicks, potential by pressure. You got two in a row trying to push up to the upside, but you're not going to be confirmed until it reclaims your previous structure low. Once it reclaims that previous structure low, that is signaling a potential reversal. And then obviously, since it rejected here earlier, you probably want to mark this if you were day trading at this little resistance right here. It's probably like 440, 50 or something. Kind of hard to tell. We're not on trading view right now. This is just a screenshot, but I'm guessing you'd want to mark this high from where it rejected. And you can see there was one little candle that rejected that general area, but overall, once the structure low got reclaimed, that is some type of reversal. And it was able to overcome the short-term resistance and push all the way up into 230. And you can see here why this wasn't confirmed a reversal. Even though this is a huge buy candle, look at the previous bar. We were not able to take out the previous bar high, which was this opening candle right here, this big red one. This big bar was not able to engulf it and it did fall short of resistance right here. Even these candles did not break over it. It went over briefly, according to these wicks, but then once they closed back inside, it reversed back down. But it did start making a solid structure down here. So here's your previous bar. Once we see this big push right here, we know that this previous bar is our structure high and our structure low. We go ahead and mark that once we have that kind of engulfing structure or at least a break over it, a clear break. You can see it actually kind of rejected, went back in. But the important thing is, like I said earlier, it's holding the lows. So it holds the lows right here. So maybe you took it right when it broke. Maybe you waited for a little pullback. Either way, your stop loss is going to be at structure low. You could probably even adjust to this little candle right here. But the important thing is, we have that push over the previous structure high, this little candle that signaled something. The algorithms, other traders, they are trying to push this back higher. Even though it did back in, the structure's still holding and then we did have a larger reversal at hand over some time. Looks like it took about an hour. So it started at 10 and ended at 11. So I hope that makes sense. Really, reversals are just taking out structures, either to the upside or to the downside. Taking out previous structures like this, reclaiming structures, that's gonna signal a reversal as well. And that's how you read it. It's probably the most simple way to read it with candles. And like I said, there's many ways to use reversals. You can use supply and demand zones. There's two different types of supply and demand zones you could use. And we'll go into those in different parts. But these are probably the most effective and simple way for a beginner, or really for anybody to read a reversal just using candles and price action and a little bit of levels. Now, here is a reversal structure, but with a support line intact, a previous support line. So we have an obvious gap structure low here. Big gap up. I think this is from NVIDIA earnings from the whole market gap up. So we know for a fact this gap structure low is going to be a big level at some point. You could even see price consolidating off the general area right here. You're not gonna get an exact touch every single time like this. Don't expect, just because you draw the gap support low it's going to touch it exactly. Pay attention to the general area because if you pay attention to the general area you can catch something like this even though it didn't tap directly. That's why you wanna use your candle structures. Look at this. We have a little high right here, low right here. Look at this big push up bar right here. Took out the previous candle high on the one hour. Look at that huge reversal. I probably should have marked this one on my screenshot but I really like this one a lot to set as an example. Not just because it tapped the gap structure low exactly but because it also has a bullish engulfing bar. It is briefly a little bit under the low of the previous bar but very much over the high of the previous bar as you can see. So here's the high, here's the low. It's basically an engulfing bar and look what it led to. All that needed to do is push over the previous bar high close over it on the one hour and you did have a continued trend the next day. Little pullback continued trend the day after that. So this is the one hour. The other examples we were looking at were probably like 15 minute or five minute. You can find these on one day, one week. It doesn't matter. They all have the same thing in common. They're taking out previous structure highs or lows. The bar next to it or just the general structure around it but it's really good to mark your previous candles. If you get an obvious break like this go ahead and mark the previous candle see if it's breaking over that previous structure high or low if you're looking for upside or downside. And if you get that confirmation you may have a reversal on your hands. So hope that makes sense. That's all the examples for upside. We're gonna go ahead and get into downside next. All right not to downside. So the rules are basically similar. When you're looking for downside you're looking for it to take out your previous bar low. Here's your previous bar low. Here's your big engulfing bar. You also have a big line of resistance at 446-64. It's a big line of resistance. You get a short-term rejection here. If you wait attempted to take out the previous bar low on this bar right here and it just ended up shooting up so you would have gotten faked out right there but if you waited for another signal you would have a really big short makeup for it right here. So you're not always gonna get signals right away.  It just doesn't work like that. So you gotta be prepared. Have a plan just in case even though this took out the previous bar low you could see we did get that big impulse move up but ultimately that led to an even bigger move that would probably make up for the little loss. You probably would have kept stop loss at high day. If you went short here or a few ball puts you would have had stop loss at high day. It would have taken you out. Then you would have had another structure setting up later. So that's really basically it.  You wanna find some type of obvious candle that is taking out a structure. In this case we have a really obvious red bar. This is your focus bar structure. So you get the high and the low. Takes it out. Really nice flush. I mean this could have made you a lot of money on day trades even a nice two day swing. And then you just go ahead and mark your levels. Obviously this is a little back test area. So you could have taken profit at 442s. He had another structure low here at 436s held up there. Also a structure at 433s didn't quite make it there which is I'm pretty sure the gap structure low that we just covered in the upside example. And then look at here. We have another upside example. So you got the previous bar high, previous bar low. Look at this big candle. Took out the previous bar high. Even took out this little structure high right here. That is some type of bottom reversal signal and look how big that push up was. So they all have the same thing in common. They're either taking out a structure high or structure low and that's all you're looking for. Even right here, look we have a previous bar low, previous bar high, big red candle takes out the previous bar low right here. This one. And look at the downside following through after. Very big. So you can find these everywhere. You're gonna find them on multiple time frames. You're gonna find them really on any timeframe. It's all the same. The only thing that matters is that you're making a plan based on your timeframe. So if you have a higher timeframe trade, you might be holding in for a couple of weeks, maybe a couple of days overnight. If you're on a one hour to 15 minute, you might be day trading, taking quick profits. It just depends. You could even use one day bars, one day structures, mark your previous day high and low on the one day and that can be your day trade levels for the day. And you can still find big reversals for day trades on the one day. Even though you're looking at a higher timeframe, you can still day trade off those as well. So it just depends what you wanna do. But I recommend checking out multiple time frames and see what fits for you. I really like the one hour and 15 minute for day trading and stuff like that. I use the one day as well for one day levels. Marking your previous day high and low is really important. It's very simple and effective. So make sure you do that. All right, now to another example. This is gonna be Nasdaq one hour again. And we have multiple reversal signals, basically in the same chart here, all within the same eight, nine days here, which was pretty cool. Cause these do come a little bit more often than you'd think, even though obviously the market can stay in a range very often, it doesn't trend all the time. You can still find these pretty well, depending if you zoom in when it gets choppy to the shorter term time frames, you might need to do that. And if we have more volatility and ATRs are expanding, you can kind of zoom out to the higher time frames and find some pretty big swings honestly with these. But you can see all the same stuff. We have the previous candle low, previous candle high. We have a bar breaking under that previous candle low, sets up for a flush. Same thing right here. We have a big breakdown bar right here. Here's your previous bar low, previous bar high, sets up for a flush down again. Here's another one, big engulfing bar. Once you see one starting to try to take out that low, you can go ahead and mark your previous bar low, previous bar high. That's gonna set up your structure and potential trade idea. Same thing again, previous bar low, previous bar high. Once we start seeing this break, we start paying attention for a potential reversal. So it's the same thing over and over. Here's kind of a failed example. We have a previous bar low, previous bar high. You can see this big red bar try to engulf it, but it failed to close under the previous bar low. And once this gap closed, usually you're gonna see some type of bounce in the market. Even if it's just short term, a gap close is going to result in something. Sometimes we'll just butter through it to the downside, but lots of times you will see kind of long skates established once the gap is closed. I don't know why, but it's just kind of a psychological thing. And 80% of gaps do fail, by the way. Pretty sure that's a known statistic. But yeah, that's pretty much all of our downside examples. You can see they all have the same thing in common. They're taking down the previous bar low, previous bar low, previous bar low, previous bar low. And here's that attempt under a previous bar low right here. Try to fill a gap, made it long. You actually have a potential reversal signal right here. Here's your kind of your structure high that you would want to see taken out. And then once it tries getting over that right here, even though these two candles are ugly, we do kind of get a little reversal right here. Obviously not the cleanest one. Here's another example of a reversal to the upside, previous bar high, previous bar low. We have a brief close over right here. Nice run the next two hours right here. Probably good for a little scout. And onto our last example, this is the one day. And basically our conclusion, many reversals all have one thing in common, to take out the previous bar structure low or high. That is exactly what they're doing. Here's a major reversal on QQQs. One day, structure low, structure high. Big breakdown. If you marked this previous day high and low, literally every time the market closes, go ahead and mark your previous day high and low for the next session. Because once we saw QQQ gapping under this, we're probably looking for shorts to be honest because there's a lot of buy and bounce to fill down. Same thing right here. We have a previous bar low, previous bar high, bar gaps under it, great day trade, even a great multi-week swing here. I think these were when the market was correcting back in August to October for the big rally that came up. Volatility was a little bit more expanded. So it's not really realistic to expect volatility to be enhanced like this all the time, but it's still good to go over volatility periods because they do come occasionally, actually more often than people think. Here's a previous bar high, previous bar low. Look how it took out the high right here. The setup for a really nice higher timeframe reversal. Even at a big dip into it, kind of hold up the general area of your reversal bar or your previous structure bar right here. We have another previous bar high, previous bar low. Takes out the low, sets up for a big reversal down. Here's a previous bar low, previous bar high. We have a close over that just briefly. Kind of chops around a little bit, but overall still holds your previous bar low, never breaks under it, sets up for a big reversal over some days. Same thing right here, previous bar low, previous bar high. Takes out the low, kind of goes back within it, but overall did not clear your previous bar high. So as long as you get that break under, you can start keeping your stop loss, you know, at your structure high and just kind of be patient because sometimes it could chop out for a little bit before going down, as you can see right here. As you can even see for upside too, takes out the previous bar high. You have a confirmation right here, but it took a couple of days to kind of get going. And then here's your last, before our huge rally, which has been never ending into 2024 basically. Here's your previous bar high, previous bar low. This is actually an inside bar. So this was a bearish bar, inside bar formation. So if you get an inside bar like this, you're gonna wanna mark the high and low anyways of that inside bar. Once we broke out of the inside bar and closed over it, that did signal something was potentially coming. And we did get a really big push up to the upside right there. Big gap right here that hasn't been filled. Big gap right here that hasn't been filled. We'll have to see if those come back into fruition. Like I said, 80% of gaps do fill eventually. Pretty sure that's a known statistic. But I hope you guys enjoyed this video. Make sure you like, comment, and subscribe for our Xtrails YouTube channel. I'm gonna go ahead and get this chopped up, sent out all that good stuff. Make sure you keep a lookout for part two. We'll go into a little bit more depth. Today, we just covered candles, reading candle structures, keeping it simple, using your previous bar high and low. It's really easy, probably the most simple and effective way to read for a reversal. Like I said, make sure you're on your one day charts. You are marking your previous day highs and lows whenever the market closes. It's a really easy way to get day trade levels and to know when a potential reversal can come in, wait for that previous bar high or low to get taken out. Make sure you do have some type of selling or buying because not everything is gonna be a reversal. Like I said, this would be a continuation. So just because this took out the high this big bar right here, this is not a reversal. This is a continuation of a trend that was already there. This has strong selling, which leads to a reversal. This is already an established trend, which led to continuation. Even though it took out the previous bar high, this would not be a reversal. And like I said, there's two different ways to the market. There's reversals and continuation. Those are the two main patterns. And there's plenty of patterns we can cover, head and shoulders, double bottom, triple bottoms, et cetera. And we can get into those later in a different part. So I hope you guys enjoy. Make sure you like, comment and subscribe. Like I said, I love you guys and I'm out. There's a reason why Xtrades is currently the fastest growing application on the market for sharing financial ideas. With over $2.5 million paid in the last two years to contributors, users are flocking to see what trades the top traders on the leaderboard are sharing in real time. If you're looking to grow your reputation as a trader on the internet or discuss your trading ideas with other reputable investors, click the link below and get connected with the trading mentor today, completely free of charge.


The Mutual Broadcasting System in Cooperation with Family Theatres and Co-operated presents once on a golden afternoon, starring Tom Conway and Natalie Wood. Maureen O'Sullivan is your hostess.  One of the great joys we as parents have is to see our children growing up in the knowledge and love of God. Yes, and maybe growing up with them is the way to keep young always. For certainly their faith and trust in God is always an inspiration to our own faith. You know children have a wonderful way of knowing that God is always close to them and that he can and will hear their prayers. So often it happens that we lose much of the happiness of life because we forget the simplicity of childhood, the direct simple way children have, for love and laughter. Yes, and insight into the happiness of children, how we can add to their enjoyment and light-heartedness is a way to recapture the joy that as adults we often lose. Love of God and daily family prayer in our homes gives light-hearted happiness and peace and harmony because praying together as a family brings God close to all of us. Tonight is a special program Family Theatre presents a story for children, for all children from six to sixty-five, a story that happened once on a golden afternoon, starring Tom Conway and Natalie Wood. Moreno Sullivan will return after tonight's Family Theatre story once on a golden afternoon, starring Natalie Wood and Tom Conway. In the lounge of the press club in Washington, D.C., the annual banquet of the press club has drawn foreign correspondence from the four corners of the globe, editors from the nation's newspapers, and of course, reporters of every description. The president of the United States is the guest of honor. People keep milling in and out, but in a far corner of the vast lounge sit two men, oblivious to the noise and excitement. Edward Kent, roving foreign correspondent for International Syndicate, and Jim Thorn, Washington correspondent for The Times-Santanal News. Oh, of course. Oh, good. Oh, Kent, this is really old home week for me. You know, I haven't seen you since, so let me see, before the war. A few years before that, 1937 to be exact. Yes, that's right. The London Economic Conference. We covered it together. You covered it, Jim. I didn't. I got fired. Say, what happened then? Somebody told me that you got fed up with the way things were happening in the world and wanted to get away from it all. No, I ran into something better than the Economic Conference. At least I thought it was. What was that? The story on Alice Liddell. Liddell? Was that the Whitechapel prisoner? No. No, this was an 80-year-old, rosy-cheeked little lady who lived in the flat below me. I got fired when I missed the most important meeting of the conference because I waited to hear the story she told me about a golden afternoon. Yeah? It's a story known to everyone, but it actually happened to her, and the remembrance gave her the wonderment and simplicity of a child. You see, as a little girl, she lived near Christ College in Oxford. This was in 1864, and there was a young professor taught mathematics at the college, and, well, one day he'd promised to take the two Liddell girls, Edith and Alice, on a picnic, and they were waiting for him near the river. Hello there. How is everyone on this glorious afternoon? Well, aren't we on speaking terms? Edith is angry. Angry? At whom? At you, Mr. Dodgson. Oh, I see.  Well, if I have to tell you that we're angry, then I can't be angry if I speak to you, can I? No. No, you can't. Because when you speak to a person at whom you're angry, then you're no longer angry. She is too. I am not. I say, what is this all about? Well, didn't you forget something? No, now let me see. You promised to take us on a picnic. Oh, good heavens, I did forget. Now you wait here. I'll dash up to my room and get the picnic basket. We'll have it filled up, and we'll be rowing down the river in no time. I know just the spot for a bit. That's the story of Fair Rosamond. And over there, near the old monastery, is her burial place. Oh, that's a beautiful story. Tell us another before we land, Mr. Dodgson. Why, I've almost run out of stories. Oh, that bridge yonder has a little story. It's been here ever since the time of the Romans. And that is how Oxford got its present name. It was a fort for Oxen to pass over. And so long before the Christian era, it was called Oxenfort. Oh. Well, here we are. Isn't this a perfect place for a picnic? Oh, I love it here. I'll take the picnic basket.  Will you shaper on the landing of the troops? Ready? Prima, Secunda, Tertia, forward. What's this mutiny? I say forward and none of you move. But you said Prima, Secunda, and Tertia. And they aren't here. Edith is Prima. That's the first contingent. And you, Alice, are Secunda. That is the second. And I am Tertia. Which is the third? Right. And now let's be off to that shady tree out of the sun. So, an apple for each of you, and we've cleaned the picnic basket. Here you are, Edith. And here's one for Alice. Catch it. Hurry, it's rolling down to the river. It'll take a longer hand than yours to reach it. I'm afraid we've lost it. You see, it's a rabbit hole, and it goes down deep. What does a rabbit do down there? Does he live down there all the time? Of course not. He has to get air. He comes out and eats shrubs. Oh, look! There he is over in the bushes. He's a white rabbit. Catch him, Alice. Catch him. Oh, you can't now. He's gone down the hole again. Oh, he was such a pretty rabbit. Why did he want to go down that old dirty hole? Oh, but it isn't an old dirty hole. It's a... It's rather a wonderful place down there. You see, up here the world is sometimes filled with things that are hard and cruel and people who are sometimes thoughtless and unkind and selfish.  Yes. But down there is a wonderland with mock turtles and lorries and griffins. Oh, tell us about it. We'd like to go down there. Well, um... Well, you see, there's quite a story about this wonderland. Story? Please tell it to us. Is it about the white rabbit? And mock turtles? Yes.  And suddenly, she found herself dropping down, down, down. And while she was falling, she was clutching at things on the way, saying... To fall is this. I'll take nothing of tumbling downstairs. I wonder how many miles I've fallen. I must be somewhere near the center of the earth. I'm sure. Won't she be safe? If I've kept you waiting. If you please, sir. Master Rabbit. Oh, my fur and whiskies. Where are my gloves and fan? I'll have to be on the way. Remember, my little poem. Now, let's see. Approve his shining tail and pour the water softenile on every golden scale. How cheerfully he seems to grin. How neatly spread his claws and welcome little fishes in with gentle smiling jaws. I'm sure those are not the right words. I must be somebody else after all. And I shall have to live in this pokey little hole. No, Mr. Mouse. Where's the cat? I beg your pardon. I quite forgot you didn't like cats. We won't talk about that any longer. As if I would talk on such a subject. Our family always hated cats. Nasty, low, vulgar things. Don't... Mouse, dear, do come back. And we won't talk about cats anymore. You promised to tell me your history.  It certainly is a long tale. But why do you call it sad? Silly girl, what are you talking about? Catapella is. But what is he doing over there? Smoking his pipe. That's a funny thing. And he's sitting on top of a mushroom. And why not? Oh, I'm sure I don't know. But he has large, lonely eyes. I know he must be very unhappy. Who can tell? I'll go and talk to him. Catapillar? Who? Sir. XP?  I don't see. I'm afraid it's very confusing. It isn't. Maybe not to you. But I'll go away if you don't want to be friendly. Come back. I have something important to say. What, sir? Keep your temper. What? Keep your temper. Is that all you have to say? No, but that's most important. Oh. So you think you've changed, do you? I'm afraid I have, sir. I keep growing and shrinking. And I'm not the same size for 10 minutes. And I can't remember things. Can't remember what things? I tried to say how doth the busy be. But it came out different. Oh. Then recite. You are old Father Williams. All right. I'll try. You are old Father William, the young man said, and your hair has become very white.  Do you think at your age it is right? In my youth, Father William replied to his son, I feared it might injure the brain. But now that I'm perfectly sure I have none, why I do it again and again? I mentioned before and have grown most uncommonly fat. Yet you turned a back somersault in at the door. Pray, what is the reason for that? In my youth, said the sage, as he shook his gray locks, I kept all my limbs very supple. By the use of this ointment, when shilling a box, allow me to sell you a couple.  Yet you finished the goose with the bones and the beak. Pray, how do you manage to do it? In my youth, said his father, I took to the law and argued each case with my wife. And the muscular strength which it gave to my jaw has lost it the rest of my life. But hardly suppose that your eyes were as steady as ever. Yet you balanced an ear on the end of your nose. What made you so awfully clever? I have answered three questions and that is enough. Said his father, don't give yourself hairs. You think I could listen all day to such stuff? Be up or I'll kick you downstairs. Kick him downstairs. I am ashamed of you. It is not said right. Not quite right, I'm afraid, sir. It's wrong from beginning to end. Well, that's because I've become so small. You're quite big enough. Oh, but three inches is a wretched height to be. It's a very good height indeed. Oh, three inches. But I'm not used to it. But you will be in time.  One side of what? Of the mushroom, of course. You mean eat it? Of course. Oh, here he comes. Here he comes. I must be away. That's it. Oh, my dear paws.  Oh, Mr. Rabbit. Oh dear, oh dear, oh dear. Right, Mr. Rabbit, where are you going? The Cheshire Cat. Then which way are you going? I've seen Harris before, so I'll go to see... Oh, what are you doing? Vanishing. But you're beginning to vanish at the end of your day. I've often seen a cat without a grin. But a grin without a cat. It's the most curious thing I ever saw in my life. He's mad. I was going to sit down at the table with you and the doormouse and the hatter. I'm mad. I don't see any milk. Then it wasn't very civil of you to offer it. Wasn't very civil of you to sit down without being invited? Your hair wants cutting. Personal remarks are very rude. Then why is there even like a writing disc? Oh, now we shall have some fun. I love riddles. You mean you can find out the answer? Exactly so. And say what you mean. I do. At least, I mean what I say. That's the same thing, you know. You might as well say I get what I like is the same thing as I like what I get. Or I breathe when I sleep is the same thing as I sleep when I breathe. Have you guessed the riddle yet? No. I give up. What's the answer? I have the slightest idea. Nor I. You're just wasting time. What time is it? It's six o'clock. It's time to eat. I'm getting hungry. Have you seen the mock turtle yet? I don't even know what a mock turtle is. It's the thing mock turtle soup is made from. Are you hungry? I don't think. Then don't talk. It's time to go. I'm sure the mock turtle should be somewhere on the seashore. There you are. Sit down and don't speak a word. But you are going to tell your story. Not a word. Sir, I don't see how you can finish if you don't even begin. Once? Once I was a real turtle. Thank you, sir. That was a very interesting story. But I'm not finished. No? No. When we were little, though you may believe it, we went to school in the sea. The master was an old turtle. We called him tortoise. Why did you call him tortoise if he wasn't one? You know, you really are very dull. We called him tortoise because he tortoise. Oh, but how many hours a day did you do your lessons? Ten the first day, nine the next and so on. That was a curious plan. Well, that's why they're called lessons. Because they lesson from day to day. Oh, look. What is that? Lobster quadril. You're going to dance? Why, of course. Form two lines. Advance twice. Change lobsters. Get that jellyfish out of the way. Now out to sea and don't be slow. The somersault. And there you... He comes again. The duchess. She'll have me executed. Oh, Mr. Rabbit. Oh, dear, dear, what do you want? I'd like to see the duchess. She's in a stew. Wait, Mr. Rabbit, I'll go with duchess. I didn't know you looked so big and funny. Well, you don't know much, and that's a fact. Everybody minded their own business. The world would go around the deal faster than it does. Which would not be an advantage. Why? Well, just think what it would do to the day and night. You see, the earth takes 24 hours to turn on its axis. Speaking of axis, it's time to chop off her head. Oh, dear, oh, dear. Your hot tempered duchess. Maybe it's the pepper that makes people hot tempered. I can't tell just now what the moral of that is, but I'll remember it in a bit. Perhaps it hasn't one. Tut, tut, child, everything's got a moral. If only you couldn't find it. Everything's got a moral. There it is. Oh, tis love, tis love that makes the world go round. Somebody said that it's done by everybody minding their own business. The moral of that is birds of a feather flock together. How fun you are finding morals and things. Oh, yes, the moral of that is be what you would seem to be or more simply said. Never imagine yourself to be otherwise than what it might appear to others that you are or appear to be. But that isn't more simple. Chop off her head. Oh, dear, oh, dear. Wake up, Alice. I say, look at Alice. She's crying. Alice, wake up. What's the matter? What happened is so unfriendly. Oh, we'll have to give him a good talking to the next time. Oh, but you didn't finish the story. I couldn't very well. In the middle of it, Edith went off to pick daisies and you went fast asleep. Then I must have dreamed about the mouse and the duchess and the turtle and the rabbit. I started telling you a story about them. Oh, I remember. It was a wonderful story. A story just for you, Alice. And for Edith. Will you write it down so I can remember it always? Write it down. Yes. And I'll call it a golden afternoon. No, call it Alice in Wonderland. Then it'll be just for me. Wouldn't you want it for all your friends, too? Oh, yes. For everybody. For all of us who are children always. A story to remember the simple joys of childhood and the happy summer days. Well, that was the story Alice Pleasance Liddell told me. That's why I missed the meeting of the London Economic Conference and got fired. The original Alice in Wonderland? That's right. Later Dodson asked George McDonald to draw pictures of Liddell's book. McDonald showed the manuscript to Macmillan, the publisher, who decided the book should be published for the millions of Alice's throughout the world. But I thought Lewis Carroll wrote Alice in Wonderland. Oh, that happened because Dodson was a professor of mathematics at Oxford. Oh. He thought everyone would laugh if they knew he'd written that book. So he used his first and middle names twisted around. And what happened to little old rosy cheek, lady? Well, she died a short time later. I was fortunate enough to have seen the original book that he'd written for her, though. And inscribed on the cover was Lewis Carroll's last dedication to the little girl who has been my inspiration. Alice Pleasance Liddell by Alice in Wonderland. You know, sometimes it's good to be able to daydream into a child's world of wonderment and life's most beautiful lessons are learned. Most of us can recall at least one gold an afternoon. An afternoon away from the world of reality that's often so thoughtless. If the world today needs anything, it's first a renewal of faith, a renewal of trust in God and in his eternal providence. If only all of us could get back to those simple truths, if only all homes would get back to the daily practice of family prayer, this indeed would be a better and a happier world. A world where there would be true brotherhood of all men and the lasting fatherhood of God. Let us tonight make this simple dedication of our families to God. Let us dedicate a short period every day to the practice of family prayer in our homes. For there is a joy and a happiness in daily family prayer and there is this lasting assurance that the family that prays together stays together. Before saying goodnight, I'd like to thank Tom Conway and Natalie Wood for their performances this evening. Our thanks to John Slott and Emil Frank for writing tonight's play and to Max Tur for his music. This production of Family Theatre and Corporate was directed by David Young. Others who appeared in tonight's play were Virginia Gregg and Whitfield, Dick Ryan, Fred Shields, Hard McNeer, Earl Keane and Psy Kendall. Next week our Family Theatre stars will be Joan Loring and Louise Beavers in Fear is a Little Word. Your host will be Bob Crosby. This is Maureen O'Sullivan saying goodnight and God bless you. This series of the Family Theatre broadcast is made possible by the thousands of you who felt a need for this kind of program and by the mutual broadcasting system which has responded to this need. Be with us next week at this same time when our Family Theatre stars will be Joan Loring and Louise Beavers with host Tony LaFranco speaking.


Welcome! In this video, I want to go over how to use the Navigation Alert Trading Service so that when you receive a trade alert, you can quickly and easily execute that trade. So if you look on the screen, I'm showing my actual cell phone. And I just entered a trade and sent out an alert. And as you can see at the top, this is an opening trade. And if it was an adjusting trade or a closing trade, it would say so. But in this case, it's an opening trade. And I sold two contracts of an iron condor in TLT. And you can see it's the November 18, 2016 expiration cycle. And then just below that are the strike prices. You've got the 137, 140, 128, 125. And I got filled at an 82-cent credit. So I got filled at 82 cents. Let's go to the platform and execute the trade. So here we are on the platform and we're on the trade tab. So we put in the symbol TLT. And then we want to go to the November 18, 2016 expiration cycle. So you want to open up that option chain. And the first strike that we're looking for on the text alert was 137. 137 call. So we want to right-click there, sell iron condor. Just like I've always taught in the class. And remember, the strikes that we're looking at to trade are the 137. And so on an iron condor, you can really just go down the line in the same order that they came in on the text message. And it makes it really efficient. So 137 and then 140 is the call that we're buying. And then the 128 is the put we're selling. And the 125 is the put that we're buying. So we enter that there. And there you go. So as you can see, and this is a good example, because now you can see it's trading at 81 cents. Okay, I got filled at 82 cents. Sometimes you're going to get filled at better prices. Sometimes you may not get filled as good of a price. But it doesn't really matter. First of all, you want to make sure that the trade fits into your overall portfolio. You don't have to take every trade that I take. But this is a good example to show you of what you can do. And then, as I mentioned, I put on two contracts. And so if we right-click and analyze the trade, it brings it up onto our analyze tab. Make sure you set your slices to break even. Just to get your slices where you want. And just to make sure that the trade is in order and is exactly how you want to execute it. So this looks good. This is exactly what I'm looking for. So I can go ahead and right-click, confirm and send. And I'm not getting filled right away. So just as we teach in the course, go back to your trade tab. Right-click, cancel, replace. Move it down a penny, confirm and send. And see if we get filled there. We may have to give up another penny or two. That's just part of trading. So cancel, replace. Move it down to 79, confirm and send. And we got filled at 79 cents. So then you go back to your analyze tab and you can see right here our max profit on this is $158, max loss $442. Again, this is just a sample trade that I put in one of my smaller accounts. You need to trade the number of contracts that fits your account size and fits your portfolio. I hope this was helpful and we'll see you next time.