Hello, everybody. It's a great to be here. I'm from a range. We're going to talk a little about Cloud Foundry in Bosch and several other tools from the USS community. I think you pretty know a lot of them, of course. And thanks for coming to this session. It's based on just sharing, raw sharing from a user perspective point of view of what we need to get from scratch, meaning even no Bosch in it at all, up to having a multi-cloud foundry deployment in production for a few apps. But that's good. So I am Fabien Guichard. Oh, sorry. I am Fabien Guichard. I am cloud operation reader from Orange. I am technical and DevOps addicts. You probably should, if you want to dig into open source. Thank you. If you want to dive into open source product and manage with many other teammates, some of them are here. A multi-data center Cloud Foundry deployments. So it's not, of course, only me. I have high-quality teammates that make, you will see key contribution to the community helping us dealing with an operating Cloud Foundry in production. So a few words about Orange. We are a European telco company with more than 265 million customers around the world. In France, we have more than 30 million customers. The trouble is that you never know when they will connect to your services because it based on contracts. So you can have fewer customers, but moreover than 30 million. So in terms of scaling, you will see it's pretty tough to operate that kind of platform. And so we are pretty big and we saw that we could achieve and we have the scale to benefit from automation and from past usage. And you were a new member to the Cloud Foundry Foundation. We're a member since June 2017. And we came to the foundation because Cloud Foundry helped us to go smoothly to Cloud Native and to have some best practice and we have right now, we had contributions since 2012. So we have been users since pretty long and we felt that it would be a good way to give back to the community by being a part of the foundation. And the division I work on, the digital factory inside O-Range. So basically we're working for French, orange, France marketing teams developing and operating software for them. The interesting part for an operator is that we have more than 100 million space per view per day. So it means you have some scaling problem to deal with. So it makes the thing very interesting to deal with. Like every online advertising business model, the management has some very big expectations and it's cost a lot. And the digital factory has developed for a long time an open source software culture, meaning that we're used to deal with open source software community because basically you don't have to pay a lot of things, you know, in terms of product software. Few words, three data centers in France. More or less, sorry, from the CMDB was not great for me. More or less than 300 application, three cloud friendly production department based on the open source software distribution. And right now a few services we have on the French portal. So if you want to have a look on your smartphone or whatever, you can just go. They are being run by cloud foundry. Little disclaimer, in O-Range or the division are using proprietary and vendor distributions. Some of them are using red ad products, for example. So it's very of you from digital factory. It doesn't mean O-Range is using at all cloud foundry everywhere in open source way. And it's pretty technical, a pretty technical talk. So if I am, you know, quite clear, just ask and do not hesitate to ask questions at the end of the talk. I try to make myself as clear as I can. So from scratch, the first things we had when we started the journey was on highest. So we have Apache Clue Stack highest. That's great. It's a, you know, 100% open source software. So it's not open stack. And we are Xen as an hypervisor. So Xen with cloud stack, nobody else in the world probably had that by that time. So we started from that. It's really from scratch. So the first thing we needed to do to deploy a single Bosch releases, of course, safe resist by that time, was to have a CPI. Basically, you don't have CPI. You just can't push and to release Bosch deployment. So we contributed the first external CPI in 2015. So it's a CPI for cloud stack, basically. And when you want to produce, you also have to have a steam cell. So we had to produce our own steam cell for cloud stack Xen. It's still not upstream, but we are trying a work hard to make it upstream very soon. Once you have that, you are able to Bosch in it. You are able to deploy your first cloud foundry. So it was pretty quick then. And we have to move the first cloud ready application into cloud foundry. So basically the first developer in November making the very first CF push and saying, okay, it's working. Four months of work just to have a single and simple CF push working. But it was very interesting to do. And the second thing, the problems start there. People are realizing that you can't really go to production. It's not just there. You're making a bold. So we had security teams coming under the field saying, what does the steam cell come from? We have a lot of internal tools trying to rank the level of security of assets coming from open source community. Basically, you could have some backdoor that kind of sink into the code. So they are trying to detect. They were asking how the build pack is bringing the droplet. You know, you can just put some special libraries that maybe are going to have some open door to the internet. And the root FS also, how do you patch it? What kind of library do you have? So there was a lot of security assessments because cloud foundry was not really known. The security inside the community is pretty huge. They're doing a great work. But we have to demonstrate that to begin with. The second pretty big stuff we have to do is multi-site means you have to decide how to do HA. So there's two ways to do that. You stretch your database and you have to deal with CAP theorems, basically. So latency problem. The other one, the one we choose to do was to have three separate cloud controller database for each data centers. And we have a pattern deployment based on CD and you will see after Terraform to synchronize and to make the whole three data centers converge in terms of configuration. So it was by that time, you know, like challenges we took and you will see it works and it works. And the last, we are able to deal with multi-DC cloud foundry production because of security assessment and how we will do HA. And the first people came with the application and start saying we have troubles with performance. So we had to do two months work to show how what does it means performance problem in terms of application, in terms of external configured devices. So a lot of things to train to explain to our teammates and to our colleagues. I wanted to show the first schema we had. So it's pretty basic. I mean, if you go to the open source documents, you will see that you have to separate, basically, Bosch from Cotson plain from data plane. So in red and in orange, you have the data plane price. It means that's where we took the queries from the Internet and drain them to our own data centers. So that's where the bad guys might be and might come into your house. The red part, it's networks that are being accessed only by internal people. So you can manage them in a different way in terms of security. All the separation is being done on a very whole technology for those who are knowing that it's Internet segment network separation. I mean VLANs to 800 to 1.Q specification. So we are very at very low level in terms of separation. So now a lot of patterns are not being done like that, especially for people going to public cloud. But as we have our own data centers, we're able to implement that kind of patterns pretty hard. But, you know, that's the way we did in the legacy. So we produce that here. And you have the same thing on every data center. Sorry, my micro. On the right part of the schema, you have the marketplace VLAN, each offer at its own networks. So, you know, the firewalls are being routing everything and outracing and not every kind of service talking to each other. And we have a VLAN with Bosch and Concurse Prometheus, you know, all together. It's the same thing on three different data centers. And the special part that it makes possible to have an application of three different data centers running on cloud foundry. It's because of this device on top, F5 VPN devices, it's a lot balancing device with GTM, global traffic management. And it works with external DNS to provide some kind of multi-data center resiliency. But it's important, those devices are not managed in any way, neither by Bosch or cloud foundry. You have to provide them yourself and to make the configuration consistent with your own domains inside and your own routers inside cloud foundry. So, the first issue we had for them, you know, taking up in my mind, the first one, we are an operation team. So, we are not, we were not, sorry, used with Git, Git operation, Git flows, that kind of stuff.  How do you roll back without destroying everything in the Git tree, for example. So, we had to learn that kind of thing. And I think all people going to on-premise cloud foundry deployment shouldn't underestimate the training they need to do on the operation team to deal with that kind of things. And I did the error myself. So, I promise you, you never have too much training in Git operation. I don't mean Git flows, but Git operation themselves.  That kind of things. The second thing, he was a problem with garden last year in 2016. So, when you are using Xen hyper-verser, you install Xen tools, and he needs to have exclusive mounts of slash proc to talk with hyper-verser. Sorry, unfortunately, garden needs the same thing to work with Diego sale. So, when you have, with Xen tools, there was a problem. Both of them wanted exclusive mount on slash proc, it means that Diego was not being able to bootstrap the Diego process and we are not able to deliver any kind of container. So the issue is here, it has been corrected, but it was a second problem. And the two last ones, they are not on the operation, but more on developer part. When you push application to CoolFoundry, the first thing you have to deal with is that, okay, how do you connect to a database? Where is the configuration and how? And you have to make your developer know that they need to change the code, meaning that if you want to expose the services, the port you need to have in your code is not a viable or a config file. It's exposed with an environment-viable calling port. And the same goes to the services connecting to Redis, RebitMQ, Postgres, MySQL, whatever. So they have to change a little of their code and that's what we call cloud ready migration. Just being able to start with some different way of taking the port number in your code and taking the strings to connect to your database. But it's really the thing you start with, basically. And that's what we call going to cloud ready. The very first step, changing your code to do that. And the second thing we had with our front developer, basically they just do CSS, JavaScript and HTML modification. They put a five on the keyboard and two seconds after, they have the results. They were making the same thing with CF push. And obviously they were 30 seconds, 40 seconds. Okay, not cloud foundry, it's just not for me. Wow, what are you saying? So we have a plug-in that is able, so it's a CF plug-in sync that just lets you local environment, synchronize with the Roman containers without having to restage your files. So it was something not that big, but in terms of developer experience for the front end developer, it was crucial for them to be part of the project. So great, a lot of feedback, that's cool. So now how do we go more to production? We have seen that, okay, you have to do that to begin with, to be credible, but now we want to have some real end users using application running on cloud foundry. The finish, we decided not to be all the time in production because internet is a pretty wide world when you are a tier one operator like Orange. So you know that. So when you're not confident with anything, you just don't move full time on production, basically. So we decided to be only on business hours on production. It begins in September 2016, so pretty long ago. The first thing that we faced was how you manage multi-site configuration for your end users. Cloud Foundry is a self-service platform in terms of philosophy and when you have multiple deployments, people were asking, I mean, too many pull requests, we had too many manual tasks, provisioning, orgs, space, roads, domain, quota, everywhere. And we are not very confident if somebody is asking, I push my application on data center one and on data center two. How do you say for sure that the organization, the space, the build pack are going to be the same? I tell you, it will be the same. No, no, no, no, no, no, no. It's not going to work that way. So the first thing we had to do is what how do you manage consistent configuration across different data centers? And as I told you as a disclaimer, we decided to have separate Cloud Control Database and to use Terraform being able to take some Terraform files and saying, yeah, if you have that in source control management, I promise you will have the same thing, or at least I will try to have the same thing in terms of resource in your production configuration. So we open source Terraform for Cloud Foundry Configuration provider, meaning you will see a lot of resource to manage your Cloud Foundry configuration. Second was to have, of course, Prometheus, my. Thanks, Ferran, wonderful job. So we see that Prometheus is a must go tools if you are operating a large scale Cloud Foundry deployment. And the last one, of course, concourse. No more manual, Bosch upload, Bosch release, Bosch deployment. It was fun, but it's not very good to manage in the time and to operate your platform that way. So you have to basically to go to concourse. So once we did that, we were more confident having, since May of this year, full services throughout them. You have the URL on the prerecordial and put them on the internet full time, 24 hours, seven day weeks. Scaling three parts. So the most interesting, no, they are all interesting, but the most challenging one, Prometheus, a federation. How do you aggregate to make your architecture story of Prometheus, Terraform, I already told that to you and concourse. Two things that I think that are not being underestimated. The first one, we have our whole legacy ticketing system. So you just come out of the field and say, I'm going to scratch everything down. No, we are to provide interfaces pretty simple with Mattermost open source software for Slack, basically. And with Xymon, yeah. We are using Xymon also with Apache Clutestart, Xen servers, yeah. We like to be that way, open source way. So we have to provide some bridge with that tool.  You have Ruby in the same platform. So how do you manage incoming requests for customers or maybe from bad guys? So you have to look into WAF web application firewall. And there's two ways to do that. The first is to integrate them into the build pack. We have an issue on the PHP public app for that. So with mode security for Apache, basically. And the second one is to provide on your external load balancing devices to buy or to implement a WAF for all technology. They have both the drawbacks while dealing with both of them at the same time. So we don't have any kind of a greater idea. Quickly, Terraform. So that is one of Terraform files from production. So you will see resources, I don't see, but I think you have basically organization, spaces and for spaces you have security groups that you apply on your spaces to have generic firewall rules being opened. You see on the right side hold the resources and many more that can be managed with Terraform and you have the URL back on the bottom of the slide. So without that continuous deployment of configuration with Terraform, it's pretty tough when you scale and you have greater velocity to be sure that this configuration is in the exact same state on every data centers because we do not stretch and do not share the cloud control database. Concourse, so sorry, acceptance tests are red but it's real life. So it's a pretty simple one but we started with that and it's important to keep in mind that case principles keep in simple and just to start with simple things. So just deploy Cloud Foundry with Diego, you pass a smoke text each time you do every kind of modification, scaling the number of jobs, changing a release, changing a steam cell, whatever, configuration of a job and to have the acceptance tests running after that. I think it's very important and maybe obviously pipeline to have for hops. Promissives, Ferran again, wonderful job. The community has done really a great job on that because I mean, you just see a push and application and production and you just do that and you have more than 100 KPIs coming out of the box. So even with some vendor tools, pretty expensive, it just wonderful, I mean, that was the use cases that help us to move on some pretty like geek platform was technical ones to for the boss, oh yeah, okay, it looks fine. I have my home, my space, my application. Okay, it's pretty professional at last. So Promissives is I think for my own opinion, a must have in production for everybody running its own platform of course. And the multi data center federation. So we decided in terms of architecture to have primitive services for the marketplace being separated for those for Diego and Cloud Foundry. Both of them are being scrapped by a primitive master and the master, they are talking to each other to federate their home metrics. That's how we achieve high availability. I can promise for sure that we are nanoseconds or milliseconds, okay, but for our home use cases where we don't have like in banking or you know, real time system that kind of requirements, it's fine for us even if you have some one or two minutes delay in the federation of the KPIs. And what do we plan next? So three things, three are of security. It's in for a consultant from Pivotal, I can't remember his name, but we are trying to achieve the same thing as Google or whatever. Rotate your credential and your password often, repair your security, your CV as fast as you can and repay your containers each time a day or you know. So they are being done manually today and we need to automate, you know, like with things like trade-up, that kind of things. We had a lot of work to do on that. And you can see we have a terraform provider for credit meaning that you can put your passwords in terms of resources with terraform in the same terraform state file without having your password in plain text, you know, in the terraform file. So it's pretty cool. We want to have cow engineering not only in terms of incidents, meant to produce them. We have a few outage of course in production but I think it's a pretty good habit for a patient team to regularly put his own infrastructure down. And auto, yes, automator is more. So we have started a number of projects, CFOps automation. There are two part templates for Bosch and framework. The framework only is open source, we are working on open sourcing the template also. And yes, maintenance of the CF web UI basically because of the cloud controller evolution in terms of API. And challenges ahead. Marketplace, big stuff for operators. We really need to have some full and totally automatic provisioning of services. A lot of guys are just putting static credentials in terms of service broker or user-provided services or service keys and manage out of the box without slash v2 slash provisioning verb, their own clusters and for whatever database or whatever services it is. And we'd like really to have like Amazon or whatever slash v2 slash provisioning being used in production to provision on the demand and on the fly clusters on demand. So pretty big challenges ahead. Oh, yes. When you are in the operator, you spend a lot of your time dealing with network troubles. One of the most important one is flow management task. So we have to find a way. We are thinking about using service broker information to manage and operate external devices such as load balancer and firewalls. For example, it's not very clean in our head, but we know that for a time being when a provider wants to export the service on the port, let's say, 9,000, he have to talk to the people saying, let me, we'll let the flow come to this port, to my application, to my services. It's not dynamic. It's not automatic. So we need to work on that. And the last one, we started a project a few months ago with IPH NIFI to try to feed our machine learning tools with a lot of metrics from Log Regulator basically. So it's very early stage project, but we are hoping that we'll be able to have more than resurrection in Bosch but to manage infrastructure differently in terms of operation with machine learning in supervised mode, of course, not unsupervised mode. So thank you very much for hearing me. And if you got any question, feel free to ask. Now, the first thing is to see if the feeding model in terms of how touch detection is good, meaning when you ask to me, do you have an incident or not? I will try to put a lot of things in my head and my own experience to say, we have a problem or not? We're trying to achieve the same thing in terms just detection from the models. And the next things, of course, is to have, let's say, in terms of machine learning, supervised mode, some policies, predefined policies that the machine will try to make work based on its own detection model. And I'm dreaming, but Skynet, like things, is to have the unsupervised mode, of course, having some neural networks, detect some how touch we wouldn't see and to try to work out and to repair the things for us. But I think maybe five or 10 years from now. Now we are starting in supervised mode, training the model to detect what we call how touch. Just for trying it out. Ah, yeah, for trying. Okay, that's the idea. Basically, that's the idea we have. But yeah, keep on dreaming. Thank you. Any more question about VLAN, now network stuffs, operator stuff. How do you not know to manage Git comments in 2015? No? Okay, thank you. Thank you. Thank you.


