Good morning, good afternoon, and good evening, depending where you are in the world. I am Francesco from Italy, and I am a product manager for Spotify, working as part of the platform developer experience tribe called PDX, whose mission is to speed up Spotify by providing teams with a simple, consistent, and delightful experience. In this event, in this conversation, we will talk more about developer experience and how to define and classify the developer experience, the main challenges, and risks connected also to the business. We will discuss about targeting the developers and the techies. We will see the difference between the two concepts. And we will also touch the topic and the role of the role played by open source in all of this. As part of my daily work, I am product manager for a specific tooling that is called Backstage, that is used by thousands of Spotify developers to create the app that you all know, and not only that. And it is also used by most probably hundreds of thousands of developers as part of small, medium, large organizations across all the industries, continents, and their technologies. In one of my previous positions at Alfresco, I have been also the product manager for the so-called Alfresco application development platform used by developers to create applications on top of the services through an open source framework using Angular. That is one of the most up-to-date technologies to create end-user applications. And I have always been an open source enthusiast, being a former software engineer and a consultant, a developer advocate, and an author of books for developers and video courses teaching about development. And if you think that I have done a lot of things, it tells you a lot about my age honestly. This is to say that developers are important to me. I continue to proudly define myself as a developer because I truly believe that development is a great art and a very creative job, when done properly, of course. But developers are not important only to me. They are very much important for a lot of the existing companies because they are helping the business. And this is pretty obvious. In this conversation, we will treat this concept that developers are important for the business as an assumptions, as a believer, because it will deserve a dedicated conversation that is slightly out of topic for this content.  Instead, I would like to keep the conversation on the developer experience topic. It's very much closer on what I like and where I'm working with, of course. Because developer are important, the business wants the developer to be faster, more effective, and innovator. All of this to be with one purpose in mind, to be ahead of the competition. This is not a new statement. This has been valid for some decades, probably since when the job of coders exists when the developers starts to become professional and IT professionals. But developers and development are pretty broad and generic terms that evolved in the past years. And in today's day, they look slightly different from what it was in the early 2000 or simply 10 years ago. Developers are different in these days. And development is very much different. First of all, we have very different types of developers. We have front-end developers, back-end developers, full-stuck developers, meaning about developers concentrated on the end-user experience, on the back-end of the service creation and development, or both of the two. We have mobile developers. That is, again, a slightly different expertise and development expertise. We have quality assurance testers to test the quality of what is given in the hands of the users. We have data scientists. They are not purely developers, but they are hacking code and they are developing algorithm and portion of codes exactly in the same way that the pure developers are doing. This is very much an interesting conversation, because we cannot classify data scientists as pure developers, and I hope no one will be offended by this. And this is the reason why I often discuss that, I mean, talking about the developer experience, we prefer to discuss that we target the techies. There is a broader term for the developer. One disclaimer is that from here ahead, I will continue to use the word developer, but in reality, I'm talking about techies, and I apologize if someone recognize herself or himself in this definition. Develop is not necessarily a type of developer, so a specific type of IT professional. It's more a methodology, but in some cases, this is used also to indicate what is in the past where this is of mean, and again, it's good also to highlight this. Also security experts is very much important. In terms of type of development, of course there is a match with the front end development for NGUIs, backend for services and APIs, and of course the methodology of the DevOps. But let me also highlight that something that I find very interesting in the market is that when we target developers, often we target the developer internal to an organization as part of the core business, but it's very much important also the external developer, third party developers. Developers, they are our customers developers, our partner developers, someone that is acting outside of the core business of the company, but he's working with our services, our technology, our tooling. All of them, all the developers are dealing in some extent with several different, many different tools. Again, if you are not an expert, the probabilities are complex names, in some cases known, in some other cases not known, but the main concept here is that tooling is very much important and every developer needs to deal with many, many, many different tools. The emerging architectures are simply making this challenge bigger, because if you think about the microservice world, something that is about the world, so in the modern architecture, instead of having one single monolith, one single application, one service is split in many, sometimes those and sometimes hundreds of microservice and every service needs to be developed and probably maintained. Platformization is also the push of the market looking at every service as a sort of platform, so exposing API, exposing services. This is also something that is making all of this even more complex. Let me summarize this. I think it's pretty tangible that developing in today's world is more powerful than ever, but very, very complex. So if you are experienced enough in development, you know that developing years ago was amazing, like it is today, but it was less deep in content, in tooling. Today is extremely powerful. You can do a lot of amazing things, but it's also very, very complex and the complexity is exactly something that I would like to focus the conversation at this point. And if you are an experienced developer, okay, this is hard, this is challenging, but I mean, you can count on your experience and your knowledge, but if you are a junior developer, this in some cases can be really, really, really complex. Complexity apart another historical behavior related to the developers. And the development is about the obvious confidence that the developer has with coding and every and very technical tooling. By nature, our developer is intrigued by tools like the so-called terminal. This is the picture showing exactly what a terminal looks like. And if you want to make a developer really excited, provided him or her with the so-called CLI, this is an example of CLI, where you can raise complex or simple comments exactly in a similar way closer to the source code. Developers are happy to be considered very close and to work and act very close to the code because this is exactly where they feel at home. This is exactly where they feel they succeed in their mission. This is about controlling the machine. Okay, I'm going a little bit psychological and philosophical. I won't go more than this, but the concept in that is that developers are comfortable in working as extension of the code and they feel comfortable in going deeper in the technical parts. Of course, this is not so, let me say human. And so it is something that is attractive for them but needs to be properly. It introduced some complexity, of course. If you mix this complexity with a relevant number of tooling and methodology that we discussed before and you can see here summarized in one picture. By the way, this picture is showing the different numbers of technologies that are used only under the radar of the CNCF foundation. So this is a subset of the existing tooling supporting the developer experience. And so if you, I mean, something that of course it's easy to see here is that if you mix the need of a developer to work in detail and deeper in the tooling and if you see the higher, incredibly high number of tooling, you can imagine the level of the challenge and also another challenge that is part of the developer experience in today's world that is about the fragmentation, of course. That is something that is really affecting the experience of the developers in today's day. Now that we have seen that we started from the problem and we have seen two of the bigger challenges from a developer perspective. We will elaborate a little bit more later on. Let's discuss a little bit about an initial definition of the developer experience. At this point, it should be clear that the developer experience is the collection of tasks, feelings, behavior, reactions and actions in general, done by developers in techies to do their work and reach their goals. Just to be clear, this is not an official definition of developer experience because an official definition of developer experience doesn't exist yet. I'm quoting here, I'm submitting to your attention here a couple of different definitions. As you can see, they're not extremely different. Microsoft One is more closer to the tooling, but not only about tooling. The other definition is closer to the experience. So it's something that is literally going beyond the tooling. But I mean, the important thing to recognize here is that there isn't a unique definition. It is about, there are, I mean, different points of view that we can discuss about the developer experience. And in some examples, the developer experience definition is more on the, again, experience and other cases is more on the tooling. This is what you will see as part of the different articles, literate books and solution as well. Just to share an example of this, probably a little bit on the edge, let me share what I have discussed with one contact in my network that is heading the developer experience for a company, pretty structured with more than 800 of developers. And he's saying that developer experience is also about the chair and the desk that a developer is using. It's about the environment, the culture where the developer act and work. I tend to agree, I think it's right. Developer experience is not about tooling only, it's about also, I mean, how to engage the developer to reduce the frustration of something that is not happening the way that it is expected, how to foster the innovation. But of course, we need to keep the fit on the ground, of course, and being practical. But again, it's a good point, developer experience is a broad concept and a unique and agreed definition doesn't exist yet. Like for example, it exists for the user experience. Before I'm going ahead with the conversation, let me discuss about some obvious statements and questions that can easily come into your mind. Probably you're already questioning about yourself. But okay, but despite the fact that maybe we don't have, or you don't have as part of your organization, a developer experience in clear, are we already doing developer experience? So the fact that we have developers means that we are doing something with and for the developers. Are we doing the right thing for them? Is it now more of a buzzword or of a need in the market because of the complexity? So why this is now is more important. All of those are good questions. Yes, developer experience is not a new concept and we have always done the developer experience approach and help the developers in doing better their job. Since the very first computer where working in a room, for example, in something like that, the conversation about to improve the developer experience was a thing. But in today's world, there is something that is more important probably because the challenges of the developer experience is challenging also the business, is affecting the business. And so this is why developer experience is assuming relevant importance in these days. Just to give you an idea how important is for the business, the developer experience, let me share some examples that I'm hearing from several companies, including Spotify, but not only Spotify. Because, so first of all, let me share an example. This is a Spotify example, for example. In 2015, Spotify was becoming a company with thousands of developers, starting from hundreds of developers and because of the relevant number of hires and because of the microservice ecosystem that it was pretty complex at that time and in general, the number of onboarding days that we were measuring through the metric that is telling about how many days was needed to raise the first 10 PRs. The number literally explodes to 60 days. And this honestly was challenging the business because it was slowing down the business a lot. Talking with many companies, they are going from a monolith architecture to a microservice architecture with many services. One of the most recurring question is who is owning some kind of service? If we have an incident, like for example, long for Jay, if we have a problem or a vulnerability is discovered as part of one's service, who is owning that? If we have to decide where to change all the lock for Jay versions as part of the core business of my company, where I can find this kind of information, something that is challenging every developer is about writing documentation, how we can improve the developer experience in writing technical documentation because this is affecting the business because we don't have documented software. We have a not well-maintained software. We have a low-quality software. And this is affecting the business, of course. This is another topic because if you have to create a new service from scratch or something from scratch, you cannot wait for weeks. It is most of the time in today's day. All of this is getting bigger and bigger and bigger at scale. So if you have to onboard hundreds of developers per year or if you have to manage those as of thousands of services and you need to understand the ownership, this is absolutely affecting the business more than, of course, the lower numbers. Something that is challenging also the company in facing the developer experience is also something vital for the final goal of the business, innovation. And innovation is closer also to the digital transformation and things like that. We don't need to explain the importance of innovation from a competitive advantage. I'm talking about the business. And in development and technology, innovation comes also from the autonomy of the developers to experiment, try, learn, and maybe learn because they failed. And, of course, improve in the next iteration. Developers wants to try new things, be free to try new things. And this is in clear contradictions on constraints and maybe long process that some kind of companies are forced to take. If you think about areas like public sector, pharmaceutical, banks, insurance, the innovation is vital, but it's equally important also having an understanding of the policies, of the rules, of the compliance, and things like that. So, autonomy is very much a need from a business perspective, but at the same time is also a challenge because autonomy is frequently connected also to the concept of chaos, of course. Let's summarize a little bit where what we discuss until now that it's a pretty big chunk of space dedicated to the challenges. And the challenge of the developer experience, first of all, we define the developer experience, but we discuss also the challenge of the complexity. So tools are very powerful, but complex in these days. They are also very fragmented because we have many of them. And there is also the need of the autonomy from a business perspective. All of this making bigger as a challenge at scale. Let's move a little bit ahead discussing about the solution and most in particular, what I would like to discuss with you is what possible solution look like, what is happening in the market and what we are seeing and I am seeing as part of the evolution of the market exactly in this space. First of all, the immediate reaction where almost everyone seems to agree about the complexity. So the fact that developers like to go deep, at the heart of the technical solution, something that we want absolutely to preserve and to provide to the developers. But at the same time, something that we want to provide in the hands of the developer as an option is also something more closer to a human experience. So in this example, you can see on the left, the terminal in the way that developers love. And on the right stuff, on the right side, you see a portal, in this case, a backstage, one of the product where I'm working with, where you can do reach exactly the same goal, but instead of having a CLI, having an interface. Having an interface with fields and buttons that are more suitable for humans. So the principle behind this, of course, is not to replace the CLI with an interface, because developers love the interface, but to provide an alternative. So instead of forcing them to act with the CLI only, also providing alternatives to make simpler and more closer to the human experience, something that is closer to the source code and to the developer experience. Fragmentation is allowed concern as we discussed in the past and in the past slides and companies, but it would be better to say developers are challenged by the need to jump from one tool to another because the tools are not talking one each other. As an example, you need to go to the terminal to manage all the Git stuff. Then you need to go to Terraforma because you want to see the pipeline. Then you need to go to AWS because you have to see the deployment and the cloud environment. Then you need to go to the test, to Confluence to see the technical documentation. So in this four tasks, you have touched four different tooling and all of them with different user experience instead of going in one single pane of glass in one single place where you can find all the information that you may want. Companies would like to, instead of providing exactly to go beyond the fragmentation experience, companies would like to provide a unified experience often connected to the concept of sole services provisioning of resources and solution rather than being forced to go here and there in the organization to receive what they need. The sole services need is very much connected to the following topic. And in this space, rules and constraints are definitely enemies, but at the same time not having the control of what teams are doing is a relevant concern, especially in high-regulated industries like banks, insurance, pharmaceutical, et cetera. This is why providing developers with service tooling where they can have a small medium or big level of autonomy in deciding what to do and how to do it, it seems to be allowed repressed for many companies and good offering in the market. As part of this, there is a concept of guiding the development instead of ruling them. Related to the challenge of the autonomy, there is also the implication of the standardization. So every company needs wants also to provide guidance to developers to do things properly accordingly with the policies of the company, with the best practices of the companies, instead of constraining them to say, yes, you're allowed to do this or not, you're not allowed to do that. Again, in terms of solution, the push and the trend of the market is again, is to react with the ease of use to the complexity, but guaranteeing the flexibility because we want to leave the autonomy to the developers to do the things in the way they want, also going deep to a terminal level to do the stuff. The providing unification views or single pane of glass to do the various things instead of forcing them to the fragmentation and to guarantee the autonomy to provide a guidance instead of a blockers or long processes to again, to unblock the creativity and innovation as part of the businesses of the company. So now that we discuss a little bit about where the possible solution are and what the product are, what the products are introducing as part of the developer experience, what the companies are doing. So first of all, a common reaction of many companies that I'm talking to, first of all, they are seriously thinking to build dedicated teams dedicated to the developer experience. Developer experience teams are often small between two and five-ish in some cases they are bigger than this if they want to cover and they need to cover also some operational tasks like for example, maintaining a pipeline and things like that. Often they are originated by the software architect teams or DevOps teams. And they often start from operational problems. For example, I want to provide the best pipeline and agreed pipeline to a complex organization. But soon they land to a broader developer experience because developer experience is broader than that in exactly the way that we discuss in the initial part of this composition. After the developer experience team is created, one of the initial challenges is about the tooling. Honestly, real tooling to address all of this concern or at least unique tooling are not defined. And one of the bigger concern that I'm hearing from the companies exactly in adopting this tooling is that they want to avoid a trap because honestly, one interesting thought is that we are talking about complexity. We are talking about fragmentation and then what we are discussing as part of an improved developer experience to add the yet another tool or some tooling. And so it seems that the risk here is also that we are increasing the fragmentation adding more tooling, adding more complexity. And this is exactly what we want to avoid. So what the market is telling us. So what's the market segmentation about the developer experience and the tooling related to developer experience because what I'm focusing now, it's more about the tooling because of course, there's not a magic bullet or something that we can discuss about culture and things like that. But again, in terms of tooling, a defined market segment doesn't really exist yet, even if things are evolving pretty fast. And some analysts are starting to see some loud request in terms of developer experience because simply it is affecting the business in the way that we were discussing. If you didn't have the chance to look at this Gardner research, I would highly recommend to go through it. This is really interesting. It is focused about the internal developer portals. We will see in a couple of slides what the internal developer portals are. But it's a pretty interesting example of attention that what analysts are recording from the market. And it is a very pretty good insights about the tooling existing outside and in the market to address the developer experience in this case for internal purpose. In terms of offering, what we see is that there is a clear market segment that is emerging, it's about the internal developer platform, the so-called IDP that of course are targeting the developer personas of an organization. So they are more for internal purpose built to build, of course, as a simplification of the usage of few or some services. So they are often defined by a portal plus a service with one goal in mind, obstructing the complexity of the usage of the services. Most of the times this type of offering in the market, they exist some, honestly, the majority are there. I don't want to quote them because I don't want to tell you, but you will easily find them if you search for internal developer platform. Most of the time they are addressing the develop experience because develop as methodology is pretty complex and it is a key pain point to be abstracted and simplified. But as part of the current offering, there are also developer portals. So portals, they are horizontal to the various services. They are literally single pane of glass that again are obstructing and making simpler. What today is pretty complex and they leave on top of the services. Honestly, backstage is an example of this, of developer portal. And we have many other example of developer product. Many different example of developer platform. This is to give you an idea of what is existing outside. Conscious of time, let me also discuss with you the role of open source. I mean, this is one of my, one of the slides that I enjoy most and this is something that I also discuss in several conversation about the value of open source. I won't go in detail of every item here because it's too complex, but let me say this. The role of open source in the developer experience is the same as other and the other market. So it is an alternative. It is a potential solution to make the developer excited and help them in doing better their job. Of course I am an open source enthusiast, so it's clear also what I support and enjoy most. But again, in terms of business opportunity, the open source offering is the same as in other area. So the open source offering is central, but it is complementary to the known open source offering because it's clear that in some case, and it's absolutely fine, that in some cases some companies may prefer to have some identified and reliable supplier and vendors and they want to trust in some vendors and they prefer to rely on them instead of rely on a not well undefined ecosystem of a community at this point in time. But again, it is clear that open source has a role in the market and also in terms of developer experience is exactly the same. It is central and it provides value equally to other segment and offering of the market itself. Okay, I'm a little bit out of time, so I would like to ramp up and summarize what we discuss. First of all, we define the developer experience and we discuss also why developer experience is important. We discuss also about some overall solution and what it is in the market and a little bit of touch of the role of the source. Finally, let me share some thoughts about the direction of travel, at least from us at Spotify and myself, for sure for myself, starting exactly from where it started, from the beginning. So the mission of PTX is about speed up Spotify and developers by providing teams with a simple, consistent, and delightful experience. I think that simple and consistent now makes more sense to you because simple is closer to the simplifying the complexity, consistent and it's more about reducing the fragmentation. And honestly, my goal and our goal is also the third part, delightful, because our real goals is now in ahead, is one and unique and only, is make the developer happy because this is what we like and this is what we love. Thank you very much.


