Good morning. I'm Tony Irwin. I guess I was given a little bit of an intro earlier, but I'm going to, I'm the lead architect for the Blue Mix UI, and I'm going to talk about our team's journey from monolith to microservices during this half hour. We'll talk a little bit about the origins of the Blue Mix UI. We'll talk about some of the problems we had with our original monolithic implementation. We'll talk about how microservices helped deal with some of these demons, I guess, and then some new problems that occurred with our microservice architecture. There's already some mention of added complexity and things when you go to microservices. The Blue Mix UI serves as the front-end to Blue Mix, which is IBM's open cloud offering, which features Cloud Foundry as a big part of that. It lets users create and manage Cloud Foundry resources, containers, virtual servers, accounts, billing usage, et cetera. It runs on top of the Blue Mix Paz layer, which is Cloud Foundry. It started as a single-page application. It's the intent to provide a desktop-like experience in the browser, so it's loading all HTML in one page, using JavaScript to manipulate the DOM and all that. The stack was kind of the state-of-the-art, at least in IBM. We were using the Dojo framework on the front-end, so Dojo front-end, single Java server back-end, at least in IBM. At the time, three or four years ago, it was kind of the common stack, but we kind of quickly figured out that it's not really where we wanted to go for our cloud environment. This is just a few random pages from the Blue Mix UI, so it's a fairly big application with a lot of different pages. This is just a very simple picture of our original monolithic architecture. Basically, at the top, the Blue Mix UI, which is the client in this case, which is the browser. Just some different components we had, like the home page and catalog and dashboard. Really just kind of showing all that logic was, at least the UI logic was pretty much loaded onto the front-end. The back-end running in Cloud Foundry was the single Java server, and then the monolith, the Java monolith, would talk to the various back-end APIs like Cloud Foundry, UAA, billing authentication, et cetera. This led to several problems. One was performance. Dojo has a very large Java strip framework, so it was kind of floating this heavyweight Java strip. It kind of led to some bottlenecks. Since it was a single-page application as well, there was really no data we included from the server in the initial payload, so it was all AJAX requests, which just again kind of bogged things down. It's also difficult to integrate code from other teams, and this will be a theme as I get deeper into the talk, but we wanted to make a flexible framework, because at IBM, I've got my core team, but there's 20 other teams that want to also kind of be part of this console framework, and asking everyone to somehow write a Dojo plug-in to get into what was our monolithic app really wasn't practical. Some of this, if you dealt with microservices, you already know, but with a monolith, when you have an update, you have to push the whole thing as opposed to being able to push a smaller part of the system, so that was an issue. Poor SEO, so search engine optimization was poor, because as I mentioned, the HTML payload really didn't include any searchable data, and the last point there, and I don't know how many people in the room have ever used Dojo, but at the time, we had some new hires come in, and they had wanted nothing to do with it, so rightfully so wanted to move to a little bit more modern, lighter weight infrastructure. So we decided to go to microservices, and these are some of the advantages or things we thought would help us deal with some of the problems with our monolith. You know, one issue we had is that we were a live production product. We wanted to totally re-architect it to microservices, but obviously that takes time, especially when you've got pressures to continue to add new function as well. So we went down the path that we could slowly break this monolith down into microservices, kind of continue down this path of a lighter weight stack, but keeping the core monolithic aspect of the product alive as we broke things apart. We tried to go for smaller services that were optimized for speed and page size, so we went with lighter UI frameworks and services that were focused on a smaller subset of things than the monolith as a whole. Microservices also help increase developer productivity. There's less chance of breaking other parts of the product, because you can deploy individual microservices. Loosely coupled services can deploy at their own schedule, so I kind of alluded to this before, that we have all these other teams that want to plug in. They don't want to wait for one big push. They want to update as they have changes. Microservices is a little bit fuzzy. Not really microservices that allowed us to improve our SEO, but just as part of this re-architecture. We started doing more server-side templating, including some more content in the page, in individual pages rather than having one big monolithic single-page app. So this had more content than that Google and other search engines could crawl. I'll get into this a little bit deeper shortly as well, but as the core team worked and we had other teams plugging in, we wanted to make it look like it was all part of one product. So we used some microservice composition so that we could all share some common UI elements and things like that. So this diagram basically shows our microservice pattern. Our typical UI microservice is going to be implemented this way. Again, we have the Bluemix UI client at the top. We're all the HTML, CSS, JavaScript is. The JavaScript may be vanilla, could be Polymer, React, Angular. We've been kind of focusing on React more often than not within our product. I always forget to talk about the proxy piece of this, the gray box there. The proxy is really what makes the microservice system come together because as requests for a particular path come in, the proxy decides what microservice to send the request to. So this Node.js microservice in the middle, the green box might be the catalog or catalog microservice, for example. So when slash catalog comes in, the request is forwarded on to this microservice. So as I alluded to, all of our new microservices are in Node.js. We're using Dust.js for server-side templating. A UI microservice needs to call our common header microservice, which this was alluded to before. It provides an API to get the header at the top of the page so that all pages can at least share that piece. And these microservices may also call other API microservices or certainly the various back-end APIs. We're also using Redis for shared session storage so you authenticate and then these UI microservices can grab tokens out of the session. And this is a visual depiction of how we compose the pages. So the green box is just a microservice. It does invoke common, and you see the strip at the top is basically what we call the header. So with the server-side templating, the microservice can take that HTML snippet, put it into its overall HTML payload and serve that, and then you've got a header with user information in it, as well as whatever content the page wants to provide. So this whole process for us started a couple years ago, really, and we feel like we're, and I'll show more, kind of the stages of our progression. But we're pretty much where we want to be, still not, you never quite get everything exactly the way you want it to be. But so back in February of 2015 was the first release we had that had any microservices at all. And as I mentioned before, we wanted to start kind of slowly. We started with Home and Solutions. We're kind of two smaller pieces of the monolith. We thought, well, let's just make those microservices to start with. So you can kind of see, so those green boxes moved out of the top, became microservices on the back end. The Java, the Bluemix UI server, which is our Java app, still running there. We've got the proxy, which I mentioned, which is routing requests to the various apps as needed. It's all deployed to Cloud Foundry. I was at a conference in Shanghai a couple weeks ago, too. And that was more of an academic conference. So folks are very interested in research around how you break a monolith down into microservices. And my view is it's more of a black art than a science at this point. We started with a couple smaller components and slowly, things that seem to logically kind of go together. But some of the academics of the conference were like, well, could you assign a score to your architecture and to rate how good it is? No one had an answer to that at that conference. I think that's a very difficult thing. Beauty is in the eye of the beholder, I think, in some of these microservice breakdowns. So as you know, there's lots of different ways to slice and dice. Phase two was about a year later.  The account stuff was still kind of mostly on the client side. You see a lot more green boxes as that UI logic moved down into separate microservices. Our Java server is still there, but it's doing less and less. It's just, by this point, it's just serving some APIs that we hadn't yet ported to Node. And our end goal is, you know, to get rid of the Java server. We do technically still have it there. We would like to, you know, just for team consistency to be all on Node.js. So that's something we still want to get rid of. But we're essentially at this point now, except for some remnants of the Java server laying around. I mentioned, you know, plugins and other teams wanting to be able to, you know, plug in, be part of the console, and deploy on their own schedule. And this diagram is intended to show that. So we talked about how the proxy routes requests to our individual microservices. Other teams here, the yellow boxes on the, I guess it's my left, or whatever. So we've got, like, Watson, IOT, OpenWisk, various components that other teams own, you know, it's like slash Watson would route all requests to the Watson endpoint that they've provided. Now, that may be in a microservice on its own right, or maybe a proxy to other microservices. We really don't care. We've got about 25, I think, core microservices or so. And with all of our, you know, I think, I guess this slide says 15 teams. I think it's probably actually closer to 20 now teams that have plugged in within IBM to this infrastructure.  So, you know, it's a very loosely coupled system, you know, maybe 100 microservices when you add up all of the teams involved. So when you move to microservices, you know, I guess the saying is there's no free lunch, right? So there's always, you know, sometimes you trade one set of problems for another. I mean, it has been a good move for us, but, you know, it does bring some added cost. So there's more moving parts, you know, I mentioned we have 25, 30 microservices plus all the plug-ins. So there's, you know, more moving parts, more complexity. The build pipeline becomes all the more important, you know, to be able to orchestrate deploying that many microservices. Federated status, monitoring, I'll have another slide that will go into that in more detail. But I think this was something we really underestimated when we started, how important it is when you have microservices, you know, all these loosely coupled things, be able to monitor, you know, problem comes at 2 a.m., how do you figure out what went wrong, you know, or if you have a performance bottleneck, how do you figure out what component is causing that issue? So we've invested a fair amount into monitoring, and we'll talk a little bit more about that briefly. The granularity of microservices versus memory allocation. So as I mentioned, there's more art than science. I think when you're breaking down a monolith into microservices, but when you're deploying, you know, one consideration, though, I've heard people point the term nano services. We did not want to get to the point where we've got, you know, a thousand different microservices, you know, so we've got more than 25 to 30. But if you look at, like, in Cloud Foundry, as you know, you have to allocate memory per instance up front. So we did notice a significant increase in memory usage by doing this. So our Java app, our single Java app was, you know, three instances of two gigabytes apiece. So we were using roughly six gigabytes allocated to those Java instances with our microservice system.   So that's, you know, far more memory than the monolith took. There were some issues just trying to, as I mentioned, we needed to keep that monolith running. So we had some issues just, you know, trying to have some seamless navigation between the single-page app and the individual pages. Blue-green deployments. There's, you know, doing a blue-green deployment in Cloud Foundry is easy. You know, with one app, when you have 30, what do you do? We ended up doing a blue-green deployment at the proxy layer. So we deploy, you know, one set of 30 microservices and another set, and we would do blue-green at the proxy layer. Promoting uniformity and consistency, that this is, you know, if something keeps me up at night, sometimes this is at IBM. We want, you know, these individual teams to be able to plug in and have freedom to deploy on schedules and everything. But if you want to try to, I have a product with a consistent UI experience, you know, what sort of policing do you put in place and quality standards when you've got other teams plugging in? I'm not sure we've totally nailed that one down yet, but that is a concern in our case. And geo-load balancing and failover, not really required to do microservices, but, you know, we had invested all the time, and I have another slide dedicated to this shortly, but we had, you know, invested all the time in trying to get HA and resiliency for our microservice system. But, you know, then if you're running in just one data center, that data center goes down. There's not much you can do. So we did undertake some efforts to be able to load balance between different Cloud Foundry deployments. So I mentioned monitoring, just a little bit more detail here. Lots of things can go wrong when you've got this many microservices, and, you know, they're all talking to various back-end APIs that can have problems. Cloud Foundry can have problems. There can be networking issues. You know, how do you figure out what's wrong? So we did build a monitoring system. You know, some needed metrics or metrics that have helped us along the way. So for all of our microservices, we have all inbound and outbound HTTP requests, so with response times and error codes, and we've got, we all, we pop it into Grafana. It's a little example of Grafana chart at the bottom.  Red would indicate 500 errors here.  We also cared about memory usage and CPU usage and uptime for every microservice. So, you know, we keep track of app crashes, all those kinds of things. So if your app is crashing, your quality of service is probably going to be impacted. You know, general health of ourselves and our dependencies. As I mentioned before, as an example, we use Redis for shared session storage. So we do want to, so one of the things we do is keep track of how healthy our Redis system is. You know, if that starts to have issues, that's something we need to resolve quickly. And aside from kind of the real monitoring of real data, we do also run some site speed I.O. We use site speed I.O. to generate some synthetic page loads so we can look at front-end performance as well. This slide, I alluded to the global console that we have before or that we just recently released. We used to have, so we deploy in four, we have four public cloud foundry deployments at IBM as part of LUMIX to Dallas, London, Sydney, and Frankfurt. We used to have individual URLs for each of those regions. These were very separate deployments. We, with the global console, as we called it, we have one URL now, consolebloomix.net. We do have a region selector, so if you wanted to create cloud foundry apps in Frankfurt or Sydney, we still have a switcher for that. But instead of doing a whole page reload with a new URL, it's more of a filter in place. So we use, I haven't really talked about Akamai, but Akamai, we use Akamai here in our picture, but the important part for load balancing is that it does a DNS lookup against a dime load balancer which basically has all the IP addresses of our different cloud foundry deployments. So it's going to return the one, the IP address for the deployment that is closest to you geographically. So if I'm in Sydney, hopefully I would get the UI server from the Sydney data center rather than the US data center. So that's an improvement in performance right there. But the other thing is it looks for, it returns the nearest healthy data center. So if you're in Sydney, you would normally go to the Sydney data center. If that data center goes down, you would be routed to the next closest one, which maybe Frankfurt, say. So you don't notice any interruption in service, and we can go figure out what's wrong in Austin. Or in, not Austin, Australia. Yeah, and that's basically that. So the odds of all of four regions being down at once are pretty rare compared certainly to one region being down. And that kind of brings us to the end. Any, I think we've got time for questions? Yeah, there's two. That's a good question. I don't know that we've been, I think we've probably have built up some technical debt in terms of some dead code being in the Java piece. I think in some cases as we sort of ported things, we were probably better about deleting that code than other times. So this is going to be a, we do have a goal, as I mentioned, to knock out that Java server eventually. So I think we will have a little bit of a challenge just to, we'll be able to see what API calls we make into it so we'll know what's still being used. But as you're in sort of a porting exercise, there'll be pieces of Java code that we don't want to port at this point because they're not, maybe they're already been ported or no longer used. So I don't know if that answers your question. The proxy that you mentioned, what does that exactly do over just routing to a certain URL in your internal? Really nothing else. We tried to keep that layer very, it's actually a Node.js app in Cloud Foundry. We probably will be moving to Engine X, but there's really no intelligence other than looking at the host or the path and routing to the right microserver. So why don't you use the routing option in Cloud Foundry, the default? Well, I think we started this before that was even an option. So it's probably one of the big reasons. Yeah, so I've heard arguments that UIs need to be monoliths because you want to guarantee a seamless user experience between the different UI components. How did your UI design process change as you split up your UI into really separate microservices? I don't think from a user experience design perspective, I don't think it changed a whole lot. I mean we do have more times where you click on a button and you get a full page reload as opposed to just some DOM updates occurring, but I don't think that really impacted our design approach that much. Now there are cases where the UI designers will, I guess, propose something that doesn't necessarily fit real well with just how our code is broken up. So that could be a challenge, but I guess I've typically thought, well, let's not make an architectural decision that we had made at one point impact our user experience too much. So if there's some swizzling we need to do or extension points or whatever to make some of those things happen, then we need to be open to that. You mentioned that you do blue-green deployments via the proxy, so you are deploying all of your microservices, blue-green, even if you only changed one, right? That's right. That's a very astute observation, so that is. We've taken some steps to improve that, so we do have the ability to swap in individual microservices, but it's not as good as it could be. Yeah, so that's a shortcoming we have, because I think we've gotten smarter about at least being able to update the proxy config of our own deck deployment to point at a new version of a microservice, so we may still be doing a blue-green deployment at the proxy, but we haven't actually deployed all new apps to do that. How many times do you deploy? How many times? Yeah, I wouldn't say we're, I know some people like to deploy multiple times a day. We're more maybe a couple times a week, typically. I guess there's a few reasons for that. One is that just when you're making UI updates, you usually do need some, we have automated tests and stuff, but sometimes you still need that visual inspection to make sure nothing looks too eschewed, so there is some testing overhead and stuff when you're doing UI. Thank you. The room goes way back there. I can barely see you. Hi there. So obviously individual teams will have responsibility for testing their own microservices, but in terms of the product as a whole, where's that responsibility lie and what sort of challenges would you have experienced? I'm sorry, in terms of testing? Yeah, in terms of testing the whole product as a whole, I mean, individual teams will have responsibility for their own pieces, but who owns the overall piece? Right, yeah, and that's a real challenge. I mean, so I mentioned that we have automated tests, so each microservice owner is certainly responsible for having a nice automated set of unit tests. It's a little bit more challenging when you then want to make test end-to-end flows, and we do have some automated testing around that, you know, testing the, you know, if you transition from one, a page would, you know, serve from one microservice transitioning to another. I mean, we do have some tests around that, but those are typically stored separately from the microservices, and I think we still need to do a better job there. We have a couple QA folks that would love it if we required a little bit less manual testing than we do today. Hey, my question was you compared the Java memory footprint and the microservices footprint. Is that around the same functionality included in these two types, or was there also functionality-wise a difference? No, the functionality was, I mean, we probably added some new function, but by and large, it was, you know, equivalent functionality. Okay, thanks. You're getting a workout. My question is you showed the different data centers of the installation. How did you manage to synchronize the state between the data and the data centers? That's a very good question. So, our UI code doesn't really store a lot of state. The, you know, we really rely on back-end APIs. So, just as an example, you know, the UI will allow you to create a Cloud Foundry application. That state is maintained in the Cloud Foundry, you know, by the API controller right, and all of its back-end. The one thing we do store is like the user token in the Redis session. So, if we do do a failover, we do have to do a quick refresh of, we've got some cookies and things, we can do a quick refresh of the token, and we end up, because our Redis deployments are separate. So, Redis is used for that in the back-end. Exactly. Yeah, yeah. So, we don't necessarily copy everything from a Redis here to a Redis there, but since we don't store very much in there to start with, you know, we just get the new token and put it in the Redis when we failover occurs. Thanks. Monolith, yeah, they tend to have an exciting internal structure as well, right? There might be some layering going on and stuff like that. So, in your case, the decomposition, did it just fall into clean top-to-bottom slices, or was there also some sort of downstream services happening, and if so, how did you cope with that? Yeah, that's a good question. I mean, I think, you know, because, you know, I showed the screenshot earlier of the different kind of sections of our UI, and typically the APIs and things provided by our... So, our monolith didn't really provide a whole lot of UI. It just kind of served, you know, all the JavaScript and HTML, and, you know, we had to make back-end API calls. So, the Java server ended up becoming just an API server. Now, some of the APIs tended to be kind of, you know, so an API for Cloud Foundry, you know, that was doing some Cloud Foundry manipulation like for creating apps, was probably only used by our catalog microservice. So, we did sort of look at the various pieces of the UI, catalog, dashboard, accounts and billing, and those were roughly, you know, some of the pieces in our monolithic code as well. So, I guess, you know, that was somewhat natural. I can't say we went and looked at the, you know, the class hierarchy of our Java app and used that to sort of drive the microservices we broke down. They were probably bigger components than individual Java classes and things like that. I don't know if that answers the question. Then thanks, Tony. Good talk. Good questions, and we ran out of time, so we have to switch over to this one. All right. Thank you.