Hello friends, welcome back to another episode here on the channel. I hope you're all doing great. And for anyone new to the channel, my name is Lee, also known as Osiris. Today, we're going to be continuing on with our VGC Series 9 content and featuring another very special team today from one of you. And thank you so much before we get into today's episode for everyone that has submitted their rental calls. We will be getting through them one at a time as soon as I am able to. But today's team is from TBV 4050. So thank you very much. A massive shout out to you as well for the team that you provided today. It looks a lot of fun. There's a lot going on in this team. And obviously you've got some unique kind of sets and item options as well. Obviously, the one that stands out to me is the Tap of Viny with the weakness policy. Now this can be a lot of fun. And I think if we can get it going, it's going to be a real way to kind of shut down opposing teams. You've got some nice options in the team. You've got the thunderous theory in which I think is a completely slept on Pokemon at the minute, especially with a lot of the got the tail Regi Alecki stuff going around. Or Clefairy, Regi Alecki sort of stuff going out. Like thunderous theory and completely shut it down with the Vault Absorb. I got some nice options for hitting opposing threats with the Thunderbolt. Obviously the Sludge Bomb and the Dark Pulse. The Sludge Bomb giving you an option to kind of boost your special attack as well. If you do go down a max route with it and the Life Orb just putting it to phenomenal damage output as well. Then you've got the Regi Steel kind of solidifying the whole team there with the Iron Defense combination, which is really nice. Grim Snarl going to be useful throughout. You know, just making sure that the longevity of the Pokemon are going to stick around as long as possible with the screen support, the speed control there with the Thunder Wave, and then a nice damage output with the Spirit Break to kind of reduce attack on your opponent's end. Venusaur's an odd one to see without the Sun, but you do have ways to get the Sun up. Obviously with the Cinderace there does have access to Max Flare with the Pyrobolt to get the Sun up if you needed to, which is always a nice option. So the Venusaur does have a mod there and Venusaur on its own in the right conditions can always be a very good Max Pokemon as well. So this is the rental code for today's team. If you do try it out, as always, do leave a comment down below. Let us know what your thoughts are on the team in a big shout out once again to TBV4050 for providing us with the code for today's team. I'm looking forward to getting into this one today. I think it's going to be a lot of fun. So friends, we'll have a couple of games of the team now as always. And then we'll throw the rental up at the end just to remind you all. So if you do try it out, let me know. But without further ado, let's get into our first match of today's episode. Okay. So first up, we've got a Celestealer, Glastria, Reggie Alecki, Rillaboom, Urshifu and Clefairy team. So a lot's going on here. A lot of threats and the Clefairy kind of very centric to around a lot of these threats. Obviously the Clefairy Urshifu, the Clefairy Reggie Alecki that we just mentioned both leads are going to cause us a lot of issues. Obviously Thunderous deals with those perfectly well. The issue is obviously if we see the Glastria come out alongside the Clefairy as well. So there's a few things that we need to kind of keep an eye on on what my opponent's doing. And we really need to protect the Thunderous at all costs. Like the Thunderous here is really important to us. So we need to make sure that we're preserving it, especially for an end game against something like either the Reggie Alecki or that Celestealer that Thunderous can deal with quite handily. So I think Grimstone's a great lead in general. Just with the disruption there, the screen support, it's always going to be a nice option to bring up top. What do I want to lead? Do I want to lead Thunderous? I don't want to keep it for maybe later in and kind of the other option is always going like something like Cinderace here, which could be a nice option alongside Grimstone with the sash. We could have something like Thunderous in the back and then have Reggie Steel as kind of something that we can utilise to kind of switch in and slow the game down if we need to. We've always got that body press option there. If we can deal with it. I think my green screen needs to be pulled a little bit that way. It's a little line, Sean. There we go. All fixed. Yeah. So basically the reason why I'm featuring more rental teams at the minute is obviously I mentioned on Friday's episode that I qualified for Playscape 4. So I'm putting a bit of work in behind the scenes and I'm actually going to start recording some of that content as well. So hopefully you put out after I've played Playscape 4 and stuff like that. So those teams will be coming, but at the same time, I hope you guys and everyone can understand that I want to try and do well in the event. So I want to try and put a bit of work into it and also being able to feature your rental teams is just a pleasure.  See how I can pilot them. Anyway, we've got Glastria and Rilla Boom out. So our lead's actually not too bad here. We want to, we could Max Inderis. We could Max Inderis here and kind of leaning on the kind of cautious about Max in it here.  We go for the Pyro Ball, Pyro Ball into something like Rilla Boom's a nice option. We can remove it from the field. It's probably going to fake out. Ooh, they're going to swish, they're going to swish. Okay, Clefairy coming in. That's not so bad either because I mean, we get, we get some big damage onto Clefairy, get the sun up and we're going to get our screens up, which gives us so much support against something like the Glastria. We may see Max Steel Spike into Grim Snow, but we should be able to take that behind the screen. Um, and the Clefairy is not going to be as much of an issue to deal with. Now we get this initial damage onto it and it does switch in. Obviously the grassy train is helping out everything at the moment. Everything touching the ground and the grass going to heal us up some magical, wonderful way. Um, but my opponent going for the Max with the Glastria and this is the thing, you know, this is why it wasn't the best idea to leave Thunderous because I think my opponent can easily identify that Thunderous is going to be a massive nightmare for them to deal with. So bring something like the Glastria up top means that you can, you've got such a good way. It puts us on the back foot straight away. Uh, whereas if we lead correctly adds G max, G max Cinderace. Okay. So we aren't going to get the sun up, which is, which is fine, which is fine, but we, um, now we should have went for the bounce there. Could have really cut my opponent off and wasted a max move. I mean, we can go for it the next turn as well and give ourselves a speed boost if we want. Um, it might not be a bad play, but the grassy terrain definitely helping us out a bunch. The issue is going for the, the, the fly now, you know, if we go for max Airstream now, then they could just max a hail storm into us and kind of call our bluff that way and that would make things way more difficult for us. Whereas we could just go. Cause another max quick will take us down for sure. I think we could just spirit break into the Clefairy slot and maybe max guard here. You know, I don't waste a turn of our max moves, but at the same time, I don't think the Glastria is going to attack into the Grimstone here. You've got following me. You're going to go after our max one. Yeah. And I don't think a spirit breaks going to be quite enough, but it's going to. Put it in range to get it the next turn. And we'll be able to scout what my opponent's going to try and do here. Steel spot. Okay. Okay. Okay. That's completely wrong. Completely wrong off the mark. I get the defense boost, which isn't ideal. Um, do they want the hail up? That's the question. As we could preserve Grimstone for a little bit later on. Um, I think Reggie steals all right to kind of bring in here. I just don't want to proc a weakness policy on the Glastria. That's the big thing for us. You know, um, I'm going to get a light screen it while I got the opportunity to, and I think I'm going to air stream into the Clefairy. It's just if the Clefairy protects it and we get absolutely bodied by a call here. Yeah. So they're doing that, but they may go for a steals bike again. You know, never know. Well, they may go for a max quick. I don't think they will. I think they'll go for a hail storm into Cinderace. I think that would be the most like, I feel like we've kind of baited ourselves almost by doing this, but we'll see. We'll see how it all turns out. You see Max quick or not. It's like cat and mouse at the minute and just another steals bike. The more kind of reliable, reliable option. Yeah. So at least we get our light screen up, which is always nice. And now my puns not maxed anymore, but neither are we, but we've got the option now to get Reggie stealing and also get the nine defense off, which is, which is a good starting point for us because I don't think thunderous is going to be a great call at the minute. I think we need to preserve. Like I said at the very start, I think thunderous is going to be something that we need to preserve till the very end. Um, so Cinderace again. Where's my opponent going to attack into though? That's the thing. I think we need to attack here because we need to get rid of the Clefairy soon as possible. Although can you afford to leave? I mean, we can bounce. We can bounce, but it's not really going to do us too much. We kind of put ourselves in a really horrible position the following turn. Um, I think they go after the Reggie steel here to just try and get on top of it before it starts iron defencing through the roof, but we've got the reflect up. So even though my opponent has got the attack boost with Glastria at the moment, it's a difficult situation for Glastria to kind of deal with both of these. Like you choose one and you get punished from the other. So let's see, help in hand. Where we going? What we seeing? So there's a Pyro Ball. You see it help in hand close combat maybe from the Glastria.  Our horsepower. Oh, that is brutal for my opponent. High horsepower missing here to see it. And that makes things very difficult for my opponent now. Now the Relaboon probably comes back on to the field. What's your fear? Okay. Urgy. Um, like a big thing here is like just get rid of Glastria and we are super fine like super fine. Uh, now what's Glastria's defenses looking like? Plus two defense. Not ideal. Um, be like we need another iron defense. And I think do we protect here or do we just bounce into? Or do we Pyro Ball? I don't like the thing is again, I don't want to set off the weakness policy. Like we could protect. I don't see Urshafu. We could Pyro Ball into the Urshafu to be honest, because I feel like Cinderace has got a free turn here. I don't think my opponent attacks into Cinderace. Yeah, I think they just canceled. Just a bit of a shame to be honest, but you can see where they're coming from like the high horsepower miss there. It makes it very difficult like it makes it harder for us if that lands because Urshafu then comes in and can pressure us a bit more. So not the best kind of a showcase match for us to start with the course, but we've got plenty of time. We can squeeze a couple more into today's episode. So we'll jump straight into game two of today's video. Okay. Up next, we've got Indeedy, Hattery and Glastria, Alolan Marowak, Azumaril and Slobro. So very interesting team, but so heavy on the trick room, you know, there's no denying it's going for anything other than that trick room here. You've got things like Perish Song as well, Potentially on the Azumaril and Bellydrum as well. It kind of leans more towards Bellydrum because of the Lightning Rod support from the Marowak. The two trick rooms set as you've got, Hattery and the Slobro both going to be impossible to stop setting up, especially with the redirection and the psychic terrain from the Indeedy. Okay. What's our best approach to this match? This feels, it feels very difficult for sure.  It makes things a lot easier for us for sure. Still got to be very wary around the Marowak. I think, you know, something like Tapu Finney might not be so bad, but then again, like screen support from Graham Snow is always going to be useful. I think Tapu Finney to this one. And then, I like the idea of Venusol here, but there's a lot of psychic that makes it very difficult to kind of deal with. It's just for those, I think we'll go thunderous over Venusol. At least we don't carry the psychic weakness there. And if we're not in trick room in the late game against the majority of stuff, we should be all right. Excluding like the Marowak, which would just absolute decimate us. The only thing that you could say that kind of counteracts the Izumaril a little bit is obviously the psychic train, which I think in most cases my opponent probably wants to lead with that. And if you do go the belliedrum route, it does make it difficult to kind of utilize things like Aquajet. Okay, well, hat indeed, that old combination. And I can see this doing quite well as we go forward in the format because I think it's something that a lot of players are kind of forgot about, but it's still very important to have a ring indeedy.  We've got the opportunity to the other option is go for a spurred break into Hatterain, but it's likely to go. I'm not will go for that because at least this turn we've got the speed advantage. The next turn we won't have the speed advantage. And then obviously prankster can kind of come into effect if we needed to with either light screen or reflect. Okay, it's the Marowak coming onto the field. The iron defense going to help us out massively. I wonder how much will take from the Marowak like Max Marowak is still going to do a heck of a lot of damage even behind a reflect even with a and the thing is you've got to worry about the hat thrown up a son. But then if you do that like Max Max flare from the hat, you're not maxing the Marowak. So you don't worry about that too much. I think we've got for another iron defense. At this point, we just have to try and slow the game down as much as we can. I think we've got to go for a reflect here just to kind of make the Marowak's life a little bit harder, which you would imagine is going to be the maximum. It may be the hat though, because the hat might like I said go for the Max flare and then power up the Marowak. But no, we're seeing the Marowak makes a little more sense going Marowak. I think that's the way I would have probably went for if I was my opponent. So just going to hope the reflect and the initial iron defense is going to be enough for us to take this big Max flare, which is definitely coming out. You would imagine so dazzlingly push push. There's a lot of damage and a life or a bat. Okay. Well, it makes a lot of sense and there's the Max flare coming in. What's it going to do?  There's so much damage. It does so much damage. I mean, we're going to get another iron defense up here, which definitely helps us but at the same time, the sun's up now. We do have the leftovers, which which does help a bunch. I think we've got to maybe even Max, Max God to be honest, but we can't. We've got no way to to hit the Marowak. You know, we could just protect here. We could just throw up a light screen. It gives us a little bit of stability against the hat. Reggie Steel is going to take still a massive chunk of damage. You know, but we've got to stall these trick room turns out. Um, and I do feel like relying a little bit more on on type of finny in this match potentially. No, we needed that. That's just to just take us down and get the type of finny on the feel for free. That's all we needed, but never mind didn't happen. Max like coming out. Um, okay. We take a tiny chunk of damage for that, so that's not too bad. I just don't see us being able to um, the only option is max and we may be able to take it and then we get a flash cannon off, but then we're stuck in the sun, which is not ideal. Um, and we need finny to kind of help us out in this match massively. The other option is go into finny.  I'm committing to this and we're going to go for a spirit break because that's what we can do. We can't go for the, uh, for the thunder wave. And I'm going to hope that with the additional HP with double iron defense, so plus four defense, even in the sun behind a reflect, I'm hoping that we can take an attack from my rock and then pick up the knockout onto the hat, which would be huge because that's like one key component of my opponent's trick room. There's speed control gone. So dazzle coming out takes down grim snarl as expected. Moment of truth. Let's see if my belief in this Reggie steel is going to be strong enough. Otherwise we just wasted a max 10.  Here we go. Get another defense boost under our belt and get rid of that hatterine, which is beautiful, beautiful, beautiful. Okay, so we're not sitting in the best position, but we're not sitting in the worst position as my opponent is now kind of finish their max turns. We've got one more turn to kind of get through of the trick room. Yeah, I think we bring in. There's no point. It's too dangerous to like play the the bait game against the Marrow. Okay. Zoomerall. What are you going to do? Zoom. We're going to misty terrain up, which is always useful. Kind of tempted just to double protect here in all honesty. Just max guard and the problem is I think we should moonblast the zoomerall just in case it does belly drum because then it gets a little bit dicey, you know, and we need to try and keep on top of the zoomerall at least. We're not massively threatened if we are. Tapping Finney, but we are as well at the same time like Poltergeist. It is a Paris song variant, so we don't need to worry too much. Yeah, this is the issue. They totally baited us here. But I mean, we said this. I mean, we take it pretty well, but these are weakness policy, not ideal, but the trick room turns do end and we get a little bit of nice damage onto that zoomerall. I mentioned send back to normal. Okay. Now we got max steel spike, which will help Tapping Finney out a bunch. Yeah, let's just double and I mean, do we see do we see the indeedy switch and I mean, if we do, then we've got to switch around. We can't afford to lose a Pokemon right now. Okay. Indeedy coming in because I think the my work here does max flare, but I don't know if it will be enough with like plus five defense to get Reggie steel. Okay, which where's muddy water mist? Of course it would miss the Marouac. Of course it would. We do have like dark pulse on thunderous.  Initial damage there would have been ideal for thunderous to kind of clean up for us. Paul to guys going after the Finney again. We've got the defense boost now. So we should be able to take this. Yep. Just about sun fade. So we're in a better position. Still got to worry about the parish song. Of course, Reggie steel in a spot where it is going to be able to pick up a knockout onto either the Marouac. The thing is though, do we switch out Finney now because we need to reset? Hmm. Yeah, I think we need to reset the parish and we don't want to lose Finney. The other option is just protect Finney this turn and go for the body press into the DD. Yeah, and then our last ditch turn go for the muddy water into the Marouac. That gets the chip damage onto it. Okay. When we're going to see the Marouac switch out unless we see the indeedy protect here, then we're in an alright spot because I think an expanding force we don't worry about really at all. No. Yeah, it's not going to take steel down. Okay. But the body press will take you down. And whenever body press will get the zoomerill because I need I need to switch Finney this next turn. But the zoomerill probably just protects. That's the big the big problem. The other thing is what I could do is just muddy water into Marouac. But does Marouac protect here because that's the big issue? I think my opponent just double protects. Honestly, like honestly, I think my opponent just double protects, which would be really bad. Like if they attack into thunderous, that's terrible for us because we probably lose thunderous at that point where thunderous is probably better to just come in fresh. But I'm going to really kick myself if they double protect here, which I 100% believe they're going to serve a switch in Finney out or need to preserve Finney. I think they double protect. But if they don't and they attack into Finney, then we're in trouble. Oh, no. I'll switch. I'll switch. Okay. That's it could be worse. Could be worse. Could be way worse because the play rough missing, but we are going to lose Reggie Steel, which isn't great. So I don't think the Marowak has. Protect on it anymore. There's no point in going for an ally switches next to him.  Can it? It's got fire attack. No, might have protected. Got ally switch goes to attack. It's all we saw from it. Like that big game in the game. I'm pretty sure it's used to detect, hasn't it? As well. The big game of the game is to get rid of Finney here. You know, we could just double protect. It does give my opponent the opportunity to go for a parish song, but it also gives them the opportunity to just we could double into the. Yeah, I think what we'll do is double into the zoom row. We'll go and we blast and sludge bomb. I think that's the play. I think they protect Marowak if anything are they haven't. Okay. Well, we get it just in one. Okay. Where we going? Where you going? Where you going after with the Marowak? We're going to get a moon blast onto it, not the best damage. I wasn't really sure if the the sludge bomb would get the zoom row to be honest. Flare blitz into thunderous and then Finney going to be able to wrap this one up. Wow. We actually take that because is the reflect still up then? Yeah. Okay. That's huge for us. Yeah. Huge and now we can just dog pulse and muddy water and it works out in the end. So tricky when you've got like these tricky Pokemon with ally switching these abilities as well that drawing moves but thunder is coming in and doing some work here and getting the big knockout at the end that we needed after the parish song which was always difficult to deal with but at least we got off to a good start in today's episode. Very good game to my opponent. Hopefully you all enjoyed today that the first one today. I think it was a really good one for us to kick off with of course and we will jump into it's not even our first one. I forget that we had that first game. That went a bit south because our opponent missing a move. So we'll get into game three of today's episode. Okay. Next up today we've got a team of Reggie Giggis Whimsicott Urshifu Rotomwash a Dragapult and wheezing. So another one of those wheezing Reggie Giggis kind of teams. We know all about them the neutralizing gas to allow Reggie Giggis just to be an absolute monster perform and do what it wants pretty much. And this is going to be tricky for us of course. I do feel like Reggie Steel could be kind of a win con for us almost but it makes it tougher because of the wheezing which can taunt Reggie Steel and kind of shut us down prevent us from being able to to do all the things that we want to do. Cinderace is always going to be useful as a lead. We've got ways to deal with the Dragapult if we did see that or the Whimsicott potentially as well but I think for most parts it's going to be wheezing and Reggie Giggis the sash helps Cinderace out a bunch as well. Just let's remind ourselves of the moveset. So no fighting stab there which makes it a little bit more tricky and I just need to check the Grimm Snow. I don't think we've got Vacar but we do have Thunder Wave which does help but again are we going to be able to get the Thunder Wave off into the Reggie Giggis? I don't feel like it's going to be a possibility so maybe something like Reggie Steel I think Thunderace is going to be good and probably let's go with Finney to finish off with. So yeah, it's a tricky team tricky team to deal with always going to be tricky depending on the tools that you've got to deal with Reggie Giggis wheezing sometimes going to be one of those teams where you're like well my matchup against that isn't great but I've got a good matchup against the majority of other big teams in the format so you can't forgo that one and then when you come up against it as long as you've got a game plan to kind of approach it you're not in the worst situation but it does make it difficult and to kind of approach these matchups for sure okay well we've got Oshifu and we've got Windsor Cod and let's just do the old thing it is fine dark type just to just to make sure and now we could go for Max Airstream into the Oshifu it's likely going to attack into Reggie Steel I think that's a big thing if you're not going with a Reggie Giggis wheezing mode I think you go after the the Reggie this the Steel soon as you can whereas we could go for Bounce Bounce or we could go for Max Airstream or we could switch into something like Finney here which might not be a bad play and and just go for an iron defense yeah let's try and get the iron defense up I mean we're probably going to take a hefty chunk of damage and we're in a good position to get some damage onto Oshifu as well whereas we could have potentially switch to the Reggie Steel out to tap of Finney and probably Max with with Cinderace and went down that route there but Elsie and switcheroo from this a Jack button onto tap of Finney they got the weakness policy and suck a punch okay what were they trying to suck a punch don't know well well well well we got the eject button anyway so that's that's that's alright that's alright you don't mind that too much just go for a moonblast into Oshifu we'll go for another iron defense and we max here and go for the flash cannon potentially into if we could double up into Oshifu to be honest and stop boosting our defenses I think that's not a bad idea we're going down the the Reggie Steel route once again I was kind of hoping that we would get to see the the weakness policy tap of Finney but it doesn't appear as though we're going to be able to get to see that in this episode since it's been stolen from that pesky little Whimsical alright well we're pulling the trigger nice and early we've got that iron defense boost which is going to help us out massively we should be able to remove the Oshifu from the field this turn pending if it's sashed on it you've got to assume it is sashed there's no way you're looking to suck a punch with a band but you can see the player that they went for the last turn I mean the eject button and then the suck a punch gets rid of the max Cinderella so it was a good job that we didn't we didn't go for the max there close combat doing absolutely nothing nothing to this tank we've got on the field ready steals just so dumb it's like it's so good but when you get that iron defense up it's such a good Pokemon and then you sit something like tapping Finney next to it especially if you've got like the combine variant of Finney which I really do like that combination and then you can just get the defense boost for Finney and calm mind up next to it and it's just so difficult to take that combination this boat position and deal with it you know but we may see something from my opponent come in and maybe disrupt that a little bit but I think that the Whimsicott's a nice target next after just protecting here Dragapult Draggy okay Dragapult do we go for the the the old Blizzard here that would be I think we go for Blizzard the only issue would be like the only issue I could see now is that my opponent goes this would be a smart player I think I think eject button the weakness policy onto the Dragapult Max hope that we hit it and then they they get there and their weakness policy activated I think that's what they're going to do you know I really do I really do so we're just going to play it a bit safe I'm just thinking about that this okay they don't do that that I would have done that I would have done this in this situation I would have Max the Dragapult eject button like tricked on switch your route on the eject button knowing that the tap of Finney is going to moonblast us you know and get that that weakness policy boost to get rid of the tap of Finney but I guess you don't need to when you've got the eject button there can we get in it's going to be a good Pokemon Cinderace with the Sash as well and Sucker Punch to deal with that Dragapult and the defense boost from the the Reggie Reggie Steals Max Steel Spike you're going to be useful for that that Cinderace we are going to take down the Elfin which is the Whims of Cat sure that's German though the Whims of Cup version the German version of Whims of Cup that makes sense I always think the German translations are the best like I always I always think that like this this portal is Tyranitar isn't it and Clack Crack is Garchomp pretty sure what's Hitmontop as well Hitmontop has got a a weird one but it's cool as well at the same time you know right well the Rotom the Rotom coming in doesn't help us out too much I mean we just we don't want to protect because the Phantom Force just break that let's get Finney back on the field just for now and you steals but the problem is leaving that blinking Rotom alone means that it could nasty plot here and that could get a bit dicey for us for sure we want to try and get a bit of damage onto it but at the same time we want to try and get hmm now we need we need now we'll go for the Seals bike into the Dragon put get that defense boost up again then got the body press where we can actually just chase down the Rotom after that I do worry about the nasty plot that that complicates things a little bit for us for sure but we're going to see Max not going to see that nasty plot come out and we can potentially bait the Rotom the next turn and by switching into thunder because go by the Max landing unless you just want to concentrate super heavy down on something like a Reggie steel here which just brushes off that Phantom force from the em oh we should have switched in we should have switched in such a switched in the thunderous that would have worked out really good I thought we more likely see the the Max guys I get the rain up I think it would have been a bit more reliable but no harm done we lose the Finny which is a little bit unfortunate but we've got the Sash on on Cinder which which definitely helps us out a bunch so we can come in circle punch the Dragon pole and just body press that the good old wrote him there the thing is with the the guys are the last turn it it boosts you up so you're going to be hitting the Reggie steel a lot harder whereas now it's going to take two turns to get you in that position and we can definitely protect on that second turn if the rain is up you know with a sucker punch then we're sitting in a great spot where we can just thunder us I'll easily beat the Rotom as long as you can get just some damage onto it you know I'm not worried about Reggie still getting knocked out by Rotom it's not nicely pop bluested it's not knocking us out on one hit no chance and get the sucker punch with Cinder race and we still got the Sash on Cinder as well so and at least that gives us a bit of room which is a nice option you know you don't always see the Sash on it normally life or something else so and there's the guys of this turn where we gone into the Reggie still got to be got to be yeah and students in fact damage see this is what I mean I think if the rain was up already you know it would be it would be doing considerable a considerable amount more damage whereas now we've got the potential just protect and potentially get enough health to take maybe do we just sucker punch is our best option against the Rotom here so just protect yeah maybe even another body press when it's not maxed so they're in their last turn of their max now so just protect this turn we don't want to get taken down by a max guys which potentially will take us down now with that rain boost sucker punch doing a little bit of chip we're going to see it yeah there's a citrus but we like I say don't really worry now because thunder is coming in just the one thunderbolt life or boosted would be enough to to deal with it yeah and let's see what we can do can we get another body press off you've always got to think as well you know hydro pump hasn't got the best accuracy if they miss a hydro pump then they're in then they're in big trouble but we've got no reason to switch thunder us in right now you know like center is still got its sash intact sucker punch might fill but I mean if they go for a nasty plot they're going to take a body punch at body pressing and should pick up the knockout very good game to my opponent hopefully you've enjoyed today's games and what we'll do now we'll hop over and we'll just remind you of today's rental code okay friends here is today's rental code again and big shout out to t bv 4054 the rental code and I've had a really good time with it so I hope you've enjoyed today's battles and it's been really nice seeing it's been a bit of the Reggie steel show but I mean we've got to see a bit of the thunderous as well the type of Finney and the cinder the team do their thing obviously Grimstone all had a brief appearance and we had that a little bit of an iffy game one I will say we got a bit fortunate with a high horse power mess so bit unfortunate for my opponent there but all in all today's episode I feel like it's been a good one and it's been really great featuring this amazing team like I mentioned at the start if you've got rental codes that you'd like to see featured on the channel do throw them down in the comment section below and I'll try and get through for tuning into today's episode hope you've enjoyed it hope it's been entertaining and educational in the same way and some sort of frame on the ladder today but really enjoying the ladder at the minute and enjoying all these rental teams so hopefully you are as well look forward to catching up with you all again very soon take care of yourselves friends and I'll catch you on the next episode so until then friends