Alrighty, I have a 2025, what I'm going to start predicting as a 2025 construction update for you guys today. So for those of you that have been keeping up, construction markings and distance tracking and surveying has been going on in the Kingswood area and action zone area. And now it has consumed time warp and flight decks queue line. So the surveying has extended to completely surround time warp and include its station. So again, I'll be making a full on prediction for you guys in our podcast tomorrow on Time Warp's future at Canada's Wonderland. And yeah, I as of right now, I'm not ready to make a prediction on flight deck, but we'll have to wait and see another two weeks if these survey markings keep moving. Because as of right now, you're going to see them, they start to surround flight deck. But I only see them attached to the queue line structures of flight deck, whereas time warp, it's attached to the actual structure, the station and completely surrounds the entire attraction. So that's where things start to get really interesting for time warp. It also just makes sense that this ride is on the chopping block and going to head on out to maybe one of Cedar Fair's smaller parks, as it doesn't really make sense at Canada's Wonderland. And if you actually stand at the exit to this ride, a lot of guests don't like it.  So I 100% see this ride being gone at the end of this season. In fact, I have a really strong prediction that I'll be able to make on 2025 in our podcast tomorrow at 8 or today at 9 30 p.m. But yeah, I just wanted to show you guys the new survey markings that are completely surrounding time warp and flight decks queue line and around flight decks drop. So it's a very large area. I also am starting to hear little birdies about 2025. So again, stay tuned tomorrow because I honestly am ready to start talking about some things.  Anyone who knows me knows that as of now I'm getting pretty close to being able to talk pretty comfortably about 2025. So I just realized what I caught on camera there for a second. When I was filming that, I did not know they did that. As I'm recording this video, I just clued in as to what that mother just did. But yeah, nonetheless, it's exciting. Like honestly, the rumblings I'm hearing, this could be one of our largest coaster projects ever. You know what? Maybe I'll drop a little tea. The construction for this new project in 2025 will start in December. So stay tuned because this is really exciting. I'm starting to hear, you know, there's some permits being filed and stuff like that. So stay tuned, December, we should start seeing construction start for our 2025 coaster. But yeah, it's definitely going to be a really big year and it's going to be a really big project. When construction starts that early, yeah, because just to put it in perspective, land clearing didn't start for something like Leviathan until April. So let's say April next year, 2024 is when you would have seen construction start for Leviathan if it was opening in 2025. Hopefully explain that well there and that makes sense what I was just trying to convey. But awesome. Can't wait to explain more in tomorrow's podcast or today's podcast. See you at 9.30pm. Have a good one, guys. Bye.