In the pool tonight down in Brainerd they were hosting the Otters of Fergus Falls but the Otters didn't live up to their name. In the 200 I.M. the Warriors take first in seconds led by Andy Dillon finishing in just over two minutes and 12 seconds. Then the Sprinters hit the water as Brainerd's Dillon Paulson takes first by just 8 tenths of a second and in diving Isaac Hurlick stole the show with this dive receiving an average score of 7.5 that is poetry in motion. The Warriors take the win tonight 97 to 66. If you enjoyed this segment of Lakeland news please consider making a tax deductible contribution to Lakeland PBS.


Thanks for joining me today. We're here today to talk about volume, specifically volume of a rectangular box. Now, you might remember, if you think back to your middle school years, joining us for the box problem enrichment, in which each one of you would have had an 8 1⁄2 by 11 piece of paper, and you would have made boxes of different sizes. So here's an 8 1⁄2 by 11 piece of paper. And if you did do this before, you might remember cutting out from that piece of paper squares from the corners of different sizes. What we usually have our students do when they do this with us is they'll cut out squares of maybe a teeny tiny one that's 1⁄2 on a side, up to 4 inches on a side. And we talk then about what do we notice? What are the patterns? What effect does the size of that square that you cut out have on the volume of a box? So I have a computer animation just to kind of put you in the right frame of mind. In terms of what we're talking about here. All right, so the first one is the blue box. And if you take a look at that, that looks like maybe that's one that was created by cutting out a square of just a half inch, maybe an inch on a side. And you can see how shallow it is. Almost just like a little tray. The green one looks like those squares were a little bit bigger, and maybe 1⁄2 inches, 2 inches on a side perhaps. And the last one, the yellow one, that has a much bigger square that was cut out. And you can see how, even though they all started out, the same size piece of paper or construction paper, whatever we used, that in the end, they look very different from each other. So back then, what you would have done was you would have investigated what the length, width, and height of each of those boxes were. The height of the box always comes from the size of that square that you cut out. And then based upon that, you can easily calculate the length and the width. Of course, then volume is length times width times height. What we're here today to talk about, though, is the algebraic point of view. Because now that you're older and you've learned algebra, you can write equations for these things. So we're going to now take it from a very analytic algebraic point of view. We're going to come up with an equation that models the volume based upon that original size of 8 1⁄2 by 11. And we're going to investigate that on our calculator and see what we can find out. All right, so let's start writing this out and figuring out how to come up with these equations. So suppose I were to draw on my whiteboard an 8 1⁄2 by 11 type of rectangle. All right, so let's call this the side that's 11. And we'll call this side the one that's 8 1⁄2. All right, and from that, what we're going to do is we're going to represent sizes of squares that we could cut out from the corners. Now remember, we want to algebraically represent this. So we don't want to think of a specific number or anything in terms of the size. So let's just call those sides X. So obviously it's a square we're cutting out, so the two sides are the same. So we can represent each of those as being X. So when I'm drawing this, I'm trying to make these squares about the same size as I can. So all these sides of these squares that I cut out would be as X. So if the length of the paper is 11 inches and from each end of that paper, I'm cutting out a square that is X inches long. We need to figure out, all right, well, when we create the box by folding up the sides, this part right here, this is really the length of the base that remains. So we start out with 11 inches. We cut out X inches on either end. So the length that remains can be represented as 11 minus 2X. Now we're going to do the same with the width. So we start out with a width of eight and a half inches long. Once again, we're cutting out a square that is X inches long from either end. So this little part in here, that's going to be 8.5 minus 2X. All right, so from all this, we need to come up with an equation that's going to represent the volume. Now remember how we get volume of a box. It's length times width times height. Well, we have the length and the width, that's the 11 minus 2X and the 8.5 minus 2X, but envision where the height comes from.  The height of the box is going to be the same size as whatever the square is that you cut out. So our length, that's 11 minus 2X, our width is 8.5 minus 2X, and the height is simply whatever that square size was that you cut out. So what we have here is an equation and we could multiply the binomials together then distribute the X. When you do that, you come up with the equation 4X cubed minus 39X squared plus 93.5X. Obviously there's three X's, that's why it comes out as a cubic equation. This also explains why we measure volume in cubic units because it is a cubic three-dimensional figure. We have a length, a width, and a height. So that's why we have a cubic equation now. So what we wanna talk about next is now that we have this equation of a volume and we all know what a cubic equation looks like, hopefully. A typical cubic equation is going to sort of look like something like that, of that shape. Well, it's going to have a maximum, it's going to have a minimum. We can actually use our calculator to find those. Later on, once you've learned calculus, you will know how to get this purely from an algebraic point of view. You won't even need your calculator to graph it. But for now, we can always graph this equation and then find the maximum and minimum from there. So if you grab your graphing calculators, I'll grab mine. Now the other thing I've set up for us in here, just so you can take a peek at it, is remember that table of data, back in middle school when you would have done this and created your own boxes and measured the dimensions. I put all that information in the calculator so that we can look at a scatter plot of it first. So what we have here, under list one, I have the height of those boxes. Under list two, I have the volume. All right, so what I went ahead and did, I set myself up a scatter plot. I'm sure you've learned how to do this in your past. And let's take a look at the scatter plot. That's what the scatter plot of those points look like. Maybe this is something you did back when you did the enrichment with us before. Now looking at it though, it very much looks like a parabola. But we know from the equation that we just found, well, it's really a cubic. So what we're going to do is go under y equals and we're going to type in that cubic equation that we just found. Now what you can do on your calculators since you don't have these points plotted, all right, why don't you just go ahead, I'm gonna turn off my stat plot for a minute. Just so that my calculator can match up with what yours is doing. All right, if you have the equation under y equals, just go ahead and do zoom six for now. This way at least we're all looking at the same graph. And you can see it definitely has that shape. Doesn't look like we can see the top too well. We can see the bottom there, the minimum point down in the fourth quadrant, but we can't really see the top up in the first quadrant. So let's adjust our window a little bit. Let's go under window and let's change our y max. I think if we make it 70, I think that'll be high enough for us to see the top of it. And go ahead and hit graph. That looks much better. We could even adjust it a little bit more because it looks like there's really no part of the graph over in the second and third quadrant. So if you wanted to, if you go back under window, we could make the x min zero. Maybe that'll give us a little bit better picture to look at. And hit graph. Ah, much nicer. So you have to remember what this graph represents. Our x coordinates, if you look at the equation we wrote from our picture we drew, the x represents the height of the box. The y's represent the volume. All right, because under y equals, we put in the volume equation. Hence, every y value on this curve is going to represent the volume for a certain height box. Now this is specifically for an eight and a half by 11 size piece of paper we start with. If we were to change the size of that paper, we're going to have a different equation. All right, so each equation is tailor made to the size of the sheet of paper that we begin with. So if you take a look at this, and let's just sort of investigate what we have. Well, if we hit trace, all right, mine happened to go to the very bottom of the cubic equation. All right, take a look at what the coordinates are down there. All right, it has an x value of five, which represents that the height of our box would have been five. The volume though is a negative seven and a half. Well, we all know you can't have negative volume. So that's really a part of the graph that we really wouldn't need because we cannot have a negative volume. So let's trace a little bit to the, let's go left. All right, once we start getting over here, let's see, well, there's around three and a half right there. So if our height of the box is about 3.51-ish, we know that our volume's going to be about 20.6546 cubic inches. So what we have here is a really great way that we can come up with a lot of different possibilities. Suppose we want to have a certain volume. We could figure that out, how big our box, how tall our box should be. What if we had, we knew our height was a certain height? Well, what's the volume going to be? There's a lot of different ways we can investigate this. So let's talk about some of those different things we can do. The other thing we might want to think about if we go back to our window, well, remember what our x's were and remember the size of the piece of paper we started with. This was an eight and a half by 11 size piece of paper. So in terms of our height, we're going to get to a point that, well, we can't have a box that tall because of the limitations on the size of the paper we started with. All right, remember our paper was eight and a half wide by 11 inches long. Well, we could cut out a square that was four inches. Some of you might remember doing that back in this activity before. That's going to be a box that's pretty tall, but the base is pretty small. Well, let's see. Cutting out a square of four inches on a side, that's eight inches right there of the eight and a half. So chances are we really can't go much bigger than that. So let's change our x max to four. You could probably go a little bit bigger than that, but not too much. So let's hit graph again. Now this looks much more like the scatter plot. All right, let me switch back to the scatter plot really, really quick. Just so you can see and kinda, you'll have this on your calculators. Let me switch back to the scatter plot just to show you what that looked like. There's the scatter plot that I already had set up and there's the curve you should be looking at on your calculator. All right, and you can see how well that curve goes through all those points. It very much models very well what these points are telling us. All right, so this is what you probably learned about regression equations. If we were to have run a cubic regression on these points that I happen to have in my scatter plot, we would probably come out with pretty darn close to the equation we just got and wrote by hand. All right, so let's keep investigating, though, that equation. Let me turn my scatter plot off so I'll get back to looking at a graph like you have set up. So there's the graph you're looking at right now. So suppose I wanted to figure out what would be the volume if the height of my box and therefore the size of the square I would have cut out was maybe 2.75 inches. Well, we can use the calculators feature to easily do that. If you do second trace, you'll get all the calculate functions that you see here. The first one value will allow us to type in whatever x we want, and it will tell us what the volume corresponding to that height would be. So if our height of the box, also the size of the square we would have cut out was 2.75 inches, hit Enter, and we get a volume of 45.375 cubic inches. And you could really make up any x value to do that with. There's certain x values that we know we can't have. We already talked about have, you really can't have an x much bigger than four. What if we did do four? Let's see what happens there. Oh, you can see it all the way over there on the right. You get a volume of only six cubic inches. Kind of interesting that the largest square you'll cut out will give you the smallest volume. Well, what if we also wanted to maybe go the other way? What if we wanted to have a box that was a specified size in terms of volume? What we could figure out is, well, what are the different possible ways we could come up with a box of that size? So let's go back under y equals. Suppose I wanted to have a box that specifically was 40 cubic inches big. So hit Graph, and you'll notice that there's two different places that the line intersects the curve. So what that's telling us is we have two possible ways that we could come up with a box that has a volume of 40 cubic inches. So let's go find those really quick. If you hit Trace, and remember, you always use your right and left arrows to move your spider. So I'm going to go find that intersection point there on the left first. So if you move over to the intersection on the left, now your numbers might not be the same as mine, which is fine. And to find the intersection, remember you do second trace, and it's down at number five. Hit Enter. Remember that you need to tell the calculator which two curves you want the intersection of. So right now I'm sitting on y one. Hit Enter. Now I'm sitting on y two. Hit Enter again and again. And we find that a volume of 40 cubic inches we can get by cutting out a square that's about 0.545 inches on a side. Well, there is another possibility because there is another intersection point. So let's hit Trace again, and we'll go over to that intersection point on the left, on the right rather. And again, you just have to get kind of close to it. Your numbers might not be the same as mine. Do second trace down to intersect. And if we were to cut out a square that's about 2.922 inches big on a side, we'll still get a volume of 40 cubic inches. So these are just some of the very introductory basic things you could investigate. Well, let's figure out what the maximum volume is. All right, taking a look at this cubic equation, obviously there's a highest point up there. So let's hit Trace. Let's trace all the way to the top. If your equation's in the way like mine is, let's fix our window maybe and go up a little higher than 70. Let's make it 80 perhaps.  So let's hit Trace again. Ah, much better. All right, so if you go to the very, very top of that cubic curve, and what you wanna do, keep an eye on your numbers. Again, your numbers might be slightly different from mine if you have a different TI calculator than I happen to have. What you wanna do is try to start out at the biggest y value you can. All right, now again, your biggest y number might be a little few decimal places off from what mine is. All right, so let's see, mine's about, think right about there. All right, so go ahead on your calculator and just move to the highest y value that you can. From that point, we're going to run the maximum feature in your calculator. All right, so if you go under second trace again, you might've seen it when we were finding the intersection. It's down at number four, and you'll notice that it's going to ask you two questions. It's going to ask you for a left bound and a right bound. My recommendation would be just go a little bit to the left, a little bit to the right, of where you're starting out. That's why I recommend that you start out at the highest y value. So for my left bound, from where I'm sitting right now, I'm just going to go one hit to the left with my left arrow, and I'm going to hit enter. And you'll notice then that the question changes to right bound. So I'm going to go one hit back to the right where I started, and then go one more to the right, hit enter again, and you'll notice if you look really closely at your calculator there, there's two little triangles that are marking the interval in which that maximum point's going to be located. Hit enter once more, and you find out what the actual maximum volume is. So it's about 66.148 cubic inches. Now when you did this back in middle school, you might have remembered finding that the maximum volume was 66, which given those numerical methods we were finding, that was pretty darn close. This is even a more exact answer because we've used it finding the algebraic equations. That maximum volume comes when we have a height of about 1.585 inches. So the interesting thing is what a lot of people think when they're younger, and they maybe see this problem for the first time, is that the volume can just get bigger and bigger and bigger when really it doesn't. There's a maximum to it, all right? And we can see that very, very easily from our calculator. Now there's a lot of other things that we can investigate as well, all right? And these are some of the things that you start getting into, especially if you were to take calculus. Because one big idea behind calculus is that of rate of change. Well, we have an equation that models the volume. So what we could find out is for any one point on that curve, how fast is the volume changing? And that's something that we can investigate very easily without really knowing the calculus by using our calculator, all right? So let's go back to the graph that we had, and I'll show you how we can do that very easily. All right, I'm going to go under y equals and just get rid of that 40, just so I'm not looking at it anymore. And this is where you really want to keep in mind what this curve represents. Remember, this is representing the volume, or y values are the volume. For any given x, and the x in this case represents how large of a square we would have come out, cut out, and that turned into what the height of the box was. So maybe we want to figure out, well, when the size of the square that we cut out is a certain size, how fast is the volume changing at that point in time? So if you do second trace, the one that's going to tell us, if you look at number six, you'll notice it says dy dx. Once you take calculus, you will become very familiar with that notation. That represents a rate of change. In calculus terms, it's the derivative of y with respect to x, which is always a rate of change. Specifically, it's an instantaneous rate of change. So if you hit dy dx, and you'll notice that your graph looks like this, we're always looking for the instantaneous rate of change at one particular point in time. So suppose we wanted to know how fast the volume was changing when the height of the box was two inches. So just type in two, and you'll notice it automatically changes to x equals two for you. Hit enter, and you get dy dx. Now take a look at where your blinky spider is on the curve. That is the spot at which x equals two on the curve. And notice how we get a dy dx value of negative 14.5. So think about what that represents. When x equals two, which means the height of our box is two inches, or you can think of it that the size of the square was two inches, we find that the volume is changing at a rate of 14.5 cubic inches per inch that the x value would be changing. The negative represents that it's decreasing at that point in time. If you were to find that dy dx at different places on the graph, and you'll notice on your handout, there's the opportunity to do that, to investigate that, you'll start getting a sense of what these different rates of change tell us. All right, what does it represent when the rate of change is negative, like that one we just saw? What happens that the rate of change is positive? What does that represent? Or what if that dy dx, that rate of change comes out zero? What does that represent? So you'll notice on your handout, there's the opportunity to do that and discuss it among your own classmates. And that's some of the stuff that sort of gives you a glimpse of what you'll be doing once you get to calculus. So thanks for joining us today. It's been great being with you and good luck as you move forward in your math classes.