Over the last several weeks, there's been a buildup of frustration and concern around the organization when you talk about from players, coaching staff, and even organizationally on him, his availability, his level of play, and even his passion and how much he has of that, his intensity of that, to get on the floor and compete at a high level. He has the back surgery from May. He did get his knee drained about a week, about two weeks ago. So listen, there are some physical attributes and we saw he had a dunk last night. He has a ways to go physically as well, but I think there's definitely some stuff that he can control that Nets, whether it's organizationally, teammates are all showing and that's something that has stood out that will be an issue for the Nets moving forward.


The great things about any motorsport team is the camaraderie and the crew work that goes on here and the GTI racing team has involvement from the MTA, have Ben Kolow from the MTA here and of course Sharon Gunson doing a fabulous job. Talk us through your involvement with this race team. Good morning Dean, yes with the MTA we aim to offer the apprentices a chance to be able to have a go at working on the team, being part of a great group and well as you can see here today we've got three apprentices working on the team on a bit of a repair before we go back into stage.  It's a great opportunity for them to get real life experience in a motorsport team which is a different environment, different pressures than what you see in a normal workshop isn't it? Absolutely, we've got time restraints like you wouldn't believe. We've got 15 minutes to change a driveshaft on a car and we've got the racer here ready to go, waiting eagerly. But Sharon, when you are driving and you've got the team behind you, it's fabulous to know you've got the best people on deck to be able to try and help you through this situation. You can concentrate on your job and you've got to cast the thousands, lots of logistics, but it is a great part of why you enjoy Targa isn't it? Yeah absolutely and that is the important thing. We can sit in car, drive, not worry about any mechanical issues, I just come in and say I need this, this, this and it's done. So it allows us to do driving technically fast, whatever we want to do, but yeah it's absolutely fantastic to know when I've got this crew behind me and they've done a magnificent job, like that car has been off a few times for brake bleeds this morning, now a driveshaft, so yeah they're certainly owning their keep today. And you're not the only car, we've got one, two, three, four, another six bays ready to go, but I think it's fabulous, like I said, the experience that everybody's getting here and a great part of the camaraderie, like we talk about with Targa West. So congratulations to the MTA and also to GTI Racing, awesome job. Thanks Steve. Thanks Steve.