Besides the official talks, I had the opportunity to go to rural Damascus, which is actually still Damascus City is a city environment, a highly populated environment. We see a lot of people injured. We see health points and hospitals with insufficient medicine, with little staff to attend a lot of patients. You see a lot of shelling having gone on, apartment buildings destroyed or burned. You see children which are under shock still from the violence going on. All consequences of an armed conflict unfold in front of you. The meeting with President Assad was very factual and to the point and was focused on humanitarian issues. He appreciates the work ICRC is doing. He appreciates the work and cooperation we have with the Syrian Arab Red Crescent. And he was asking on what he could contribute to make our work more important and to scale it up. So I mentioned the obstacles at the present moment to the work of ICRC. The problem of bringing medicine and medical equipment into the country, to distribute it all over the country and to those places which are most in need. And we discussed issues of visiting prisons and of the protection of the Syrian populations, of internally displaced people. What I hope will happen now, I left Syria and the meeting with President Assad with several commitments to improve on medical delivery, on access of the ICRC, on increasing the scope of our operations. And I hope that first signs and positive signs of these commitments will materialize in the next few days. And I hope that within the next few weeks we can see improvement.


Let's take a look at a roll that I've almost seen happen a few times this summer, but hasn't quite yet, but I'm sure at some point it will pop up. And this is roll 10.2 or 10.12. This is the roll about what is and is not considered an error. I'm sure every official score out there has read it many, many times. But this part of it is actually a comment on the first part of it that clarifies that whenever two fielders are to collide, that it is actually the fielder who does the colliding that is charged with the error. And this is to say if we have the few times that I've seen it almost happen is whenever we have maybe a fielder out in left field, maybe he's running in to get the ball. We have a shortstop coming back and they would knock into each other. The ball would get away and something like that. So let's say in this situation that does happen, we have our left fielder, he runs up, he's parked underneath the ball, ready to catch it. The shortstop might run over backing up, maybe he doesn't see him, and he knocks the ball away. In this case, because the left fielder was parked underneath the ball, ready to catch it, and it was the shortstop that knocked into it, we would charge the error here to the shortstop. He did the colliding, I guess you could say. It was him who knocked the ball out of the other fielders' glove and caused that misplay. So it clarifies then in the second portion that there aren't two errors then charged on the play. It's not both of them who get the error. Only one error would be given out on the play and then it would be to the collider. Remember, not always do we have to charge an error. The rules which define an error say that the fielder only has to display ordinary effort. So maybe if the ball was hit into the gap, say the left fielder is running over here, the center fielder started here and they both have long runs. Maybe one knocks into each other and the ball gets away. Maybe that won't necessarily be an error at all. Maybe it'll be a hit. But for the most part, remember, it's the fielder who causes the misplay of the ball who is charged with the error.