Hey everybody, this is Brett, and today I'm super excited to show you this brand new 2022 Jeep Grand Cherokee Summit Reserve Package. This stock number is 22J113. I am here at Summit Automotive in Fond du Lac, Wisconsin, your new and used Jeep and Jeep Grand Cherokee headquarters. And I really wanted to do a video on this one in particular because it is the Summit Reserve Package, probably one of the, it is one of the top packages that you can get on the Grand Cherokee. This one's in a really nice color, it's Baltic gray metallic, paint coat is P-A-S. And this one has the 3.6 liter V6 Pentastar engine, puts out 293 horsepower, 257 foot-pounds of torque. It's going to get you 26 miles per gallon on the highway, 19 city and an average of 22 miles per gallon. Just a really nice combination on this vehicle as far as options, color, looks, and styling. And wait till you see this interior on this thing. It is amazing. We're also going to turn on all the headlights and everything when we get to the end of the video here, so definitely stay around for that. And if you like the video, you can subscribe to my YouTube channel and the upper right hand part of the screen is a link to do that. You get the kind of, it's not chrome, but it's a silver finish to the grille and lower front valence pieces there. You get the LED fog lamps, the LED headlamps, the LED running lights right there, of course the chrome Jeep logo on the front and the seven slotted grille for the seven continents that Jeep has been on. So this one has 21 inch painted and polished aluminum rims and they are really good looking rims and they come with Continental cross contact tires. These are 275, 45R21s and you can kind of see the tread pattern on there. This one does come with the optional running boards and you get the chrome, oh, it's actually kind of that silver finish on the Grand Cherokee logo right there. We'll take a look at the original window sticker. It's always a big point on these vehicles. You can see that this is a 2022 Grand Cherokee Summit Reserve, the Baltic Grey is the color, the interior color on this one is two paleo and black interior colors and these seats are considered Palermo leather seats. Get the 3.6 liter V6, 8 speed automatic transmission. Everything on your left right here is your standard equipment including the Quadra Track 2 system, the select terrain, traffic sign recognition and everything like that. You connect five with the 10.1 inch touchscreen and everything right there is your standard. Now your optional equipment starts with the Baltic Grey metallic which is 395, the Summit Reserve Group 22U is $4,480 and that gives you those 21 inch rims and tires, the Palermo leather seats, the 19 speaker high performance audio, the active noise control system, the 950 watt amplifier vented rear seats, deluxe headliner, Palermo leather door trim and this one also has the Advanced ProTech Group 4 which is a $22,35 option, heads up display, gives you the night vision with pedestrian and animal detection and we might take this out later and do a night drive with it just to show you that system. Rear view auto dimming digital display and then the luxury tech Group 5 which is 275 gives you the wireless charge pad and the manual second row window shades. Those Mopar steps are 975 and it has a discount for a conventional rear axle of $400. Total MSRP on this one is $70,055 if you want to get to your Summit price and the upper right hand part of the screen is a link to our website, click that and then click the bell notification or click that and then check out our prices there, I'm not really sure what we're asking for this one but it will have all the discounts and rebates available on this particular vehicle. Three year 36 bumper to bumper, five year 60. There is your miles per gallon 26 highway 19 city and 22 combined and it's not rated for safety reasons but a lot of times these Grand Cherokees are extremely safe and we're going to get into this interior in just a second because it is beautiful but I just wanted to finish the outside walk around here. Notice you get the black top half of the vehicle, you also get the LED tail lamps, you get the silver finished Jeep N4x4 logo on there as well as the Summit Grand Cherokee logo there as well. So this one has the power lift gate of course, notice you get the dual rear exhaust back here, the Berber floor mats, the factory subwoofer right there and this one does come with a spare tire. You get that kind of silver finish right there, you can press this button to get the rear gate down. Those seats do fold down flat and I'll show you just how nice and flat that those go. Press the button, it'll be at you three times and then begin its descent. Notice you get the rear parking sensors back here as well and then you get the capitalist fuel fill which is always a nice feature. Belted grays got just a little bit of metal flake in it, so you can see that right there. It's really a cool color. It does have the enter and go system so you just have to have the key in your pocket and it'll automatically unlock. Blind spot monitoring, you have your heated mirrors, built in directional signals and get a really good look at those step bars there. Here's the moment, this interior, really, really good looking interior, love that color. You get these Summit embossed into the backrest, you get the quilted stitching on the seats, the black piping on there, power driver seat, lumbar. This one does have the massaging seats. You get the Berber floor mats throughout, auto headlamps, power, telescopic and tilt steering wheel, the wood grain trim, the black accents. That wood grain trim goes onto the door. You get the quilted leather on there as well, power windows, power locks, power mirrors. These mirrors do power fold in, so that's kind of a neat feature and how that works is you just turn this knob here and then they'll go back out, but if you turn it all the way to the bottom they fold in like that. We'll take a quick look at the back seats. One of the things I like is notice how far back this front seat is and I can still get this backrest down without moving that front seat because those headrests, they fold down right away and then we can get that down. You can see just how nice and flat that those seats go, which is really nice if you're hauling a bunch of extra stuff. Trim's a very similar back, here you do get rear air controls and these back seats are heated and cooled with the Summit Reserve package, so really nice there. In here you get two USBs, two USB C's, and a 115 volt, 150 watt plug-in. These C's fold up like so. Get that same trim back here and the one thing that the back seats have that the front seats don't is this sun shade, which if you've got kids or a lot of people riding in the back, that's a really nice feature to have and you do get child safety locks on the back doors right there and we'll take a look inside, check out the radio, the instrument cluster, everything that this vehicle has to offer on the interior. So you can see you get the big instrument cluster right there, I'm just going to see if I can figure out what size that is, it does not say on the window sticker here, I think it's like 10.2 inch, 2.5 inches or something like that. Anyways, it's all configurable, you got your compass, your outside temp, your digital speedometer, everything's nice and crisp and clear, you can do all your different stuff on here. You can do your navigation stuff, your radio, this is your off-road package if you want it to raise the vehicle, go into like off-road mode one or if you just want it automatic, you can choose all that stuff on there. You get the heated, really a good looking steering wheel, you get the black trim on there, the wood grain trims all integrated, the brown stitching on there as well, controls are all the same as all the other Jeeps, heated steering wheel, this is your adaptive cruise control, normal cruise control, lane keep assist, all that good stuff, there's more tech equipment up here, your start stop, lane departure warning, stability control, parking sensors, your perpendicular and parallel park assist, this one also has the passenger side screen which is really cool, basically somebody can even hook up like an HDMI video game console if they wanted and play video games there or watch a movie or whatever and when you get to the driver's seat you really can't see it so it's kind of blocked off so that's nice, heated and cooled seats throughout, climate controls right there, there is your wireless cell phone charge pad, two USBs, two USB C's and an aux jack, here's all your four-wheel drive system that you can do with the manual, you can put it in snow, sand, mud, rock, auto or sport and that of course changes the driving dynamics of the vehicle, you can raise the vehicle, lower the vehicle, go to off-road mode one, off-road mode two or for better aerodynamics on the highway it actually lowers so that's really cool, four-wheel drive, down hill assist control, here's your keyless entry, they went with the rectangle style key fobs for the new body style and you can see you get keyless entry remote start and your power lift gate on there as well, so there's that, you get two cup holders and just take a second to look at this interior, wow, Macintosh sound system, very, very good looking and of course you get the suede headliner, the power vista roof, second roof fixed glass, power sunroof in the front, assist in SOS, controls for that sunroof, rear gate, map lights and then you get the video camera review display so you can make that just a review mirror like so or you can actually make it a video camera now that's a video display of what's going on behind you, you can do a couple things here you can make it dim or you can raise it or lower it like so so that's pretty sweet and then you get the heads up display in the windshield there so that's all really cool stuff and of course home link buttons for your garage door security systems and lighting systems so what I'm going to do is I'm going to turn it on we're going to turn all the lights on and I don't know if I can show you any of that night vision stuff on here I really haven't played around with it a lot yeah I'm not sure exactly how we can get into that but you can see with the little moon there it does have the night vision on and I think that turns on automatically when you have the lights on not really sure so anyways you can see all the different stuff here tire pressure monitor and everything in there where you can just have your main menu with the digital speedometer on there too so we'll do one more final walk around with all the lights on as promised and I would personally like to thank you for checking out the video today and hopefully from this HD video you have gotten a really good idea of the overall looks styling options and learn a little bit about the Jeep Grand Cherokee Summit Reserve really a good looking ride a lot of nice options this one has just about everything you could ever ask for and really think it's a sweet ride let me know what you think in the comments if you like the video if you like the car if you want to see something different in the next video I'm open to doing anything to help make my view your viewing experience better on my videos but I'd highly recommend this vehicle from a look styling options and just a really nice ride standpoint and to see more pictures of this Jeep or one of our other 550 new and used cars trucks SUVs minivans wranglers half tons three quarter tons one tons Cherokees grand Cherokees wranglers we got it all with the new Jeep showroom it's going to be amazing so a lot more videos like this to come thanks for checking out the video in fact in a second you'll see a link to subscribe to my YouTube channel which is in the upper left hand part of the screen a link to more grand Cherokee videos that I've done in the upper right hand part of the screen a link to this vehicle on our website in the lower left and a link to one of our latest YouTube videos in the lower right click those check us out and we're super excited to be offering the brand new Jeep Grand Cherokee Summit Reserve and Baltic Gray metallic thanks again for checking out the video I really appreciate it remember to like subscribe and share on the YouTube channel and once again thanks again for checking out the video I appreciate it thanks again