Everyone, and welcome. This is Melissa Arma with the stock swash and reviewing Tesla. Tesla was the biggest option of the week last week. So I had called two trades in it. But I want to specifically talk about the one trade that I called that wasn't going anywhere. Wasn't going anywhere. It was flat, up a little, down. And then it dropped the day before the expiration. And this is really something that is probably going to continue to happen, meaning things fake a certain direction. And then they go in the direction you think they're going to go to begin with anyways, which is me. Again, I knew Tesla was lower. I talked about it, talked about it, talked about it. Thursday morning, which was the ninth. So I called the 215 putts earlier in the week. They didn't go until the Thursday. And you still actually could have been in them Friday. Friday's low was 205 and changed. But I got out of them Thursday. But you could have still been in them Friday, actually. Anyways, the trade went here. Was it too late? No, it wasn't too late. It was a beautiful trade. Again, low on this day was 206 and changed. But it ended up going almost 10 points for the strike on the very last day and almost here even. But this was where all the money was. So it was momentum. So a lot of people, when they're doing options, again, I had called the 215 putts in Tesla. But a lot of people, when they're doing options, they are worried about things that they shouldn't be worried about. So when that happens, either A, they don't know how to take the option. They're unsure of the direction, whether to do a call or put. Or they are oversized, oversized in the trade. And really, that's because they're probably really unsure of themselves, too. So the best thing that you can do is to make money in options. Again, this is the way that I play it. I'm looking to trade the momentum. So I'm waiting for the momentum to come in. The momentum could come in the last day. While I prefer every trade I take to go the second that I take it, that's not always a case. And the point I was trying to get at earlier was this is what you could see a lot more of going into the end of this year and even in 2024. Because you better be sure of yourself when you're taking a trade. And if you're not, again, you follow me. Because I'm sure of myself all the time when I take something. Again, win or lose, I'm sure of myself. It doesn't mean they never try to take work. Some trades I take lose. But far more trades that I take are winners than losers. And again, I'm sure of myself because I've raided the gap using my 26-point rating system. But again, I was so sure about Tesla. I talked about it every single day last week I talked about it. And then on Thursday morning, I said, this is it. Today is a day. Tesla's going to fall off a cliff. Tesla's going to tank. Today, today, today, I set it in the room in the morning before the open. And then in the morning, and then it tanked. And then it absolutely tanked. And it went on Thursday into Friday. But this is really what you're going to see into 2024. You're going to see many, many things fake out or look like they're going to do something or not or whatever the case may be. Or you may be waiting on a trade to go. And then whoop. And then it goes in your direction or goes against you. Like people are going long this today. Again, we'll see where this goes today. Again, this is a lot depending on the market today. Let's just see where we are right now at 12.30. But volatility is good with options. And too many people, when they're trading options, are not focused enough on momentum. When I take an options trade, I'm not trying to make $0.05, $0.10, $0.25. Unless I paint $0.50 and I want to make 50%. And I want to get out and make $0.25. Typically, I'm trading options to make $5, $10, a move similar to Tessa, where I'll buy a $2.15 put and I'm looking to get it to $2.10, $2.08, $2.05. So I want big moves. I want momentum. That's how you can make money trading options. Yes, you have to get in the right direction. And yes, you have to get the timing right. But that's the case in every trade. That's the case in every trade. The whole reason that people love to trade options with me is because I'm calling such huge trades like Tessa where you get this massive amount of momentum that comes in. That's all the profit. That's all the money. That trade was up prior to that day, if you'd gotten out of it one of the earlier days. But it wasn't where the big trade was. The big trade was the sell-off that happened. Again, we were in puts on the Thursday and then the drop into Friday. But again, I got on the Thursday. I'm still getting here with the market. The market looks dead right now. There's just no volume in this market today. Anyways, this was the biggest trade last week on the options news. I know we had a light week. We had a light week, but just, again, you can make money trading options if you trade momentum. If you know how to find momentum and spot momentum. So people say, how do you know how to do options? I'm using my same system. It's a golden gap system. That's how I'm making the picks like Tessa. That's how I knew Tessa would drop. And I knew it would do it soon. Soon meaning last week in a couple of days. Soon, soon means fast. May not be the day that I call it even though I love when that happens. But soon is soon, not 10 years from now or five weeks from now or next year in 2024. Again, one of the reasons I don't do long-term options, which is called leaps, is because you pay up so much for those. And if you can't predict efficiently that somebody's gonna drop quickly, how can you predict where it's gonna be six months from now? Again, I've used this analogy all the time where I say you could probably tell me what you're gonna make for dinner tonight.  If I ask you what time you're gonna eat dinner next Monday and what are you gonna make for dinner next Monday, you have no idea. So it's a lot easier to determine where something's gonna go soon within one week than it is farther out. When there's many other variables, many other things could affect the overall market or the stock that you're in. So anyways, Tessa was the biggest option last week. It was volatile because, again, it fainted like it was higher and then it fell off a cliff. It was a great call. It was a great call, so. We'll see what happens with this this week. Again, this isn't the mercy of the market right now here today, but you can even see how low the volume is in the market. That's Tesla, that's the Qs. Look at that. There's more volume in Tesla right now than there is in the overall market. This market is dead, dead as a doornail today. But we'll see where it goes tomorrow. A big number out tomorrow morning. If your interest is inside enough for the gap option as a newsletter and getting some nice option calls, beautiful calls, email me at Melissa at thestockswish.com. No prerequisites, I have a six month subscription, a 12 month subscription, and no trials. Go to the website and check it out. Thanks everybody, have a great day.