Welcome folks, this is Tom O'Brien of TFNN. We go five days a week, we go seven hours a day, we go 24 hours a day on the internet at TFNN.com. Always remember folks, whatever you think about, you bring about whatever you focus on, grows, hope everyone's having a great day, safe day, it's making a great night, a great week folks. You have the power to create. Your power is so strong that whatever you believe comes true, you are that way because, that is what you believe about yourself.  Mugging wise, let's take a look at it out here. We have the Dow Industries down 156, Nasdaq's down 10, S&Ps off 15. Gold, gold contract down $3.10, trading at 19.20 an ounce. We have Silver down 14 cents, $23.05 an ounce, light sweet crude, up $1.68, $69.38 a barrel, notes and bonds, 10 year note, trading up 13.6, 1.1308, the 30 year up 22, at 1.2807 and King dollar. King dollar right now is trading, where are you baby? There it is, up 4.36, at 102.928, the year is at 109, the yen is at trading at a price point of 144, the British pound is 126 to one US dollar. Our phone number's<PHONE_NUMBER>, give us a call folks. One note's going on in your world. Just had to hit that button folks, okay, because we just came down and tested here. Let's go do it. So let's go over to the e-mini first. Let's take a look at it. Okay, so we did the update just prior to it. We were looking at that bar and we just came down to this bar and you're gonna see a rejection here. It's gonna be interesting to see how this shakes out. This is July 4th in summer trading combined folks. That's what's so wild. So you can see what we just did, we did the update. We were talking about the bar. The bar has 58,000 contracts. The bottom of that bar was the 4406. No, 4403. Bottom line is that we just got down to 4401. How many minutes were into this? Yeah, you get nine minutes. It's not gonna happen. It's gonna be a rejection of lower price. This is just a shake out down to the bottom. You're gonna see the market rally again. Let me see, did I get my trade? Did I get it? Okay. Bottom line, we'll see how this shakes out now. Now the bottom line is that you can see what happens here. We'll start, you're gonna get a rejection. Now the question's gonna be, is that do you have any juice to go back topside or are they gonna unload on it? That's on the E-minis, okay? We go into the NQs. We take a look at the NQs. Okay, so the NQs, that bar, 19,000 contracts, 13,000. Not enough sellers folks. That's the bottom line. You're going high. We're torn to trading range, but that's how this shakes out. See, you can see on the way back up, we didn't have enough juice either to get into the bar on the way down. So what we had done inside the NQs is that we did just over 50% retracement on the way up, which is bullish. At a 50%, you really don't know. It goes both ways, actually. This is a little bit over. But the E-minis, when we did that, we did... Let's see what you got here. That was just about a 50. Gold, would you take a look at the gold contract out here? Excuse me. Gold contract right now got down to 1911. Excuse me. 1911, excuse me. It's straight in 1919. You're going to have a contraction of volume. Let's go look at the GLD for a second. So the GLD's rejected low up. Oh, this is nice, man. This is real nice. Okay, so check this out. If the GLD could get about 20 cents higher. So 177.63 is your benchmark. And you can see right now would be below that by basically 17 cents. You're going to have much lighter volume even in the benchmark of 7.9 million. So that's what we want to see, because you have the rejection of lower price again, but you want to get inside that range. Notes and bonds, they want higher price. Higher price, lower yield are coming at us. This is going to be really wild between our own pile, between the Fed, the whole Boloax. You know, we've got another sideways move out here, but you can see this, see this up here. 1.2 million contracts, that's it. That is low contract volume beyond belief, and we did get down to 112.26. It rejected it. That's saying higher prices want to come at us, and then we go over to the good old US dollar. Dollar out here is as a trend going, well, my take is that the dollar is at the whole price. You know, we got to a price point today of 103.145. You're at 102.296 right now. So that baby's telling me that the way this is setting up, it's still setting up to get down to the lower end versus the higher end. So the higher end of the range that we're in is 105.800. The lower end is 100.788.  You have the Tesla is up 5.5 dollars. You got kind of up a dollar and a half. We have four to 30 cents. Carvan is up 370. Look at that, man. That thing was at $2, now it's at 28. It's a 10-banger already. That's pretty wild. It's at C3 up 2. If we go inside the NDX100 and take a look at the strength versus the weakness, Lucent is up 5.5 percent. You got Netflix up 3.5 percent. Siri's up 3 percent. Take it away from the JDs off 2.9. You got Regeneron off 2.5. Qualcomm's off 2. And you have an American Elector off 2 percent. Our phone number is<PHONE_NUMBER>. Give us a call, folks. We have the dial. The dial industry is right now down 106 now. It's up 16. S&P's off 8.5. We'll come right back.


Hi stampers, welcome to another week of Watch It Weekly Wednesday. I'm Aubrey, part of the Stamp and Jill Creative team, and today I'm excited to share with you a suite of products that's in the new annual catalog. The suite I want to share with you is the Stargazing Suite. It's on page 86 and 87 of your annual catalog, and it is so striking. The minute I turned to this page, I was like, oh yes, I have to play with that one. It's so, so cute. I have loved this one. I'm going to show you a few of the products that are in this suite and some projects that I've come up with using it. So first off, we have our stamp set, the Reach for the Stars stamp set. I love this saying, if I had a star for every time you brightened my day, I'd have an entire galaxy. You have your astronaut, you have your spaceship, or rocket, I don't know what the difference between a spaceship and rocket is, but whatever it is, that's what this is. Greetings friend, you're stellar and Reach for the Stars. Super cute sayings, and there's so much you can do with this. It also comes within a bundle. Here is the dies, so it has the astronaut you can cut out. It has the rocket ship you can cut out.  It has the rings for your planets, and then it has all of these circles that you can cut out your planets with. Super fun, and it coordinates super well with the designer series paper that's in this suite. Let me pull that in, so you can see there's six pieces of the designer series paper, and they're double-sided. I'll just fan them out here so you can see all of them. The really fun part is that one side has these fun bright colors, and the other side just has a ton of like galaxy space-looking paper, which is really fun, especially if you want to make a space-looking card, kind of like this one. There's so many papers you can choose from, and you can make a ton of cards with that. So that's really fun. On two of these sheets of paper, you can see there's printed these planets, so you have kind of the red, orange, yellow version of planets, and the green, blue, purple version of planets, which is very fun. And then you just have all of your galaxies, like I said, and then just some really fun and bright pieces to go with it. One of the other really fun papers in this suite is the holographic trio specialty paper. This one, when I look at it, it almost like makes my eyes go a little crazy, but it's so, so cool. You can see just that really holographic-y look, and it is so fun.  You can see it there, and then with the stars here, it just adds a sparkle to the cards. So you have just a silver piece. You have kind of that wonky silver piece. That's a technical term, I think. And then you have this purple-y pinky piece, which is really fun, too. So let me show you a few cards that I've made using this stamp set, and maybe give you some really fun ideas. So I started off by showing you this fun of the galaxy. You can see our little spaceman and a planet in the back. I said this one is Uranus. My daughter, Reagan, just did a report on Uranus, so I know it is blue. And it has rings, which I didn't know until she did a report. And it's tilted. It's on a tilt. So that's for her. Shout out to Reagan. And I know that it's pronounced Uranus. That's all I'm going to say about that. This is another one, Reach for the Stars. This is that dye that's in the dye set that has those cute little bubbly fill to it. It just, I don't know, it looks like space, really fun. Here's one with the spaceship and all of those really fun planets. And you can see in the background on this one, I used the wink of Stella to make the stars. So that's another really fun idea. Here's one I made using along with this suite, the It's in the Stars background set. That goes really, really well with this suite of products, too.  So fun. And bright card. And then your stellar. This one, actually, I got the idea from the catalog. You can see this one here. It's kind of similar, a little different. But I loved that look of the three different colored spacemen stamped. So that's where I got that idea. So fun. I've had so much fun playing with this set. I love the bright colors. I love the holographic images, and it has just been so fun. So if you're interested in purchasing these products, make sure to check the links below. And thank you so much for watching. We'll see you next week for another Watch It Weekly Wednesday.