City Inspector warned store to remove flags, gets in customer's face. After a city inspector warned a store to remove U.S. military flags, a customer got upset. Video then surfaced, showing the inspector getting in the customer's face and outrage erupted. Melinda Power, a code inspector in Jacksonville, Florida, entered Jaguar Power Sports with her supervisor to issue a warning citation, telling the store to remove its rooftop flags representing each branch of the military because she said it violated city code, WJAX-TV reported. Power told the business to correct the violation or risk prosecution for the offense, which upset the staff. We cater to our men and women, both retired and active military. So it was personal, store manager Marcy Moyer told WJAX in an earlier report. We felt like it was a personal attack, she added. According to employees of the store, which also flies two American flags and a Jacksonville Jaguar's flag, a customer, who happened to be a military veteran, overheard Power's warning and was also upset by it. When he decided to say something, Melinda Power got in his face. A surveillance video captured the confrontation. What did you do for this country? Power asked the combat veteran, according to employee Katie Klass, who was present at the time. The veteran, who was not identified by name, responded, saying he took three bullets and almost lost his leg for his country. Klass said that he also told Power he was retired and a veteran.  Employees said Power was so disruptive and disrespectful to the veteran that they asked her to leave, but things were far from over. In a since-deleted Facebook post, Melinda Power allegedly recalled the incident differently, saying she thought the customer had asked her, Do you know what I did? and she responded, Nothing. But, she also allegedly admitted, I should never have been unprofessional and disrespectful period. Sincerely apologize, adding that her father, husband, and son-in-law have all served, and that she has the utmost respect for the military. It was too little too late though. As the video of the inspector getting in the veteran's face surfaced, outrage ensued, and City Hall was inundated with calls about the citation with 50 calls taken in the first hour of business alone most of which called for the inspector's termination. In addition to the calls, military veterans fumed in front of news cameras outside Jaguar Power Sports. The overall consensus of the veterans was that the inspector's actions were insulting and out of line, particularly when those who've served in the armed forces have given so much to their country, and it would seem the mayor agreed. What I so reported is 100% inconsistent with how I expect every city employee to interact with our citizens, he said, adding that both Power and her supervisor were placed on leave. As the son and grandson of military veterans and the mayor of a city with a proud history of commitment to our nation's defense, I will not tolerate disparagement or disrespect of the men and women who serve or served, Jacksonville Mayor Lenny Curry explained. On behalf of the city of Jacksonville, I apologize to veterans and service members, who are rightly troubled by the events that have been reported. The mayor also said current ordinance does not address residents or businesses displaying military flags, but he will not allow any citation of those who demonstrate their support for the armed forces. He added that his team is working with the city's Office of General Counsel to bring clarity to the relevant city laws. The veteran involved in the confrontation said he's pleased that the mayor responded, but he'd like Melinda Power to apologize to the veteran community not necessarily to him though. Further showing his character, he added that he doesn't want anyone to lose their job. Jaguar Power Sports Manager Marcy Moyer shared his sentiments, saying she didn't want to see power fired. I know that our customer base would love to see me say, fire her, but I hate to see anybody lose their job, Moyer explained. That was not the purpose of this. It was to bring awareness and hope that someone would not treat someone else that way. Indeed, this incident serves as a reminder that we should handle disagreements by still showing respect for one another. Luckily, the veteran and the store staff showed us how that's done when the city inspector failed miserably to do so.