So you are here in Agile India 2012, and you are back again in 2013. So what's been your reactions for the current conference, and how do you compare with the previous? Well, one thing that has maintained from last year to this year is I've been very impressed with the quality of the questions. People are really thinking deeply about the presentations, and I've received from very insightful questions on the presentations that I've given and also the ones that I've been in. So that's something that I was glad to see continued. It speaks a lot to the audience that is being drawn to this conference. And I have to hand it to Noresh and the rest of the program committee. This year's program is very, very strong. I've heard from multiple people. I don't know what I'm going to go to this time. There's just too many things that are in parallel. So this is a really strong program, and I hope that that's something that can get out into the community here in India that this is the quality of content that is being generated in the Agile community here in India and for India. And hopefully that will lead to even greater attendance next year. If you were to take one big highlight for you, being in this conference? One big highlight. I really enjoyed Neil's keynote this morning. And in particular, I've always been a big fan of Richard Feynman. And I never really expected to see the life of Richard Feynman, the scientists, weaving through a talk at Agile India. That was pretty awesome. Yes, so I'd say that's one highlight. But I think another highlight for me, going back to what I said before, the interaction, the level of conversations, not just the questions in the sessions, but the people I've had a chance to meet and talk to, this is a fantastic group of people, and I think it speaks quite highly of the way the Agile community is developing and has developed here in India. The other question is obviously you travel a lot, and you've been to a lot of conferences across the globe. So if you have to compare this, I know it may not be fair in comparison, but then where would you rate this? Well, I make a big deal about the questions and the conversations, and of course the kind of conversations varies from conference to conference. When you've got a very technical conference, you've got people seriously geeking out on what's the latest, jet optimization or something like that. And in a conference like this, which is as much process as technology and tools, you get different kinds of conversations. But the quality of the conversations here, the quality of the questions, I think rivals many of the conferences that I attend across the globe. So we made small changes in terms of last year we had seven parallel tracks running. So this time we consciously segregated between management and technical. So is that something to vibe with you? I think that that is going to increase the ability of certain kinds of practitioners and certain kinds of roles to attend the conference because it's a bit easier to make the case that this is a conference that's dedicated to what it is that I do, whether that be iteration management or scrum master versus a developer or a tester. I'm a little bit concerned about it though because one of the things that we try to do on an agile team is blur the boundaries between the roles. And so the segregation I think can have a bit of a detrimental effect on the way the various roles learn to understand each other's problems. One of the big issues I think is when you get conflicts between roles is that role number one doesn't really understand why role number two really cares about this. And so I think having a bit more interleaving is useful. But practically speaking there aren't too many developers who are going to show up to a session on agile project management if there's a technical session available to them. So I think I'm probably being a little bit too concerned but maybe if there's a way to have some kind of interaction maybe it be a closing keynote on the first night or something where you can perhaps get a little more mingling of the groups. Maybe an overlap. Yeah, that's what I thought because that blurring of the lines is critical in that sense. I find that when I deal with architects and developers when developers start to understand why it is architects care about things they start to be a little more comfortable and vice versa and I think we can get the same kind of us versus them when you start thinking the management of agile project versus the doing of agile projects when in fact on an agile project everybody is doing something. So one final question. So would you recommend people across the globe wherever you travel to attend agile India conference if you were to do next year? Yes, I would. Thank you very much. Thank you.