or no resolution. It's their obligation to provide us with the information we need. And we are trying to look and try to find ways and mechanisms. And we have been trying to do this for many, many months unsuccessfully, so whether resolutions may have an influence on this or not, it's not for me to say. So far, we haven't been very successful. We continue addressing this issue. And we address it directly with them, independently of whether, if there was no resolution, I would still be asking them, please cooperate with me. So it is speculation, what kind of impact a resolution may have. One more. Yes. In your story about this, in your last report, what we have seen of it, reports of your report, there is an increase in the amount of enriched uranium to 60% and 20%. How worried are you that this is getting out of control in a way? Well, I wouldn't say it's out of control. But what I would say is that the program continues to show a degree of advancement, which is, of course, something that people are noticing. And this makes it even more important and relevant that Iran cooperates. These are very high levels of enrichment. I have said it many times. So of course, this is an activity that can take place. But when you do it, you have to do it in full cooperation with the IAEA, not with a reluctancy or reluctance or limiting access or with the things that we have been seeing. So it's part of a general pattern, I would say, that has continued for a long time now. So we hope that we can finally sit down with them, that we can reconstruct dialogue with Iran as soon as possible. Hello, Diji. Hello. That's going to Akini Bontalafshan Network. I have two questions, too. So let me start with the first one on Iran. As since the camera data on the manufacturing factory is not given, and then there was a discussion of the loss of the data and the difficulty of reconstructing. Now, it's been quite a while. And what's the certainty of IAEA at this point, or maybe by the end of this year, to be able to really say that, yes, we can reconstruct what had happened? That's number question one. It would be very difficult, not impossible, but very difficult. You remember that last summer, when this happened, I said this is going to be very serious. And I'm sorry to say we were right, because we were hoping that the measure or the disconnection of the cameras would be temporary, that we would be able to have them again. This didn't happen. That doesn't seem to be a prospect of that again. So as you are rightly saying, what that prevents us is from having a view of things that have been ongoing for a very long time, for a very long time. Since February 2021, with data being registered and the cameras functioning, and from this summer, even without the cameras. So there is a mass of activity about which we don't know anything. So assuming being optimistic and assuming that there is a return to the JCPOA, and we have to provide the assurances about the baselines, we would have to have an ad hoc arrangement with Iran. It wouldn't be possible on the basis of the information we had. First of all, we had to check whether the old information, the information that was still being collected by our systems, is still around. And if that was the case, well, we should have to sit down and see what do we do about the gap that we've had for the past six months or so. So this, as we have said, would be technically very difficult, would require a number of partial and mitigation sort of measures, which would require us to sit down with them, to look into records, to talk to a lot of people, and try to reconstruct the jigsaw puzzle in between. If it was impossible, we would have said it. It is very difficult. OK, the second question. Actually, the second question is on the Ukraine. You have been diligently working on this agreement of the protection zone. Can you give us a bit more updates on what's happening now and what's hindering you? Not you, but what's hindering the? Well, it's a bit difficult. And I would ask you to bear with me on this, because it's an ongoing negotiation that involves military aspects as well, as you can imagine. But what I can say is that I have kept my channels of dialogue open, of course, with Ukraine. And naturally, I have to talk to Russia as well. And I have been doing this. What I would say is that the main issues that are being discussed are those related to the military equipment and some related also to the radius of the zone. So you can imagine that for two countries at war, they have different objectives. And I guess they don't want to see these military objectives being affected. My message has been very clear in the sense that whatever military goals are on the table, they should not include shelling of a nuclear power plant. And on this, I'm very clear with both. Thank you very much. Bethany Bell, BBC, a follow-up question to that, if I may. Is there a kind of timeline that you think might be possible in terms of establishing this protection zone around Zaporizhia? And what are the biggest challenges that you see right now to that? Well, in terms of a timeline, I wouldn't say so. But I would say that time affects the whole situation there, because we are there. What you see, you cannot measure exactly the degree of danger, because any day you can have a shelling, you can have a bomb being dropped, or the interruption of an external power source, which cannot be repaired fast enough. So my impression is that it should happen as soon as possible. The way, of course, we are looking into the, this is not happening against a peaceful background. There is an ongoing battle. And of course, we are looking at that. And what we see in general terms without getting into an area which is not my area of specialty, which is not getting any easier or any more relaxed or with less intensity in terms of the conflict. So I am extremely worried about it. And I'm trying to get it as soon as I can, as soon as I can, really. And again, how realistic is it, though, still? I mean, is this something that you have hopes for very soon? Or is it something that is... I think it's completely realistic. We have proposed something which is very feasible. We, you may remember that there were debates about whether this would be a fully demilitarized zone or whether we could involve other agencies or the UN blue helmets or things like that. Since we knew that all of these alternatives would make it politically very, very difficult, we adjusted it, narrowed it down to purely nuclear safety security-based considerations with the IAEA as the interlocutor. That was, I believe, a reasonable way forward since Ukraine and also the Russian Federation said that they were prepared to work on the basis of this. They were not saying, forget about this, this is something that we cannot even contemplate. No one has said that, which gives me hope, gives me the impression that we have material to work on to get to this. Hi, Raqida Bahnam from Al-Arabiya. I have a more general question. The relation between the IAEA and Iran has been steadily going backward over the last year, at least. Now, we know, I know you're not a politician, you've said this several times, but I know also that you need the support of politicians in order to be able to fulfill your job. Yesterday you were in Germany, we were not allowed to ask questions, so maybe now you could talk a little bit about how much political support you actually have. What did you hear yesterday from the Germans? Do you feel that there are some countries that are a bit more reluctant and to giving you the full support you need in order to be able to... Are you, excuse me, if I ask you something, are you referring to Iran or Ukraine? Iran, sorry, only Iran. Yeah, well, very good. When it comes to Iran, I believe that the support the IAEA has is really overwhelming. I cannot see anybody questioning what we are doing on the contrary. I think that irrespective of the debates that may be taking place, even among the hitherto united front of the JCPOA, which has now some fractures, everybody says, everybody recognizes that the work with the IAEA is indispensable. There wouldn't be a JCPOA without the IAEA who would verify, who would guarantee, and the still and clarified issues that on which I have been pushing would still require the agency. So if there is an area where everybody agrees that there must be cooperation is on the work with the IAEA. So I feel very supported and understood when it comes to my work with Iran. Of course, we haven't reached a point where we see eye to eye with Iran still on these issues. I keep trying and I will still keep trying. I only believe in a diplomatic solution to this based on the technical work of the IAEA. This is what we need to achieve, really. Hi, DG, Tukhshinivs Agency. Sorry, yes. Yeah, Tukhshinivs Agency, honorable. Yes. I have two questions about the Saporizhya. Yes. As you know, the high-level employer or worker from this NPB was detainee by the Russian forces. Yes. Do you have any information that you share with us? Yeah. First question. Second question is about the save zone, the nuclear save zone. Yes. I guess you meet some different countries or some different politician leaders. Would you like to speak this topic with Turkey? You know, the Turkey play a different role. Would you like to speak this topic with Turkey that can maybe help? I don't know. Yeah. Well, thank you very much for the suggestion. On the first was on the prison. Yeah, well, as you know, the issue of the staff is one of the most important ones for me. It is the protection of the staff, the ability of the staff to work in normal conditions, which, of course, in the case of a war, like this has gone through the window, must be, in a way, addressed. For example, my permanent mission in Saporizhya is one of the ways to do that. They are listening to the staff. They give advice, et cetera. And we are doing the same here. What you refer to is a more delicate issue on which, as you know, the agency, when it could play a role. There were cases of some experts or members of the staff of the plant which were detained. And we were able to, in a certain sense, cooperate to assure their release. This happened over the past few months. There are still a couple of cases on which we are consulting. And the situation is not entirely clear yet on that. As you know, when it comes to these issues, there are many factors involved that have to do with prisoners and the exchange of them. But when we can, we always try to play a constructive role. And I have been trying to do that. In terms of, of course, we value very much Turkey. I have been seeing Russian counterparts in Turkey a couple of times. I discuss that occasionally with the Turkish government. So we value very much their contribution. The contributions, they have been making in general in this conflict, above and beyond the nuclear. I think we have to exercise every possible means to stop this war. And I think any effort and those efforts are very appreciated by the international community, and including myself, of course. Sir. Hello, Diji. Hello. My question is, two resolutions in the Board of Governors in six months, means the US and E3, also international community, are disappointed about the revival of the JCPOA, also about the Iranian cooperation with IAEA. But it seems you are personally optimist. Could you tell how much is the limit of your optimism about the Iranian cooperation with the agency? Thank you. Well, I don't know if I would say I'm optimistic. I am determined to continue. I am not going to stop in my efforts. My effort is aimed at making Iran cooperate with us, understanding that they have an obligation to do that. Of course, they are a sovereign nation, and I cannot force them to do this. But there is an objective international law obligation that they have to work with us. What we try to do when it comes to a certain area, which is very technical, where they need to provide some answers, is we try to do it in a way that would facilitate their coming forward with this information. I don't want to get into too much technical detail, but there are different ways in which a country can provide information. We try to facilitate that by putting questions in a way that will allow them to cooperate. So I think it is in their best interest, honestly, to work with us. As I've said many, many times, the IEA has no political agendas here. We are abiding by our mission, and they have an obligation to do this. This is the basis of peaceful nuclear activities in the world. When you conduct nuclear activities at Iran has a very ambitious program, you have to go by the rules. And if there is something that was found that should have not been there, you have to explain. It's not a matter of a politicization of this issue, as some sometimes say. It is simply complying with the obligations. And this will be the only way for Iran to regain the confidence that they aspire to get. Without that, the confidence is not going to materialize out of thin air, unfortunately. So I hope they will cooperate. My question is a little bit like his question. Has IEA any deadline for this situation? Sometimes yes, sometimes no from Iran, from IEA. And how long will this situation continue? I mean, do you have any deadline? No, I don't like deadlines. Deadlines have a repressive connotation that I don't like. I think we have to work with respect, with mutual respect. Of course, taking the agency very seriously. You cannot continue for months on end and for years without giving explanations when explanations are due, when you have an obligation to give them. So I wouldn't talk about deadlines, but at the same time, we cannot continue with this forever. It is obvious that for the international community as such, if you add absence of cooperation with a nuclear program that is growing and growing and growing, then the lack of confidence is absolute. And this situation is not going to result in any positive atmosphere or any positive thing for Iran. I hope they can come to that conclusion as well. Thank you. Sorry, Francois Murphy from Reuters. There's a couple of questions, and one on Iran, one on Ukraine. Let's assume for a moment that this meeting, later this month, does happen with Iran. Your NPT report has a kind of interesting wording on what you need to see from Iran at that meeting. So I was just wondering if you could put it in perhaps slightly plainer English. I mean, the report says you basically need Iran to sort of start providing answers in this meeting, which suggests they need to show you like a tiny little bit of something that would be the beginning of a process. So I'm wondering how would you describe what you need to see from Iran? And then on Ukraine, it was about three weeks ago that you were on the doorstep of the UN Security Council and you suggested that an agreement could be reached within days. I mean, you often put it in terms of what you hope rather than what you expect. But you said it could be, you hoped there would be a deal within days. And here we are, three weeks later, still no deal in sight on the protections on. I'm just wondering if you can give us some sense of how these talks have evolved. Because for us, it's essentially a black box. As long as we have no deal, we have no sense of how it's going and you tell us we're not there yet. So are we closer than we were? Are we further away than we were? How is it going? I understand. So the first part on the wording and what we expect. I think you're right. The wording reflects what it reflects and you understood perfectly well. Because what we have been getting is, I mean, it's like we are talking past each other. We are asking questions and we are not getting answers. Or the answers we are getting are answers as I think quite, in a very direct way, I characterize them as technically not credible. So we are talking with experts, among experts, and we are saying, well, what you are giving me, it's not possible. So please try again. And so the idea for me has always been because I'm trying to be optimistic, as the gentleman was saying here. And the verb start I think has this meaning. If we start to see that some of the technical answers point to the problem we are signaling, well then it's something that I would be happy to reflect. One of the things that I often hear is that from some Iranian counterparts is that we are not reflecting something positive. We'll say, well, start delivering something. For me, engagement is not simply that you sit down or that you, we tried that already. We tried having calendars, having periodical meetings, quarterly meetings, monthly meetings, bimonthly meetings, here, there, everywhere. It's not working. So we can sit here and in the space of one minute, I will realize whether this is meaningful and we are getting into an area that is related to the origin of the particles in these places and the information we are showing them. And this hasn't happened. I hope it will, I really hope it will soon. Regarding Saporizia, in fact, maybe it's a black box, but it's a small box because what we are saying, what we are proposing is very simple, don't shoot at the plant, don't shoot from the plant. And the points of still of doubt are not that many. So I'm saying that it's small in the sense that you are not going to, if we can have the zone, which I really hope will be the case, you will not discover all of a sudden 24 pages agreement with annexes, it's a very simple thing which will allow for, will reflect a political commitment, very serious political commitment of both sides to stop doing something which is still taking place. And I'm not attributing anything. It's still taking place. So we are having yet another series of consultations this week and the next week. It's going to continue. So I'm sorry if I cannot go much further, but there will be much more than getting to yes, really. That is necessary. And this is why we are discussing, I was discussing yesterday, as you were referring to with Foreign Minister Beabock in Berlin about that. There are countries that are very involved in this conflict and they have a stake in peace. They want to know more. They want to see how they can support us. And I need that because of course, this is a conflict where there are alliances, there are alignments as well. And these count as I have come to learn. Very good. I thank you for your interest and your questions and we will be seeing each other very soon. I hope. Thank you very much.