What's up everybody just here for Jasper's case breaks calm shows 1920 hip hurried the rookie's graded young gun edition Series two hockey two box break three random teams each number three just sold out and again ten total spots Everybody gets three random teams in a cell Yotes and ducks are combo to make one team and again every box contains two graded young guns from Connery David all the way down to Mark Stoner and many more So let's do the break guys. Let's roll it And we got a six and eight three nine times rolling a lot of nines today. Good luck one two three four five six seven I'm not here as well one Stars No stars wait with the leaves Steve with the blue jacks Nicholas the predator Steve with the Bruins avalanche Stephen K With the wild wait with the senators Canadians they live with the shark Steve the lightning Nicholas the penguins wait with the panthers even care the rangers way with the Islanders Edel with the blues Steve with the devils Stephen K with the hurricanes way with the savers Nicholas with the ducks yachts Steve with the flames Edel with the red wings Wait with the capitals and they go to the venus wait with the blackhawks nights Nicholas with the kings Wait with the oilers jets of flyers All right, anybody want to trade. Let me know all right if anybody wants to trade Let me know if not. I'm closing it. All right, you guys. I got a box two four and five Let's see if I can roll one of those numbers or roll, but I got a five Box 59 out of 100 our first one guys We got is a 2010 everdeck PSA nine French Pique a subon Like the French edition of young guns. It's pretty cool Montreux, Canadian's That's one It's a bgs From 1819 upper deck series one 95 It is Elias Petterson bgs 95 This is a perfect solid nine five all around Vancouver Canucks that is one of Nicholas lolly. There you go. Nice box. All right next box 2010 upper deck PSA eight Taylor Hall for the oilers Going to wait Another PSA. Oh, this is a PSA 10 from 2015 16 Upper deck series one hockey Who you know who's in 1516, right? Well, we know Connor Mcdavids in it But how about this guy? This guy is also part of it Miko ranting it. There you go Miko it's one of the Colorado avalanche Steve Birch Very nice. And there you go another two solid boxes of these great and young guys Appreciate it guys. The next one's already in the store and I believe if I refresh my page Already down to five left. Appreciate you guys. Jasper's case breaks.com