As the earth formed, it was rotating on an axis perpendicular to the solar plane, just like all the other planets. Today, it's off by 23.5 degrees. The 1970s Apollo missions to the moon collected 400 kilograms of moon rocks, that's 900 pounds on earth. These rocks showed a remarkable similarity to rocks here on earth. This indicates that they were made at the same place. An analysis of the oldest moon rocks showed that they are the same age as the oldest rocks found on earth. This indicates that they formed at the same time. These along with many other earth-moon system characteristics, supports the idea that the earth-moon combination was the result of a massive collision called a giant impact hypothesis. There is an animation created by full dome that illustrates how this may have looked. It's a hypothesis instead of a theory because there are a number of variations and not enough data available to enable definitive selection of the right combination of possibilities. The hypothesis that currently comes closest to what happened has it that a planet the size of Mars, called Thea, moved in from the outer solar system with major quantities of water and collided with the earth shortly after it had formed. It hit at a 45 degree angle, traveling at around 4 kilometers per second, that's 2.5 miles per second. The collision would have tilted the earth, liquefied, vaporized, and homogenized the mantles of the two planets and ejected massive amounts of matter into space where it coalesced into the moon.


On the court, the Bemidji Girls basketball team is currently riding a little winning streak. After losing three of their first four games, the Jacks have rebounded nicely, winning two in a row. Looking to make it three straight, the Jacks have...thief river falls on their hands. At the end of the first half, it was the rumor flatness show. Here passing by...great passing by Mackenzie Nicholson leads to the flatness three. Jacks up 37-24. Next possession flatness all by herself on the fast break. She stops and pops for the elbow jumper. Jacks up 39-27. Later flatness runs the give-and-go to Katie Elto. She gives it back to flatness. Mid-range jumper too easy. 41-27. Jacks leading. Flatness was not done yet in the first half. This time Lindsay Hildenbrand gets in on the assist. Flatness for three. That's good. Jacks went on. Went into halftime leading 46-29. They go on to win it 88-67. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


Hi, everyone, Joe for jazby'scasebreaks.com. Coming at you with another wax party break. This is Jasby's 8 Box out of the park baseball mixer. Pick your team number two from where else jazby'scasebreaks.com. That's the only place to be. Here on Thursday, big thanks to Carl, picking up a ton of teams at the end, including LastBot Mojo Braves. So good luck to him. Good luck to everybody. Thank you for getting in. Let's start with triple threads. We have one, two, three, four, five, six, seven, eight in this eight box out of the park baseball break. We've got another one in the store. Check it out, jazby'scasebreaks.com. Pick your teams.  Whatever inexpensive teams there are, I would snap those up. At least throw your hat in the ring for a wax party break. Details of that promo, jazby'scasebreaks.com. Check it out. We go. There's Vlad Guerrero, Jr. to 125. For Carl, Javi. Also for Carl, Garrett Cole, Yankees, Carl, Mookie Betts, Aaron, Aaron Salinas with the Dodgers. And your hits. We have triple relic, Byron Buxton, 24 out 36. Blasts to begin. Walter with the twins. And then behind Henry Aaron is Alec Thomas, 39 out of 75. Rookie Otto for the Diamondbacks. Diamondbacks have a great crop of youngsters coming up the ranks. This is going to go to Ryan and the Snakes. Behind the Man of Steel is Tony Santillon, triple relic and autograph, 35 out of 99 for Carl and the Reds. And then we've got Jazz Chisholm, 18 out of 18. Piece of the jersey going to Carl and the fish. I want to go marlin fishing someday. It's on the list. Go to Florida, charter a boat or something like that. That's what they do. You can rent all the other stuff. I would imagine. You don't have to buy all that stuff. You've got to use a standard fishing pole for a big old marlin. Go out on the boat, catch me a marlin, bring it back to one of the dockside restaurants, have them grill that mess up for me. Maybe read the old man in the sea, that'd be appropriate for marlin fishing. There's C.J. Abrams for Carl, John Carl Stanton for Carl, Trevor Story for Zachary, and Reggie Jackson for Peter. You want to go too, Carl? Who wants to go? Should we make the Sejasky trip? There's Racing Home Glaver Torres, 13 out of 27. And behind the man of steel is Key Brian Hayes, 33 out of 99. Right, got to read the Hemingway. It's short, too. You could read that in a quick read, afternoon. There's Byron Buxton, a 469-foot walk-off. Wow, nice, nine out of 27. It's a big hit. It's going to go to Walter and the Twins. And then we've got in Julio Urias, one out of nine, piece of the jersey on the IL right now. But hopefully, he gets back soon. Aaron for the Dodgers.  Yeah, I think so. What was Hemingway's drink of choice? Would that be, should we do five stars in the baseball as the two-five stars? We'll close with Dynasty. Rum, maybe? I think he's a rum guy. I went to Pamplona once to run with the Bulls, which I did. It was awesome. There's a bullfighting ring. And outside, there's a statue of Hemingway. Pretty cool. Here's Emmanuel Rivera, 31 out of 75, rookie auto for the Royals. Ryan for the Royals. Rex wants to go to Florida just to meet Florida men. All right, Rex, I might want to let your wife know about that. We got the chicken man, Wade Boggs. Nice, Boston Boggs for Snell. Florida men, says Rex. Yeah, Rex is doubling down on it. Do you know that Florida also has a large monkey population? I did not know that, no. If you visit, right, Wade Boggs. RIP Wade Boggs, one of my favorite sunny episodes, Frank. The, oh, Rex wants to meet famous Florida men, I see. Yeah, if Rex is going to be meeting men, they better be famous. Not just any man will do for Rex. Famous men. If you go to Hemingway's place in the Florida Keys, there's a lot of six-toed cats that are there. There's Hoy Park, rookie auto for the Pirates. Oh, Florida men. Florida men. Well, not that there's anything wrong with looking for Florida men, right, Rex? That's not what you were suggesting, right? Not in 2023. Carl with the Pirates. And there's Daryl Strawberry, 47 out of 50. Wait, who's the Florida man? Are you talking about the Marlin man that sits behind the home play and baseball games? Here's the straw man, Daryl Strawberry. That's going to be Mets Edition for Carl. Baseball time. You have been there. I've not been there, Carl. Yeah, the six-toed cats. There was like one or two six-toed cats and they've all inbred and they've produced more six-toed cats. There's a lot of them. They're all feral cats. Just roaming around the residence. All right, this has a Hall of Fame logo on it. Put your thinking caps on. I know it's a little late, so I'll make these clues very easy. I'm a left-handed hitter in the Hall of Fame. Played for two teams my entire career. Batting average, 286. Lifetime 2004 and 72 hits. 541 home runs and over 1,700 runs batted in. 10-time All-Star, three-time World Series champion and World Series MVP, ALCS MVP. Seven-time Silver Slugger, AL Home Runs leader. My number retired by this team. First ballot Hall of Fame or 77.9% of the vote. Who am I? The ball, not me. I know who I am. Larry Walker, which is he at 541 home runs? I sure can, James. There's a DVR function on our live stream. You can rewind just a little bit and you can catch all that again. Thank God for technology. Remember, the baseballs go to the team, the player played for the longest if they're retired. The team they're currently on if they're active just for the baseballs. And if it's a multi-signed baseball, we'll just figure out the most appropriate way to randomize it. Yep, Frank's got it. Big boppy, David Ortiz. And sometimes the baseballs will have a team logo or insignia on it and that'll kind of help with that as well, but David Ortiz played for the Red Sox the longest. There's all the authentication stickers right there. And that's Zach Snell, Snell with that one. Snell, yeah. The Hall of Fame logo on there. I went to the Hall of Fame last summer. It was a lot of fun. Cute little town, very small, but had a lot of time at the Hall of Fame. There he goes, Zach. All right, next one. Now, the Guess the SIG game is boring. That's no fun. That doesn't require any thinking at all, Joe Pizzle. Joe only wants to play that game because he's good at that one. Oh, and this one's easy. I can't show you this one. This one's too easy.  Not as fun, not as interactive. It's just like, I'm just waiting for people to try to guess what Scribble is on there. Who am I? I'm another Hall of Famer, first ballot Hall of Famer, with 77.5% of the vote in the late 90s. Three-time All-Star, two-time AL MVP, a Gold Glove Award winner, three-time Silver Slugger, played for one team my entire career and ended my career with a 285 lifetime batting average, 3,142 hits, 251 home runs, and 1,400 runs batted in. Who am I? From Danville, Illinois, and then briefly lived in Covington, Indiana, then his family moved to Southern California when he was an infant, and then he went to William Howard Taft High School in Woodland Hill, he went to Taft. I had a friend used to go to Taft. Was third pick overall in the June 1973 Major League Baseball Draft, one slot ahead of fellow Hall of Famer and 3,000-init club member Dave Winfield. Yeah, James has got it, Robin, yow. There it is on it, gotta pop this baby open, let's check out that auto. There it is, played for the Brewers. His entire career, that goes to Carl. Oh, is that a hits inscription? Oh yeah, nice, yeah, 3,142. That's pretty cool. Rockin' Robin. Rockin' Robin, tweet, tweet, tweet, Rockin' Robin, tweet, tweet. Also earlier, Frank was mentioning that is that Hemingway's favorite drink, according to Google, the mojito? What is in a mojito? Is that rum and, I just drink gin straight up. I'm one of those guys, or Jameson, straight up. Mojito's rum and a soda? Soda, butter, and a lime, maybe? Oh, mint, mint in it too. It's a minty drink. All right, we got an active player, ladies and gentlemen. He's one of those bats left, but throws right kind of guys. A DH right fielder, working on some first base from Vegas. Lifetime 281, currently has 1,400 hits, a little over 1,400 hits, 288 home runs, 824 runs batted in, 124 stolen bases, played for two teams my entire career. Seven-time All-Star, two-time NL MVP, an NLCS MVP, an NL Rookie of the Year, a two-time Silver Slugger Award winner, et cetera, a Golden Spikes Award winner, Home Run Derby Champion, et cetera, et cetera, et cetera. Yeah, Frank and Carl's got it. It's Bryce Harper. He's currently on the Phillies. See, this one was too easy to show too. All right, there you go, Carl. Yeah, he's not good. Guy's not very good. Now, back in 2015, after he won his MVP, I asked people, will Bryce Harper win another MVP? And I feel like most of the responses were no that he would not win another MVP. Then, he won an MVP in 2021. So, I'll pose the question again, does Bryce Harper win a third MVP at some point in his career? All right, congrats, Carl. Now, let's see what's in this Dynasty box. No, no, says Joe Pizzle. Three is kind of hard, right? How many ballplayers have three MVPs? Let alone two, let alone one, but all right. The final hit, hide the ink with my thumb here. What we got here? The face is starting to show up a little bit. Ooh, I know this person. It's the wizard, Ozzie Smith. Nine out of 10, three color patch and autograph. Think currently a, I wanna say he's currently, what's he doing these days? Professor at Hogwarts, probably? Nice one, Cardinals, the Josh X-Line. The Josh X-Line, the X-Line. Josh X-Line with that one. There you go, ladies and gentlemen. I'm Joe for jaspyscasebreaks.com. That was Jaspy's eight box out of the Park Mixer. Picker team two, Picker team three is in the store right now. And it's also a wax party break. So let's give away the wax party invite in this one here. Dice, list, let's roll it, randomize it. Six into four, 10 times, name on top, gets the invite into the wax party. Good luck everybody, one, two, three, four, five, six, seven, eight, nine, and 10th and final time. Now we know who has the odds, but did someone pip that spot? Pip that spot, is the English would say. We'll see. No, no pipping here, no Wally pips here, Carl. No doubt about it. Your name's on top. You got another wax party invite, Carl. Thank you very much, man. I'm Joe for jaspyscasebreaks.com. Thank you very much, everybody. I'll see you next time for the next break. Bye-bye.