Hi friends and subscribers and welcome back to my YouTube channel Jerusalem and Israel unpacked this is Daniel Rosal here bringing you this video today from the from my little cranny here in the center of Jerusalem in Israel. All right, let's get into today's video but I want to firstly make a couple of notes about this YouTube channel note one is that for about the last six or eight months. My YouTube videos have been sort of these little animations I make up in Canva trying to explain what I think are interesting topics to do with Jerusalem and Israel. I look for the kind of slightly more offbeat topic. This isn't just kind of your standard pro Israel channel. I'm always trying to just explore behind Israel and Jerusalem a little bit. So recently I just haven't had the mental bandwidth really to produce that kind of content because there is, you know, obviously a war going on here. And it's just been a really busy time generally. And I've just reverted to this very boring production standard. I'm sure visually of me speaking into a webcam. I do it after my morning coffee and I just pretend I'm talking to a friend. So that's the first thing I'm doing more of these videos and I realize that they're not that visually interesting. So this is the note. I'm going to be less derelict in running my podcast. It's called the Daniel Rosal podcast and it's been I've barely put out anything for the last few years, but it is out there on Spotify and all your standard platforms. And because I think this is really more a podcast with a video element when I do these kind of videos, I'm going to be distributing them out via the podcasting platforms. You can also I highly encourage people to subscribe to YouTube premium because that way you can sort of watch any material as a podcast to support background playing.  That's another option if you find me talking into a webcam to visually boring, but you enjoy the content. That's a recommendation I want to make the last place. My last studio was a little bit better, but then we moved we moved to a new apartment and there's just not a lot of space behind me there to do something exciting, but I will work on it. Anyway, today's video. Oh, and no two is that I interviewed last night a Irish guy who supports Israel called Kearon and I'm going to be editing that video either today or tomorrow. If you're interested in the Ireland, Ireland, Israel stuff and my videos have been very negative kind of dunking on Ireland a little bit. And people said, you know what? There is there is support for Israel in Ireland. There are pockets of support, so please for some balance. Can you do a video about the pro-Israel movement in Ireland? And I said, that's a great idea. Put out some feelers and the first guy to get back to me was Kearon. And we had a chat last night and we talked about the media bias in Ireland. We talked about the support for Israel in Ireland. And just if you're interested, keep an eye out for that episode of the YouTube channel. All right, let's talk today. I want to talk about what I see as three main challenges in Jerusalem. And I think a good rule of thumb is don't talk about challenges if you can't offer a solution. So I'm going to throw out three possible solutions as well. These challenges are informed by my almost decade-long experience of living in the city, as well as the research I've done for this YouTube channel, stuff like the Jerusalem Institute for Policy Research and whatnot. So both of those are forming my impressions here. All right, challenge one. And by the way, this is for friends of Jerusalem, this video. If you live in Jerusalem, this video is definitely for you if you're an English speaker. And if you support Jerusalem and its future because while we're currently married in war, we have to remember that there will be a day after. And I think it's important during this tough time of war to keep that in mind that there will be a day after and we will get back to building a future. And to some extent we continue building a future while we're at war. So I want to say as well that I think everyone who's a friend of Israel has to be a friend of Jerusalem. I don't mean has to, like you're forced to, but I mean that if you're a friend of Israel, you're a friend of Jerusalem because you're automatically a friend of Jerusalem because Jerusalem is the capital of Israel and Jerusalem is the epicenter of the Jewish people's connection to this land. It's more than just a city in Israel. So just want to say that. All right, challenge one in Jerusalem from my perspective, widespread poverty. The numbers fluctuate from year to year and Jerusalem is often called the poorest city in Israel. So that's a general longstanding trend. The numbers that I have here on my screen are that 47% of Jerusalemites live beneath the poverty line. Now that was from a couple of years back. So maybe it's gone up or gone down a little bit, but not drastically in either direction. And that is a shocking rate of poverty in the city. How do you see this? Well, you do see this if you keep your eyes open when you're in Jerusalem. Firstly, you'll notice a lot of beggars wherever you go. The second thing you'll notice is a preponderance in certain sectors of Jerusalem of these kind of supermarkets oriented for the ultra orthodox already population that are selling stuff like bulk pasta and bulk rice and what I would call subsistence foods, right? They're selling them on the cheap in large quantities. And this supermarket I'm referring for those who don't know to OSHA add is very is both run by all the ultra orthodox and that's their main client base. So you get hints of it, right? You see people buying 5 kgs of pasta to feed huge families and just scraping by and you see begging. And those are just two of the manifestations of poverty in the city. I'm just going to move my microphone a tiny bit here. So that's the challenge. Now Jerusalem is as I've said countless times and sorry to be so repetitive and boring. A city of three cities in one. You have the Jewish sector and that is two cities.  I mean, less religious Jewish people who define themselves as just that tea, which means orthodox or master tea, which means traditional. And that's where I see myself as being master tea. And then you have the Haredi as I mentioned, then you have the secular Jewish population. And then so that's ultra religious Jewish, less religious Jewish and Palestinian. The numbers, it's about 60 40 Jewish Palestinian, sorry, Jewish to Palestinian. So it's not that far off from being 50 50. So the idea that Jerusalem is a just Jewish city is completely false. Not only that, but the trend line is that Jerusalem is actually becoming slightly less Jewish. At one point it was 72% Jewish. Now it's down to 60 ish. So that's that. And then within the Jewish pop, you have a three, a third, third split approximately. A third Haredi, a third who are secular. There is a secular population in Jerusalem of Jews. And you have a third who are defined themselves as, as I said, that tea or master tea. So among these three groups of the city, the poverty really is mostly among the Palestinians and the Haredi. The non participation rate in the labor force. There are firstly among the Haredi. There is not as much as people think. And within the Palestinian, the most shocking non participation rate according to the Jerusalem Institute for Policy Research and their 2022 annual report, which I'll put a link to was among Palestinian women specifically. So the issue why you have such a shocking rate of poverty in the Palestinian sector at about 72%. It's got to do with the fact that the men are not earning a loss and the women for reasons of maybe tradition are not working. So you've got single income families with one of the income providers being, you know, maybe a laborer or stuff like that, right? Not very high paying jobs. And the city to some extent is trying to encourage the establishment of these kind of high tech centers in East Jerusalem was the idea of getting East Jerusalem. East Jerusalem, my Palestinian entrepreneurs, the resources they need to create the tech ecosystem that has drastically raised a standard of living among other groups in Israel. My solutions that I'm going to propose and I just remember I'm just a guy living in Jerusalem. Although I do support a specific political party here, and I have been trying to work within the party to get these issues on the agenda. My solution to poverty is that the city, I think, well, you've got two angles, right? The second non participation is one. That's the obvious place to start. Non labor force participation among ultra orthodox and Palestinian specifically. The second one is bringing companies to Jerusalem. Now I've been living in Jerusalem, as I said, for almost 10 years. And every time I've gone job hunting in Israel, it's been the same picture. There are barely any startups in Jerusalem and startups are, as I said, it's called high tech in Israel. High tech is kind of a catch-all phrase, meaning companies that are distinguished by their technology. But every time I've got job hunting in Israel, I've been like, why the hell am I living in Jerusalem? And why I'm living in Jerusalem is because I made Aliyah here to Jerusalem. And then I met my new wife. And for various reasons like jobs, we've been kind of rooted to the city since for some time or another. But every time I've been between jobs or moving jobs here, I've said there is no opportunity in Jerusalem. Now the numbers I have to support this claim were from startup nation central and they do really show a huge disparity between the employment picture in the Merkaz of Israel, the center, which is Tel Aviv and surrounding areas as Jerusalem. Jerusalem is drastically worse. So that has to change if Jerusalem is going to be a city that's going to attract and retain young people. Because right now it's doing one part of that picture. It's attracting youth and it's not retaining them. Why? Because people get fed up of the dismal employment scene here. I'm not currently job hunting myself. I work for a nonprofit, which is based in Tel Aviv. So I'm in the lucky situation that I only need to go to Tel Aviv once a week. A lot of people living in Jerusalem have to do that commute every single day. But I didn't have any choice in the last job hunt. None of my options were Jerusalem based. It was either this job or another job in Tel Aviv. I have a friend who's job hunting now for quite a while and he's told me it's the same. It's not changing. We don't see it getting better. I'm living in Jerusalem. I would say I haven't seen the same picture going on for 10 years now. So that really needs to change. My second proposition to our potential solution here, and I think this is one that gets neglected, is that we can, as that link to Tel Aviv, the light rail gets better and better. Or the train I should say, not the light rail. As that gets better and better, it's becoming increasingly viable for people to do jobs like the one I do. Right? I go to Tel Aviv once a week. It takes me now only one hour to get to Tel Aviv, 30 minutes on the train, 10 minutes to get there, blah, blah, blah. One hour give or take. It's not dreadful. And I listen to podcasts in a way and it's actually quite enjoyable. The fast train is wonderful. So with that link to Tel Aviv getting stronger and stronger and better and better, it's becoming more and more possible for people to do remote jobs in Jerusalem. Now, what do you need for a remote gig economy to flourish? I'm going to suggest two things. One of them is co-working spaces because no one likes to work alone all day or very few people do. And we need affordable co-working spaces, not WeWorks. We need high quality, well managed and affordable co-working spaces, creating bubbles and ecosystems for people working remotely, whether it's with companies in Tel Aviv or Herzliya or companies not in Israel is really immaterial, that people who do remote jobs should have a sense of community. And I think that it has to be key. Right now, we don't have enough co-working spaces in Jerusalem that are affordable, especially ones that you might have, let's say a private office, but shared spaces. And WeWork, it's something like 4,000 shekels a month. It's not affordable for most people in Jerusalem who might just be getting by anyway. Certainly not affordable for me to pay that kind of money for the privilege of having an office. The second thing is connectivity. I have terrible internet. This isn't just me grumbling about my personal bad internet connection.  We have Laos DSL internet. Now, there is fiber optic internet, but the deployment is not happening anywhere near as successfully as politicians would have you to believe. It's sluggish and there's still wide spaces. I live in the center of Jerusalem and there is no fiber optic from any provider on the street. So I use DSL and it's a disaster. When I upload stuff, it takes down the network. So I have to coordinate my YouTube uploading to when my wife isn't on a Zoom call.  It's a joke. In the year 2023, crappy, slow DSL internet needs to not be a thing anymore. And we need to get fiber optic connectivity to every street in the capital city of Israel quickly. It's a joke that in 2023, there's large swathes of the capital city of Israel, where in the high tech economy, the epicenter of the high tech economy where there is no fiber internet, that needs to be a priority, in my opinion. Okay, challenge two, unaffordable housing. The huge problem in Jerusalem, renting in Jerusalem is too expensive and buying in Jerusalem is just astronomically expensive and way beyond the means of most people, most regular young people like me who make normal salaries. The only way that I could amass the equity needed to buy a place in Jerusalem is either with the support of family or if I sold a startup for millions of dollars. The amount of equity people need to get is something like $200,000 to get another property ladder. That's just for the down payment. It is crazy, crazy, crazy. So we're seeing right now the kind of sickening phenomenon of there being a housing bubble in Jerusalem, but all the housing being built is for, I hate to use the term rich people because it's lazy, but luxury housing for the very well financially endowed who only come and these are Jews living abroad, who only come to Jerusalem for a few weeks out of the year. So we're seeing this perverse phenomenon going on in which there's loads of building in Jerusalem and none of it is stuff that local residents have any reasonable prospect of affording. That needs to change. So, you know, mechanism, this isn't really my area of expertise, punitive taxes for non-owners or mandating maximum fees on the part of developers so that a house is affordable to a local resident. Again, I'm not an expert on this by any means. So that's housing policy is totally something beyond my area of expertise. But that's just as someone living in the city. I see repeatedly all my friends moving out of the city to, if they have any connection to Jerusalem, they're moving out of the city to Bechemish, Sur Hadassah places like this because they can afford to buy there and they commute into and out of Jerusalem. But buying in Jerusalem itself has become astronomically difficult. Challenge three is security. There are just a ton of lone wolf attacks in Jerusalem, stabbings and whatever that just don't make the international news. They're going on at a trickle, but they happen and they have not been happening. Why do they happen? No one likes to talk about this because it's not politically correct. They happen in large part because East Jerusalem is totally open to West Jerusalem. There is no border. The security fence is around East Jerusalem, disconnecting it from the Palestinian authority. But between East and West Jerusalem, you have a hostile, largely in large part and some part hostile Arab population and a Jewish population and that hostile elements within the Arab population move into West Jerusalem and stab people. Repeatedly, we've seen attacks from East Jerusalem residents in West Jerusalem. Now, what's the solution to this? This is again another one of the pools where I don't have relevant expertise to offer. This is a question for security people. One of the ideas that's been floated is putting up a border between East and West Jerusalem. So that another wall, so that those people, there are checkpoints to prevent the, as we've seen the success of the checkpoint system and the barrier system in the West Bank, that we would see a similar phenomenon in East Jerusalem. The problem is for the patriotic or the more Zionistic Jews, they would see that. Putting up a wall as conceding territory in Jerusalem to the Palestinians, to the Arabs, right? If you wall it off, it's like saying, well, that's your turf. This is my turf. We agreed upon a border and therefore they oppose that. So it's a really sticky question, but something does have to be done. Otherwise, it's just a fact of life living in Jerusalem that there is a knife attack every few days. And that's very unpleasant. All right, that's going to wrap up today. I see I'm almost at 20 minutes of jabbering here, but I hope that's been interesting. If you have thoughts, leave them in the comments and, you know, give me ideas as well for other videos of me just chatting into my webcam after my morning coffee. Thanks for watching today's video. Subscribe for more and until the next one.