Tady jsme těchto lésov, který je hlavný obstáčný lésov, který budeme říct o výbraně. Toto se, které jsme vytvořili v repozitě. A jsme říkáme, jak je výbraně které je výbraně. A jak je výbraně, které je výbraně. A které je výbraně, které je výbraně, které je výbraně. Jsme výbraně. Máme říkáme, jak je výbraně. A které je výbraně. A které je svým výbraně. A to je hlavný lésov, který je svým výbraně. A které je výbraně. jsme nám nevíme na to závodit, co je závodit, které je závodit. Líber je závodit v závodit C. Jsme vzítel návodit Gamatech závodit. Tímžíme staticky závodit. Jsme nevíme na závodit C. a definitivně máme pdf manuál, který je zběžené na doxigeně. Když se vám cítí, který je v České repozitory, který je v dělávou folderu. Všichním se, které je těžké vývědět, které je těžké vývědět. OK, těžké vývědět, který je v repozitory, vyslykáváme pakete LAYBA, které je v mě. V mě to je F4 a vývědět.1.11.0. A těžké vývědět. Vysláváme vývědět, které je vývědět. A těžké vývědět. A těžké vývědět. Vývědět je vývědět, které je vývědět. A v mě to je F4.01, který je vývědět. A těžké vývědět. A těžké vývědět. OK, těžké vývědět. OK, těžké vývědět. A ... .. D состояни do týespera. To je to d 걸orka, který ho dost construir knowledge, porél ten k Despuésup school z shortage of knowledge and how to play. AORT AORTA t.ex. z ADC, které jsou funcí na initializací a initializací. Co je tým dělom tým dělom? O tom můžeme říkali jsou těchto dělom, ale ménu je těchto dělom, který můžete těchto dělom tým dělom. To bude v těchto dělom tým dělom repozitory. Požílim o tým dělom, že vyspět je tým dělom. Jak se tady výjde? To je to závědětně světěstvícky. Můžeme se vytvořit, které je to výjde. Až se závědětí, které je to výjde. Aby se to dál výjde, které je to výjde. Aby se to dál výjde. Jak se vás zvukává však parámetrov, co se učíká občává všechny a jak se zvukává nejvává filé na librá, na které výjde filé, když si vám cítí, co se vám cítí a co se zvukává. A kde se librá všechny však však však vůjde. OK. The basic overview usually we have in the v working in C, we have the source files and the include files. In your project you may mainly use your source codes, in your user source code C files and also your user code the header files. They are also files, mainly one file called stm32f4xx underscore it.c in case that you have the different family, the name with the f4 will be different and also related header file. Now this files, your files and this interrupt header file, the underscore it is the file which handling the interrupts. About this I will talk a little bit later. And these two files can or must include the library. The library include is done only with the one file and this is the stm32f4xx underscore hll.h. You need only include this one file into your user code and in the stm32f4xx underscore it it is done automatically is generated with the cube and mix. Only you need to add include into the stm32 hll into your code. You can see there is also some source files mainly for each payfile. They also include the hll.h. There is some configuration files, the payfile header files and some definitions of the registers and also of the types. And on the bottom there are some cmc files which are usually co-paid with the decor. Some system initialization, stepped up file and the basic header file. The most basic header file which includes all the registers which we have inside the stm32f4. But for you it is only necessary to include stm32f4xx underscore hll underscore h.h. Now it looks very complicated but don't worry it's not so difficult. Now we can look also into our first project which we generate in the cube and mix which is the GPO toggle. I think it's a good example to compare it with our code to see where you can found this files. OK, I have here my GPO toggle example now opened in the system warbench from AC6. On the IDE now doesn't matter, it will be very similar. OK, we have here our GPO pin toggle but this is for now not important. On the top you can see we are including the basic stm32f4 underscore hl dot h. This is all which you need to add into your C file into your main.c to allow you to work with this library. This is everything for you. You only need to add this include file. I also talked about the interrupt. If you will search here in the application you usually have the user folder. We have main.c, you can see there is more files. We can look in the it.c and we can see we have here also stm32f4xx underscore hl dot h. This is only file which is necessary to have here to allow us to work with the library. In case that we want to hear write our user code. Everything is OK. You can also see here the stm32f4xx dot h. This file is not necessary and it's not necessary to use this file here. Definitely the header file from the interrupts it's necessary. Now we have the our user code and we have the HullDivers and also the CMC's library. Here on this slide it's only description which part belongs to which part of our library. Our user code is mainly the main.c, the stm32f4xx underscore it dot c. And there is the stm32f4xx underscore hl underscore msp dot c, which is the microcontest support package. About this file we will talk a little bit later. In the HLDivers is usually in the section which belongs into the driver. They are usually only the drivers from the pay files which we are using because we have the GPO now. It will be GPO. The flash which must be always present because we all the time using the flash. It can be the MA, it can be the power system, it can be the clock reset and clock control and definitely the core also. And these files must be there. And the last part is the CMC's. CMC's files must be also present. There is the startup file, which is called during the startup. And there is also the system file for the stm32f4. There is the basic initialization and the day initialization. About these files we will talk a little bit later. Yes, main.c, where the code mainly begins, the interrupts contains interrupt handlers, nothing new, memory support package. I talked about this before. I will let a little bit for the later. Ok, now we will look on the part of the drivers. Now something small about the drivers and difference between the drivers and the reference manual. Sometimes in the drivers you can found some profile, which are not directly inside the reference manual. A very good example is the USART. You can found in our reference manual the USART. In the USART description in the reference manual you found that the USART can work as the UART, the synchronous UART, can work as the ERDA, and also can work as the smart card. I think this is very clear. But in the HL library we try to a little bit separate this functionality, because each functionality always use the USART, for example the ERDA, but we write for this the specific HL API. Then don't be scared if you find the ERDA driver, that it's not in the reference manual, it's only the sub function of the USART, but it's called the ERDA. Something which is different from the previous libraries, which we had, it's that we try to create this HL library, this hardware abstraction layer, API to be more universal for each family, to allow you use only one API to work on the multiple devices. Usually the common profiles, which have all these families using the whole API, but there is only one remark, usually the clock system is completely different on each family, then this is only part, which you need definitely very deeply to check and to adapt on your new family, which is the RCC, the IP, which is the reset and clock control. I think this is the same slide. Yes, the extension files. Some libraries, or the C files from the IP, have some extension shortcut called the name of the library, underscore X on the end. You have the one variant without the X, and then second with the X. What does this mean? This means that, for example, this functionality is extension from the other families. Here is an example that the API was not before on the other F4 families. Like for the flash, it was the PCA protection feature, was not before on the F4 family, and with the STM32F429 we added this feature. For us, it was not a common feature on the STM32, then we not put it into the flash.c, but we put it in the flash underscore X.c, to define that this feature can be unique only on one particular part in the family. Here we can found it into our project. If you look, if you have the F4, you can found the flashdave.c, which you have the basic functionality for to unlock the flash, lock the flash, erase the flash, program the flash, but in the flash underscore X.c you will found the specific API for this cell type, which is usually to enable the PCA. In this case. OK, the second reason when we putting the X, that this feature is completely different from the other families, not only inside the, for example, F4, but this functionality is completely new because it's not, for example, on the F1 or on the F3, then this is also reason where we putting the X. On the F4 family, it's usually the RCC, the reset and clock control, when we add some more functionalities into this API, which is unique for the F4 family and it was not before on the F3 family. OK. The last part is not that we adding the underscore X, but we adding the new, completely new IP. Then we also add the completely new driver file. Example is here the LTDC controller, which is the LED TFT controller for the TFT displays, which is start with the STM City to F429. The previous devices don't have this feature, but it's completely new IP, then for this we not create the X file, we create the completely new driver file. Yes, and something to work in your project, to work with the library, you need to check if in your preprocessor is set to use underscore HL underscore driver, this definition must be there. If not, then you definitely not include, the library not include the files, it will be blocked. You get the error message, that you cannot use the HL library. And second part, which need to be defined as which microcontra are you using. If you use the different one, you need also to use the different microcontra. Because also in the library can be small differences between the cells types, and you need to specify which cells type do you have. If you look on this in the project file, again,