He's going to talk about Adelic geometry via toposphere. Yes, hi everybody. So thank you very much to the organizers for inviting me. So what I'm going to be talking about in this talk is a joint with Steve Vickers, who is in the Zoom webinar. So he's here to be my conscience in case I say anything silly. But yeah, it's a great pleasure to be here. So thank you for the organizers for inviting me. And thank you for everyone for being here. I'm going to be slightly self-indulgent here because I think it's just nice to show some pictures. So this is the first conference I ever read, proper math conference I ever went to. And it was the 2018 version of Topos's online. And so here's a wonderful picture of all of us. I think this is Olivia and Laura. I think this is Engel and Ivan. And I'm over here. So I'm this adorable cluster of blue pixels, which you can't really tell. But yeah, it was very interesting times. And we were in Koma, which in case you're wondering is this place.  But I think, well, we'll leave that to some other time. But basically we went hiking and I was convinced I was going to fall off the mountain because Engel wanted to go all the way to the top.  But as you can tell, I didn't die. So I'm here to share some mathematics with you guys. So yeah. Okay. So let me just reset a little bit. So here's on this slide. I'm going to give you a program for the talk. So what am I going to tell you about? I'm going to talk about two basic things that cross cut different areas of mathematics. So the first question is what kind of information can homotopical data encode? And the second question is when can we solve a problem by breaking it up into smaller pieces? And then, you know, one, the first slide I said, a deli geometry via topos theories, like the subject of this talk, right? A lot of buzzwords there. I'm going to try and introduce some of the main ideas and discuss how it serves as a very interesting test problem for understanding how these two themes sort of illuminate each other. All right. So, all right. So on the first theme about like homotopical data, let me just start by recalling a much beloved example from algebraic topology, which is lime bundles over circle S1. So, all right. Suppose I'm standing. Well, you can't see it. I'm not actually sitting, but suppose I am standing in a, on a circle and I have a pole tied around my back and I walk around in a circle, right? And suppose I reach my original position, I'm still upright and that then, you know, the pole would have traced out, you know, a cylinder as you can see over here. But suppose on the other hand, you know, if I walk around a circle and then, well, maybe I'm feeling a little bit tipsy because, you know, why not?  And then in which case the pole on my back has traced out, well, something that looks like a mogus strip. There's sort of a twist in this particular setup. And so here's a very basic question from algebraic topology. Are these the only one-dimensional vector bundles over the circle up to isomorphism? And the answer is yes. And well, there's sort of like a couple of different ways that you can sort of show this, but the typical ways to exploit the theory of clutching maps. And really there's like, okay, what I want to say here is that there's a very tight relationship between the homotopy classes of certain kinds of maps between certain spaces and homotopy classes of maps between certain types of spaces and the vector bundles. And so the general argument usually goes something like, well, there's a close relationship between these two things and through some additional orientation arguments, we see that there's essentially only two relevant homotopy classes for us to consider. And one of the homotopy classes of maps corresponds to the cylinder, the other one corresponds to the mogus strip. And this is very, very interesting because this gives us a first glimpse of this really tight relationship between homotopical data, as encoded through the maps, and geometric data as expressed through the vector bundles. And this actually gives us, well, a first glimpse of a much more general phenomenon. And well, we have this particular classification theory which says that, well, suppose X is some sufficiently nice space, like just think of the CW complex and consider the vector bundles to be this, well, vector and X to be the set of isomorphism classes of n-dimensional vector bundles over this particular space. And this theorem says that basically, if you look at the homotopy classes of maps from X into, well, it's class of the gross minus, but basically it's classifying space. You look at the homotopy classes of maps from X into its classifying space, they are in bijection with the vector bundles, the n-dimensional vector bundles over this particular space. And notice what this is first saying is something really, really interesting in that the homotopical data in some sense is sufficient to, well, it does determine in a very strong way the geometric data from the vector bundles. And from the point of view of an algebraic topologist is very exciting because it gives us some indication about how homotopical invariance might encode very deep and very strong geometric information for us. So this is, you know, from the view of algebraic topology, how homotopical data might equals geometric data. And I put to you like a similar attitude occurs in toposphere in regards to geometric logic. So I'm just going to cite a paper by Vickers, continuous in geometric logic where he says, you know, simply but very boldly, in this paper, I shall survey some of the special features of geometric logic and a body of established results that combine to support the manifesto, continuity is geometricity. And so for the next few slides, I just want to put a little bit of flesh on this particular thought and start by just recalling some of the aspects of geometric theory and the theory of classifying toposas, which were already sort of touched on during the school. So, okay, what is the geometric theory? Well, a theory is basically some sort of axiomatic description of mathematical structures. I'm going to paint a picture in very broad brush strokes here. And the model is just something that satisfies this axiom, right? And geometric theory is just basically something that, well, it's a theory that's built out of the required list of logical connectives, right? Things like finite conjunctions, arbitrary disjunctions and the existential quantifier. So these are familiar ideas from the theory of classifying toposas. And, okay, so this is a particular example, which we're going to return to at various different stages of this talk and through different perspectives. And this geometric theory is the geometric theory or the propositional theory of Dedekin reels. And so I'm not going to give you the axiomatic description. I just wanted to highlight that, well, you have a Dedekin reels. And what is it? It's basically, well, a Dedekin reels consists of two sets of rationales, right? One of it sort of corresponds to the left Dedekin section and the other one corresponds to the right Dedekin section of the real numbers. And the axiomatic description sort of describes what exactly these properties of these sets of rational sorts have and how they sort of interrelate with one another. And so, right, there was some discussion during the first day about points of toposas. And it's well known that there's some toposas that, well, don't have enough points or don't have any points at all. And I'm going to give you a slightly different perspective here. So, all right, we call that any kind of, we know that the notion, the appropriate notion of maths between toposas is the notion of a geometric morphism, right, which are adjoint fantasies that possess the desired properties. And so classically, well, or traditionally, we think of a point of a toposas as some sort of geometric morphism from set into, well, into your desired toposas. But actually, you know, much of topos theory is about trying to figure out ways to vary the set theory of the situation. And so from this perspective, you know, it also makes sense to think of any kind of geometric morphism from any arbitrary topos into our topos of interest as some example of a generalized point. And we'll see why in a little bit. So this is, I think in the first, I think this was during Ricardo's talk where he talked about how toposas can be viewed as some sort of generalized space, right, because, well, that's what the purpose of the growth and excitement does. It sort of categorifies this notion of opens, living over a particular space. And here's a different perspective from the point of view of geometric logic. So recall that we have this particular universal property that characterizes what a classifying topos is, right? It's one that we have this particular equivalence of categories where, an equivalence which is natural in E. And we also have these basic foundational theorems, which really just says that this sort of description gives us an exhaustive description of growth and topos. Every growth and topos is a classifying topos of some kind of geometric theory. And every geometric theory, he has a classifying topos, you know, done through the well, syntactic constructions. So here's the slogan is that like, well, using this particular equivalence relation, right, I said before in the previous slide that we can think of geometric morphisms as some notion of generalized points, right? And using this description of the classifying topos, we can view the models as being corresponding to points of a topos in a particular way. In other words, again, we start to see in this particular guys how continuity or homotopical data sort of equals geometrical, in this case, logical data. And in particular to suggest something quite interesting because as category theories, you know, we're often used in thinking about what are the objects of the category, but in this specific case, in the case of topos, because of the universal property of classifying topos, it suggests that we can also think about that we can reason about topos in terms of the structures that they classify.  And so to sort of just see this, well, this inaction, so this is just me recalling the previous slide and using the theory of data can risk a particular example. So I'm just plugging in, you know, are in the appropriate places, right? And just plugging and chugging. And okay, so suppose I have a generic data can relax. I can add X to itself, right? X plus X is still the data can reel. In other words, it's still a model of this particular topos with respect to the theory of data can reels. And by the universal property of what classifying topos is, this corresponds to a geometric morphism between the appropriate and the relevant topos, right? Okay, so, okay, I'm going to, this is sort of like a bird's eye view of what we're doing right now. A bird's eye view of the kind of, well, the sense in which we're talking about generalized spaces right now. And really what we're doing is trying, we're starting to pull away from the set theory slightly. So classically in terms of, well, points at topology, we think of, well, what is a space where a space is basically a set, right? And points are the elements of the set. And then topology is sort of some sort of extra structure that we equip this thing with. Wasn't the point of view from point-free topology is that the points become the models of the theory and then the topos has become this sort of universe loosely speaking in which these points live inside. Okay, so, all right. I also just want to highlight this particular interesting notion of the generic model which we've also seen before. So every single, well, classifying topos has a notion of a generic model or also known as a universal model. I think Olivia calls it a universal model. And this has characterized by this property that in any kind of model of this particular theory can be obtained as some sort of, obtained by the inverse image filter for some unique geometric morphism. And one of the important consequences of this is that any geometric sequence, a sequence of geometric construction that holds for this generic model will also hold for all the models of this particular theory. And so on the next slide, I am going to show you a picture which I have shamefully appropriated from Olivia's book, but it's in the bibliography, so I think it's okay. But anyway, it shows a very nice visual representation of what's going on for those of us who haven't seen this stuff before, that you here is the generic or the universal model and all the other models here in these other different shapes. So it corresponds to models that can be understood as applying the appropriate inverse image filter to the generic model. Okay, so that was the first theme and I want to talk about the second theme. And this is sort of the thing that we do as mathematicians to a great deal, where it's like we have a problem. It's very hard to solve and so what we do is we break the problem into many different pieces. We solve the problem from each of the small pieces and we put everything back together again. And it's a thing that cross-cuts many different areas of mathematics, but I just want to talk about it in the context of number theory. So, okay, here's a polynomial on the slide. And one can, you know, it's a simple question to ask, what are the rational or the integer solutions to this particular polynomial? And in general, because, well, there isn't a lot of structure on the integers or the rationals. This is quite hard to deal with. But, you know, here are a couple of observations that have guided much the development of diaphragm geometry. So first thing first, if you have an integer solution, obviously this implies that we have a real solution and also more P solutions. In fact, pietic solutions, right? And if we look at the real and pietic solutions, these are easier to check than just the integer or rational solutions. So let me just say quickly for the real solutions, you know, well, you have a polynomial. If you can just check the signs, then you're pretty much done because, you know, if you plug in a number, you get a negative solution, you plug in the number, you get a positive solution, but the intermediate value theorem, you know there's something in between. And so, of course, this algorithm says that, well, you have a real solution, but it doesn't tell you the necessary integer, but it shows you in some sense how it's easier to check, well, to check for solutions over these richer geometric situations than the case of the integers or the rationals. And so this poses sort of a new question. So like given a polynomial with rational coefficients, like, does knowledge about its pietic real solutions give us some information about its rational solutions? And, well, this sort of suggests something which I'm going to frame in a very general sense, which is some kind of local global principle that basically what we're asking, right, one direction of this principle is obvious, right? That if something is true for the rationals, it ought to be true for its completions as well, but we're interested in the other direction as well. So when does it existence the solutions over the completions of the rationals and so this sort of motive explanation via del ring here. So like the local global principle says that, okay, it's this particular principle right here. And this thing doesn't always hold, like in certain kinds of polynomials it's true. Like for example, in the quadratic forms, but in other cases, like due to work by Selma, there are examples of polynomials where this is not true, but even then it's a useful thing to try and reason about what is true or what holds for all completions of q. And, you know, it's not true, it's not true, it's not true. So this is a simple principle that we call completions of q. And the adoring is well classically defined as some sort of restricted product of all the completions, but morally it's a way of trying to reason about all these completions simultaneously. And so just recall what we said from the previous slides about the generic model. So the idea, the starting point of our research project was sort of thinking well, how about instead of thinking about reasoning about properties that hold simultaneously for all the completions, we reason about what holds for the generic completion. And then we go from there. And so, it's just sort of a suggestive quote. I'm just going to, well, this is a quote from an accident survey by Barry Mazer. And he says that, well, a major theme in the development of number theory has been to try and bring somewhat more in line with the periodic fields. And a major mystery is why resist this attempts is strenuously. And we saw echoes of this during Schultz's talk where he was talking about how, you know, the liquid tensor experiment is not locally profite, which causes a lot of issues and a lot of technical adjustments that needed to be made in order to bring, you know, some of the condensed analysis to bear on, in the case of R. All right. Exploration begins now. So let me just start talking about what we're doing. So I said that we want to think about the completions of Q, right? We want to think about what these things are and what the generic completions might look like. But what exactly is a completion? Well, we have a notion of distance, right? That's a metric, if you like, that's defined on the rationals. And we define, and these are, well, these notions of distance, these notions of metrics have to satisfy these basic conditions. So, right, it has to be non-negative. It has to be multiplicative. And it has to respect some notion of the triangle inequality. So these are fairly standard notions from undergraduate real analysis. And what's interesting is that we're not interested in just every single kind of completions, but up to some notion of equivalence. So we define a place as an equivalence class of absolute values, where two absolute values are equivalent if there exists some alpha from this interval, such that if you exponentiate, they're basically equal with respect to this particular relationship. And as it turns out, if two absolute values belong to the same place, then it turns out that they, when you complete them, they yield topologically isomorphic completions. So this is why this notion of places is an interesting one. And so before we start talking about what the generic completion is, we want to understand what the generic places. And so intuitively, what does this topos look like? So, right, the first few slides, we're trying to tell you about how we should think about the points of the topos or the models of this topos. We want to basically be equivalence classes in some sense, right? That any two absolute values belonging to the same equivalence class ought to obey this particular relationship. And so we're interested in this particular, well, as a starting point, it's interesting to think about this diagram as a starting point. So Pi in this case is a projection map, which, okay, AV is basically the classifying topos of the geometric theory of absolute values. And if you're wondering whether the theory of absolute values can be cast in geometric terms, the answer is yes, so let's just go with this. And so you have an absolute value here and you have some exponent here. And the projection map just sort of forgets what's happening in the second tuple right here. But the exponential map is saying that, well, I actually want to exponentiate this. And what we would like to do is basically quotient by this sort of equivalence relation, right? But before we even do that, we need a notion that this is actually, this exponentiation map actually is a geometric morphism and that this is a well-defined diagram of toposes. And so let me just quote a quick result that we've done recently that's on the archive. So this is where a geometrical point-free construction of real exponentiation is helpful. So if we can define, do a geometric construction of exponentiation that here's the geometric logic and sort of by the reasoning that we showed in one of the previous slides, this also massively because continuity equals geometricity by the universal property of the classifying toposes. This corresponds to a map that we can use to build our diagram of toposes. All right. So let me just sort of return to this picture. So we said that we want the points of this topos to be equivalence classes of a particular kind, right? So actually we also, right, there's sort of an algebraic action here, right? If I exponentiate this absolute value with the specs of one, I want to get back the same thing and I want them to compose in this obvious way. So it seems that we want to quotient, right, just to, well, we want to quotient this topos by an algebraic action. The question is what is the appropriate quotient in construction here? And the answer is that, well, if the action is reversible, then we're going to use what I'm going to call the standard descent construction. And if it's not reversible, then I'm going to use the lax descent construction. And so, all right, I've been painting fairly broad brush strokes, but if you don't absorb all the details of the next two slides, don't worry, but let me just try and say something a little bit more formal. So suppose I have a truncated simplisher topos, right? Where all the maps here are, well, between these toposes sort of commute up to some sort of coherent isomorphism. And really what these simplificial identities sort of encode is basically the algebraic properties that I listed as desired algebraic properties on the previous slide. And so in the case of standard descent, you know, well, in the case you have a topological group or you have a space of objects in your space of arrows, right? And in the case, because it's a group, we know that all the arrows are invertible. And so, all right, we can define by some sort of nerve construction, some kind of simplisher topos. And we're just going to, when I say two truncated, there should be, you know, E0, E0, E2, E3, E4, but I'm just concentrating at E0, E1, E2. So that's why I mean by two truncated. And through work of people like Murdike, we can construct a descent topos. And explicitly, what are the objects of this particular category? Well, it's a sheaf of G0 plus some sort of action map, right? And the action map exists in G1. And this is necessarily invertible because, well, as we said, the group what has all the arrows are invertible because we're dealing with a groupoid. And it satisfies some special conditions known as the unit in the co-cycle conditions. In the case of lax descent, where we don't necessarily have invertible arrows, then what we have is, well, we can do a similar construction, right? And the objects, again, is some sort of sheaf. The lax descent category has as objects some pairs, which are sheaves of E0 and also some sort of action map. But the thing is that we don't require that data, the action map, be invertible. And so this sort of interesting distinction sort of gives us a very, well, an interesting perspective on the different notions of quotienting that might exist in the context of topos theory as generalized spaces. All right, so just sort of plugging in the various relevant details here. So this suggests this particular picture. So I'm going to, this is a word of warning. I'm going to suppress the sheaf notation, the S, this is what you see here. I'm going to suppress it for the ease of readability, but they really should be there in the subsequent slides. But this is just to put something on the slide so that everybody can look at, that we are applying the same recipe, the recipe suggested in the previous slides to our context. And what we're interested in is getting and obtaining a good explicit description of this universal code kind of this diagram of topos is. But this is the global picture. And it might be really, it looks kind of tricky to deal with. So maybe one thing we can do is just sort of break it down into like local pieces and see what we can do with this. So this, the way to do this is suggested by Ostrowski's theorem, which says that every single absolute value of the rational is equivalent to some notion, some kind of non-archimedean Piati absolute value for some prime P, or the Archimedean or the Euclidean absolute value. And you might wonder if you're constructively minded, is this a, we know that this is true classically, is this true constructively and geometrically as well and the answer is yes. So this forms a valid organizing principle for how we're going to proceed with our plan of attack. So let's start with the non-archimedean place. So already I've made some simplifications, right? So in this case, instead of, so for any non-archimedean absolute value is determined, and this comes out of the, well, the analysis from Ostrowski's theorem that is uniquely determined by where it stands the prime P and this lives in this particular open interval zero to one. So that's why I've replaced this here. And for any non-archimedean absolute value, because of the ultrametric inequality, the exponentiating to alpha for any alpha from zero to infinity still use a non-archimedean absolute value. It was only in the case of the Archimedean case where exponentiating to something that's greater than one use something that violates the triangle inequality. So in this case, we have a greater level of flexibility and we do in fact get some sort of group action. All right, which is established like what is D? Well, D trivializes. So basically everything is set. And all right, I'm not going to go through the technical details of the proof. I'm just going to show you some pictures and hopefully this works. But basically, all right, the crux move for this is basically just note that the connected components of the sheaves, well, we already know that these things are locally homomorphic to zero one, right? And sort of hinted at by this sort of different perspectives we can understand as sheaves as, you know, a local homomorphism but actually the send data actually imposes very strong conditions and this basically forces everything to be homomorphic. And so once you've realized this, then this, well, you can use this for leverage to prove that actually the category of descent data really does, you know, trivialize and give and is equivalent to set. So what about the Archimedean place? So in the case of Archimedean place, the setup is slightly different. So any Archimedean absolute value is equivalent to well, the Euclidean absolute value raised to some power of alpha from zero to one. But in this case, notice that it's stuck between zero and to one and anything greater than one is not well defined. So I've made the appropriate adjustments here. And also the space of this is where monoidal stuff comes in. So like the space of Archimedean absolute values is acted upon by a monoid action as opposed to a group action. So in particular, it's not invertible. And so, well, we had an interesting, I showed you a picture in the previous slide about what's it happens in the non-Archimedean case. Can we play the same game as we did in the Archimedean case? And here's the big surprise. The answer is no. And so, okay, I'm going to show you some pictures and we'll see if this works. So we said that shoes can be understood as local homomorphisms. And here is a particular type of local homomorphism that does, that exists over zero one. And it turns out that this is compatible with the lax descent data. And so what's in previously that the standard descent data is, you know, it basically flattens everything. You don't, you just basically get a homomorphic homomorphism if you have a connected component of the shoes in the case of the lax descent data is much more forgiving and forking phenomena is allowed to persist. And so, all right. This is just a quick exercise, but I think I'm running out of time on it. Okay, so I'm going to skip this, but basically this is the idea of like how crazy can the forking phenomena get. And, well, this type of forking phenomena is eliminated because of how she's understood as fiber-wise discrete spaces, but let me just skip that for now. So the insight comes in is that we have, I've said before about how we have a geometric theory of Dedekin reels, but we can also forget the left Dedekin section. So this gives us the theory of upper reels and we're going to denote zero one as the space of upper reels living between zero and one. And, okay, I'm running out of time, so I don't really have time to go through some of the technical details, but basically the purpose of this particular slide is to say that we have a particular lifting lemma that says that there's a canonical way of extending sheaves that are selected by the lax descent category to the sheaves living over zero one of the upper reels. And this is essentially being proved by Steve and myself, but there's still some constructive details that need finessing. So, okay. Right. The purpose of this is also just to say that this forking phenomena actually gives us a very interesting insight into what exactly this lax descent data is doing. So in the case of the descent data, standard descent, all this potentially unruly forking behavior is completely flattened. Whereas in the case of lax descent, globally forking phenomena still might persist, but as you know, through verifying this claim locally, well, local forking phenomena is actually eliminated. So this gives an interesting sense of contrast between the standard descent story and the lax descent story that mirrors some notion of, well, global stability versus local stability. And so here's, I said it was a bit of a surprise as to what this candidate, so the candidate picture is this, and I haven't proved, we haven't proved this yet, but I've given you some indications about how the Archimedean place is not trivial, right? Through this language of forking phenomena, why is this surprising? Well, out of Keelow geometry sort of guided by this fundamental analogy between, you know, the point and affinity living on the projective line and the Archimedean place of the rationales. And this sort of suggests that, you know, really, really should be thinking about the situation as some sort of one point compactification. But that's not what this lax descent data seems to be indicating here. So our candidate picture sort of suggests that there's some kind of blurring going on at infinity. And the infinity is not just some sort of classical point with no intrinsic structure. Okay. I don't have time. The point of this slide is just basically to say that I'm thinking about some seriously and about some of the potential connections between my work and homotopy theory. And, well, here's a particular pullback square and it's just interesting to think about. It's called the Chasa square, which is well suggested, but misleading for pretty much the same reason that there should be the Archimedean place there, the Archimedean completion there. But it's kind of difficult to figure out how to incorporate this in. And ideas from our previous calculations might give us some interesting insights about how to do this. Okay. So let me just very quickly conclude here. So what have I shown you? I've told you about two different themes, right? Continuity equals geometricity. I also said something about local global issues and how generic reasoning sort of allows us to have these two themes engage in dialogue with one another. And that through our analysis, we can see that the two themes are very similar in terms of the relationship between the two themes. And the other themes are very similar in terms of the relationship between the two themes. So I will just say that pulling away from the set, they reveal some very interesting insights between the relationship between topology and algebra. And that descent and lack of descent gives us an interesting understanding of what it means to quotient these poplices as generalized spaces. And that lack of descent sort of indicates some kind of blurring going on in our picture. And so much more careful thought is needed and about how to


What is going on guys welcome back to the channel critical overlord here so in this video I'm just gonna kind of share my thoughts and something. I've been thinking about for quite some time actually for several years now I Know I'm not the first person to probably Share a video like this or the first person to come up with this idea But I just want to put my thoughts out there since I have subscribers And I know you guys want to hear my thoughts on screen and I know for those of you who have subscribed to me for Jeepers Creepers content. I'm sorry the content for Jeepers Creepers has been slimmer again I do have a new job at the moment So I've been working a lot but for Jeepers Creepers content I'm still trying to just do character videos so comment down below any characters You want me to make a video on and I will do that but get getting on into the video as you can see from the title of Does or did Sydney Prescott or does she have a secret child that she gave up for adoption? After the events of the original screen now for those of you who are fans of the series, you know that in the original screen Sydney Prescott found out that her boyfriend Billy Loomis killed her mother as well as his partner his best friend stew They collaborated to kill Sydney's mother and the reasoning for that was because Sydney's mother was the reason for Billy's mom Leaving the household because Billy's father was having an affair with Sydney's mom and I can only imagine how Heartbreak and that would be to find out that the reason why the love of your life or your first love the first woman You ever love your mother the reason she left is because of something regarding your girlfriend's parents That's that's kind of hard to deal with I kind of do sympathizing sort of ways with that character of Billy Loomis No excusing his actions though, but anyway, you know that that's what the issue was in the first film now In between the first and the second film there's like a two-year gap What I am believing and what I have always thought for quite some time is that somewhere Down the road Sydney Prescott gave birth to a child because there is a sex scene that occurs between herself and Billy Loomis in the original screen where she is losing her virginity to him And I'm pretty confident and I do believe Sydney Prescott was pregnant I do believe her and her father left left Woodsboro for some time after the events of the original film And after Sydney had the baby, I'm willing to bet that that's when they just decided to go back to Woodsboro Now, of course, the only two people that know about this would be Or three people would be Sydney her father and the baby who was now all grown up and now once revenge That's my that's gonna be in the next bit. I'm saying that I think that the child of Sydney Prescott a secret child I believe that Would be one potential route to take for screen five now that is very similar. Yes to Roman Bridger and the secret brother however regardless of Regardless of the Roman Bridger aspect I feel like a secret child wouldn't be too out of the realm because Billy and Sydney clearly had sex There could have been consequences for that that were not addressed at all in screen two three and four now a lot of People will say well, why didn't Sydney ever mention this?  She didn't mention it out of shame. I wouldn't I would everybody does things for certain reasons Sydney Sydney probably didn't mention it out of shame that she was ashamed to have been pregnant by that guy and she wanted to go and leave town and Her father she told her father her father kept it a secret. They both agreed to leave town They settled down for a bit while Sydney went through that whole ordeal Sydney gave birth and the baby was given up for adoption and they left town now How did no one find out? Well, like I said before they left town So to argue that how did no one find out about this is kind of silly because if they left town Who knows what they who knows what they did and maybe maybe they wanted their own space Maybe they maybe Sydney had some like some time off from everyone in Woodsboro Maybe they only saw or had contact with Sydney through phone contact. I'm I'm pretty confident that Sydney Prescott did have a baby. She gave it up for adoption and That is probably gonna be one of the potential routes that they consider for screen five now another interesting thing I do want to talk about in this theory of mine is that the baby would have a sidekick and that sidekick would be the person who actually discovered the baby and taught it about Sydney Talked the baby about its true roots. It's true mother Kind of sim it still sent very similar to Roman again I would rather they not take this route, but it could be the baby the secret child of Sydney and then a partner in crime being another being another Loomis relative I'm thinking I'm leaning more towards Hank Loomis and maybe something to that sort of effect or Or Maybe we find out Something else in regards to the Loomis the Loomis bloodline and that whole ordeal, but I'm thinking right now One of the potential routes they could take in screen five is making hating pants years character of Kirby alive She'd be the focal point. She's in college similar to screen to give it the screen to treatment somewhat use the Use the college setting again, of course. I know that's been done before but Whatever how the Halloween franchise is always taking place in Haddonfield. So this is still just one little thing But yes, have have the film revolve around Kirby Kirby has a has a group of classmates that she's now become connected to or connected with In screen five the new killings could be sparked by a reboot of the film stab Which is the film series based on the killings in Woodsboro in the screen franchise and then have the Have one of Kirby's friends turn out to be that secret child of sydney I could see something like that playing out and I think that's something that could potentially work of I think they could do it. I really think they could I feel like there is a way they could do that. That's something that I would like to see now Of course, they could make it more interesting by then bringing in another Loomis another Loomis relative or something of that effect or giving this This secret child some very sad background and making us feel for the character There's several things they could do to make this come full circle all the way back to the Loomis debacle that started with uh sydney's mother and then Just have it be. I don't know. I just don't I don't really want this film to be if it is screen five because we still don't know if it's going to be a sequel or not, but I don't want this film to be Something that is taking a narrative with these two with these original characters and not tying it back around to the beginning So if it's not going to be sydney as the killer Somebody else needs to be connected to sydney. Something has to be done here Something has to be done that takes us back to the beginning. That's what I would like to see for screen five Let me know what you guys think about this theory down in the comment section below add on to it If you would like to if you haven't already make sure you subscribe and turn on post notifications So you never miss a video in the description. I'll have links on my social media accounts on my facebook twitter and instagram You can message me there to let me know if there's any movies news or reviews You'd like me to cover in the future with all that in mind guys. I will see you in the next video


This article discusses the use of emojis as a way to visually represent poetry. It explains how the emoji maker platform allows for the creation of a new model of digital presentation of fiction, specifically focusing on the psychophysiological characteristics of the lyrical protagonist. This model uses emojis to express the emotions and moods of the protagonist, allowing readers to interpret the text through a visual iconic sign, smile. This article was authored by Ruzudan K. Makhachashvili, Svetlana Ikovpik, Anna O. Bakhtina, and others.


I'd like to introduce Mason Egger who's here to talk about continuous deployment of documentation. Take it away. Awesome. Thank you, Jeremy. Hey, everybody have a good lunch? Yeah. Yeah? It's pretty good. Let's give the PyTexas organizers a round of applause for that. Awesome. So this is my talk, Building Docs Like Code, Continuous Integration for Documentation. This is my first time giving this talk as a talk. This is usually a very angry rant whenever docs don't work the way I think they should so I have to like make it more professional and more good for a professional audience. So I'm Mason Egger and here we go. So quick, who am I? I'm a site reliability engineer on the cloud platform team at HomeAway. We're based out of Austin that we have a downtown office and a north office in the domain that I work at. I'm also a volunteer educator with a program called TEALS. It is a Microsoft philanthropy that pairs industry professionals with teachers that may not have traditional computer science backgrounds but are being forced to teach this class inside of the classrooms because they don't have access to, you know, the knowledge that people want their kids to learn this stuff. So if you're interested in that at all, feel free to come and talk to me at any time during the conference. I love talking about that. And as anyone on my team has ever been able to tell you, if you ever ask, I'm a documentation fanatic. I very much think that bad docs are the reason why we have bad code. So we're going to talk about how to have good docs. So who is this talk for? This talk is for pretty much everybody, but this is a good talk for open source maintainers, junior and senior level developers, program and project community managers, DevOps engineers, educators. The list goes on and on. The TLDR of that is anyone who writes, maintains or manages a product that they intend to share with someone else, this talk is for you. So Act 1, the conflict arises. How we manage our documentation. So a common approach to the way we manage our documentation. And it's a tale as old as time. There's a developer sitting up at his desk at 2 a.m. in the morning banging out some code. The developer writes the code, the developer becomes happy with said code and commits the code to a version control system. And then once he is happy with it, he sends it off to his coworkers and they do reviews and tests. And then we come around to this decision. Is it time to release this code? Well, if it's not, the developer rejoices, goes back to writing code because that's what developers like to do. They like to write code. If it actually is time to release the documentation, they've grown internally.  So now we're doing that. Someone could be the actual developer themselves. It could be a technical writer if your company is lucky enough to have technical writers. I have worked with some. They're amazing. But that was my last job. My current job does not have technical writers on staff. It could even be a different developer, a new hire or an intern. Because I have seen common things before. It's like, oh, you're the new guy. Go write the docs, which is a terrible idea. And we'll get to that later. Issues with this approach. The documentation in this approach is almost an afterthought. Your code is great and you need to tell people that your code is great. And if it's an afterthought, you're not really getting, you're not optimizing that. There are long release cycles where things can be forgotten. We all try to do agile methodology, most of us. Two-week sprints, iterative release, blah, blah, blah, blah. All that stuff that we say we do, but we don't actually do. But I worked with it. My first job was at a company where we shipped a physical hardware device every six to eight months. There was no iterative development on that. I didn't get up every two weeks at the end of my sprint and go, OK, let's ship a thousand more blade servers. It didn't work that way. So I would get to the end of a development process, eight months down the road, and they come and ask me about something I wrote on day one. And I'm like, oh, I don't remember how that works at all. Let me go look at the code. And then we're in this really vicious cycle. The more layers of separation between the implementer of the code and the author, the more likely you're already get for an accurate docs. Technical writers are great, but they didn't write the code. Like, they don't know all of the nuances of it, so they're likely to get some mistakes on it, especially if you're not working with them to help them get the code, get the docs right. And one of the issues approach with this is that the developer dislikes documenting. And that's actually a really big problem. Like, why is developers do we not like documentation? Like, why don't we like it? Developers enjoy writing code. Developers enjoy talking about their code. So why don't we like writing about the things that we're talking to all of our buddies about? It doesn't really make sense. So the real issue here isn't that developers don't like writing documentation. The issue is, is what they dislike is the workflow that we have enforced upon them to write their documentation. A developer has a very finite or very nuanced workflow that they like performing. They like writing their code in VEM or VS code, committing it to get, testing it on their laptop and all of that. But every time we ask them to document something, we make them break this workflow. We make them context switch out of their preferred environment to go use somebody's clunky UI, some, you know, amazing what you see is what you get editor that actually is not what you see is what you get. And then, or that also has a search feature that I would be better off asking dev you random for a result than actually the search feature working. So how can we integrate our documentation process into a workflow that developers will enjoy? What if we treat our docs like code? You know, the Occam's razor in the room would be if developers like writing code, then why don't we just make the docs code? What if we have our docs living, instead of living externally to our code, they live right alongside it, whether this be in the same exact repository as the code or in the same, perhaps, GitHub organization as the code for maybe long-form docs or different types of docs. And what if we used a markup language or a markdown language that developers already know that they've been using forever that is, you know, way better than what you see is what you get and doesn't add an extra level of complexity so even like new technical writers who may have never used markdown before could actually use it because it's relatively simple to use. So let's treat the docs like code. What do we mean when we say treat docs like code? Docs source files are stored inside of the version control system, which means if you were using Git or Mercurial or anything, all of your docs live alongside it to get a Git clone from my docs to Git clone from my source code. We build the docs, the document artifacts automatically. Documentation is just as much of deliverable as your wheel file is or as your executable or any of that things. Docs are artifacts and they should be treated as such. Ensure a trusted set of reviewers meticulously reviews the code. We spend hours doing code reviews to make sure that we don't accidentally break our code base, but we don't spend hours reviewing our docs to make sure that we don't hand off our code to somebody else to make sure that they don't break their entire system because we didn't document it properly. Why is that? We also have to make sure that our docs are tested both for accuracy and for functionality. There is nothing I hate more in the world than going and doing an example from a documentation and then trying to type it out and then it doesn't work because it's wrong. The source code in the docs wasn't correct. So accuracy for it doesn't actually work and functionality, do all of my web pages render correctly, do all of my links, if I have hyperlinks in there, do they all resolve to an actual place? We should be testing our docs for all of these. And we should be publishing our docs without much human intervention. We have CI-CD pipelines for build artifacts. We should be using all of these to also publish our docs to our web pages, to our wikis, or wherever you want to post your docs, we should be doing this also. What do we gain from this? It promotes collaboration, which is a great thing because not only are we writing our docs for our customers, or we're writing our code in our docs for our customers, we are now writing them with our customers. If, you know, maybe we're not the greatest at English or we don't have like a degree in education and know how proper things need to flow to make it where the docs are understandable, but maybe one of our users does. And they want to, you know, submit a PR and fix the docs for us. Hey, that's great. That's work I didn't have to do. I love work that I don't have to do. I never do work I don't have to do. Okay? You can ask my boss. I'm really good at it, you know. I think there was the old Linus Torvalds quote, is that, you know, intelligence is the ability to appear to be doing nothing, but yet still getting everything done. You know, it's often working at this morning is often a very first step for somebody to collaborate into an open source project. So if we have our docs out there, we're more likely to maybe start fostering more open source contributions into our projects because we have our docs in there. We can track documentation mistakes as bugs.  Don't go look for it, it's awful. The open BSD community treats every bug in their documentation or the lack of documentation as nothing less than a critical or a P2 bug. And that's how we should be treating incorrect docs. We treat code, you know, if my code loses me all that money that it did in one of our talks earlier, that's a pretty big bug, but if that was an on-off switch and we improperly mislabeled the on-off switch in the docs and, you know, we cost everybody else to lose it, that's the same level of bug We include docs in our code reviews. This is actually really nice because, you know, you write a new feature and you write the docs, and when you're reviewing the code, you can review the docs, and it just, you know, you now have more sets of eyes on the documentation. It allows us to make our docs more beautiful. We have all these wonderful static site generators like Sphinx and MK docs and all of these other things that can make wonderful documentation where I know that most of y'all probably don't have art degrees and you don't like dealing with how things look so let somebody else do that. We have tools that can do this for us. It allows us to leverage our current workflows that we already have. We have amazing workflows for building, you know, software, agile process and all of this. Now we can apply all of these same workflows to our docs and it empowers the developers to document. If the documentation is closer to the source code, I have found that the developer is like 10 times more likely to actually edit it. And I have a case study for this that we did at HomeAway. I guess a case study and, you know, they were my guinea pigs. It's kind of a six-in-one-and-a-half dozen and another. There was a new team that was formed at HomeAway to build a brand new product. It was inside of my organization. We had a new GitHub org, new team members and everything. The first thing I added to that org because I was on this team was a base documentation repo that was allowed us to do all of our long-form docs, all of our architecture decisions, all of our readme's, all of our how-tos getting started all in this repository. Throughout the entire time that this project was active, these docs were the most up-to-date and well-maintained in the entire department. They were giving retrospectives every week, every two weeks at the end of our agile process and they had new docs every two weeks. Whereas another team that I was also working with at the time updated their docs every six months, every quarter, you know, basically whenever the boss yelled about it because he couldn't give it to somebody else, that's when the docs got updated. I've seen it work where people will actually work on the docs more because they're already in there. They're already in their Git repository. They're already in their source code and their code editors, I use them personally. And it's not that difficult just to open up the file and change it real quick and then commit it with your source. So how does this change the workflow that we currently saw earlier? So now the developer writes code and docs. The developer commits the code and the new docs to the repository. The code reviews, code reviews and testing and docs reviews, we get all of that same stuff. Same process. Is it time for a release? No, haha, hooray, I'm back to writing code. And if it's yes, the artifacts are published and the developer never has to go to that side of the screen. It's that side because I can't do things in reverse. So they never go over there anymore. We don't ever have to worry about taking them out of the process for writing code because all of that process of publishing them and building them and all of that has become automated for us. So act two, a hero emerges. Who can tell that I'm excited for Avengers? Anybody? Yeah. So CICD for documentation. Quick definition for those person people in the room. Continuous integration means that code is continuously tested, integrated with other code, changes and merge. Continuous deployment means that code is continuously deployed with each patch to the entire code base. This is very similar. You do the same thing with your docs. Your docs would be continuously tested. Your docs would also be continuously deployed. What does this mean for docs though? It's a little bit different. It means that every time that we do a patch, we are building a full version of our entire documentation. So if you have like a whole giant web page that posts all of your API docs, you would build this web page every time that you build the patch. You are continually testing the content with each patch. And there are some pretty interesting documentation testing tools that you can do with this. Or you also, if you have technical writers, they will be able to review this and actually read it for you. You are publishing automatically with every release.  This is probably the most important thing you have to do. If I am using, you know, my library version 1.0 and my library version 2.0, but the only docs that you publish for my library docs, oh, I don't know which version I'm using. I think that's my favorite part, like read the docs because it has the little version checker in the bottom. That is the best part of it. I mean, there's probably a lot of other amazing parts, but I like that part. So a quick introduction to just two different types of documentation because I saw a talk similar to this once and didn't know this. There's two or three major forms of documentation you'll deal with, long form documentation, which is user guides, getting started, FAQs, all of those things. These are the kind of docs that will live in a separate repository inside of your organization. Like these necessarily don't live in the same exact repo as your code base because they really aren't tied to code. This is really more of an overview of the product, maybe an architecture decision, things like that. Then we have the functional documentation, which is the documentation that actually lives inside of your code base, inside the same repo. And these are RESTful APIs, SDKs, man pages, things like that. Those are the code that you would see, the PyDoc, the inside of Python, you would see your documentation above it. That's the kind of documentation this is talking about. So we have some really amazing documentation tools that can help us with this. There's three different types that I've kind of roughly classified. There are static site generators. These are the ones that are good for your long form documentation, your FAQs, your runbooks, all of those things. Your source code base documentation generators, docs that live inside the code, PyDoc, JavaDoc, the source code that, basically annotations, code annotations for your documentation. Some even generate clients for testing, like Swagger, if you've ever used the REST API document editor, Swagger, you can actually generate tests on your docs based on this. It's really cool. And then I put in system documentation generators because I found a really cool package called RON, which is a markdown based man page generator. And I think the name is hilarious because the markdown format is raw and it's raw and it's the opposite. I think we're mostly with people I was talking with last night. Every single name of every package in the computer science is a developer laughing at his own inside joke. So that's all that is. I thought it was hilarious the first time I did it, the first time I saw it. And it gets less and less funny every time and that's exactly how that joke should go. First tool I'm going to talk about real quick is MKDocs, since this is the static site generator type of documentation. These are markdown based documentation with a YAML based config file, relatively straightforward. The time to hello world on this is probably about 30 seconds. Like to get a working running implementation of this, it is insanely simple. We use MKDocs a lot at HomeAway for our long form documentation because the developers at HomeAway really like markdown and all I do is write markdown and then it gets out of their way. It is easy to configure. There are many different extensions and many different themes that are supported. It is Python based, so if you don't like any of those extensions or themes, you can easily extend your own. It just uses Genja 2 and some templating files. It's really all it does. I think one of my favorite parts about MKDocs and UML, and this is just a personal pet peeve of mine, is that you can now support flow charts and sequence diagrams with the right extension in markdown and it will actually render the flow chart and sequence diagram inside of your documentation. Because the amount of times that I go to an old page and like, okay, who made this diagram? Was it in Gliffy or did we use Google Docs? No, we used the other one, but who had it? Well, that was the guy that was here three years ago, but he quit and now he like, you know, heard sheep in Montana. We're never getting that thing filed back. So now I have to rebuild all of these diagrams. And I'm tired of that. I spent an entire night one time building a diagram for a meeting that we just happened to have tomorrow. So now I'm like, now it's in the source code. Everybody can edit it. We never lose track of these diagrams again. That was a personal pet peeve and a rant of mine. If I only get like two or three rants in this talk, it's going to be a good talk. So documentation tools, Sphinx. This one is another one of my personal favorites. I find it slightly more difficult than MKDocs, but that's because, you know, I think that markdown in YAML is really easy. It's restructured text-based tool that does support markdown. It's the most common tool for creating SDK documentation form and code documentation. I forgot to put in Python. So this is the one that most of you who've ever done a Python SDK or something, you very likely use Sphinx. It can out port to literally any form of media that you ever ask it to ever, including latex. People like, which one's harder? Sphinx or latex? Well, Sphinx writes latex, so it's obviously smarter than latex. And it might be censorship. I'm currently uncertain. I'll get back to you and I'll let you know. My favorite part of Sphinx is, and this is the extension they have for doc testing, which is where I can write the code inside of my, inside of my, or I can write source tests inside of my source code documentation, and I can actually run the tests on this documentation to ensure that the code that I put in my documentation accurately runs. And if it doesn't, this build will fail and it will say, hey, your code examples are wrong and you're lying to your users. And I love that because the amount of times that it won't, it will talk me on more occasion than one, so I'm not as good at this as I think I am. And it also catches my teammates and then they get angry at me and I just giggle. So it's hilarious. Just a quick thing, because I have to plug her on because it's such a hilarious tool. Markdown-based man pages, I think are awesome. As an assistant engineer, I enjoy and love man pages, so I'm just going to go with that one. So, Act 3, the final battle, where we have our demo. So here was the issue that I was trying to solve with the open-source project that I have started called Unlocked EDU. I need to be able to create many open-source texts all with a similar format that is production ready to go out of the box. I don't really want to worry about building the texts. I don't want to worry about what the format is or how the page looks. They should just appear.  I want a workflow that jump-starts doc-writers. And the secret one that I don't think I put on the slide is I've implemented this at every job I've ever worked at. I'm tired of re-implementing it every time because I implement it once and forget it. And then three years on the line I have to implement it again. So now I just open-sourced it and next time I go and get a new job we're going to have it ready to go. So my solution, the author will generate docs. The author writes docs. The author will publish his docs and then they're automatically published to a hosted solution. This is the workflow that I want to develop. So the tools that I chose to use this are cookie cutter. Cookie cutter, if you don't know, is a Python-based project generator. It is more often than not used to generate Python projects but it actually can generate anything you ask it to because that's what it does. A text editor, whatever you want to use to edit these actual source files.  So now let's see if the recorded demo will play today. It is. The first thing we're going to do is we're going to generate a docs pipeline with our cookie cutter. So this is the source repository for the cookie cutter that I have built. Everybody is able to go get it and I'll there will be a link to it at the end of the slides. So the first thing we do is we just run cookie cutter. It asks me if I want to redownload it because I've done this and it took me like seven tries to get this demo properly recorded where I didn't hate it. I fill in a little bit of boilerplate information. I fill in the name of it, the site repository. This is that description. This is what it has in GitHub. Apparently I decided to take time there. The site author. The GitHub username. This is to make the build badges work and things inside of the code. You can choose whatever license you want to license this under. That was just me being bored and enjoying open source licenses. You select your documentation engine, GitHub pages and what CI you want to use. So what did you get from this?  I use docker and make for almost everything. So if you don't end up having make on your system, you can use just choose the raw docker files. The thing I missed was the real quick configuration file. So this is just what the base docs look like. It's just a PyTex's demo boilerplate. How would I use this locally? I'm a slow type or sometimes. So the first thing you have to do with this, you have to lock your pip file because as I was doing this, there was a version of ginger that was out of date and it caused a security error in GitHub so I did it. So now you have to generate your own pip file. And then I do a make build and I have now built the docker container that I have to run all of this. And then I do a make run and I can go and view it on localhost and my docs automatically appear and now I have them ready to go. So if I want to edit this, I would just open the docs again and I would add some more text to it. Let me make run it again and we go over and we refresh and now we have, you know, PyTex is awesome. It's right there. It works pretty simply. Other thing you can use, I use something called Biobu which is basically just a fancy wrapper around Teamux. So I can actually leave this docker file running and constantly edit my docs on another screen. I'll get live updates on the other side as much as I want. So I don't have to constantly change the image, re-run, check my docs and do all that. So now I come over here. I've got my docker file running. I add woohoo with an exclamation mark. I'm bad at markdown so it went on the same line. So now I'm going to go fix that and I cut that part out of the demo apparently because I'm not good at editing. Set up your get repo and push. Just a quick little thing on, you know, make sure you give it the same name as you gave your project otherwise it's going to make Travis really unhappy with you. So we've pushed it up and we've likely detected our docs so we go to the build demo or the build badge icon that you get and you open it up and Travis is waiting and thinking and now Travis has detected it and my builds run really fast because that's the power of editing instead of making you sit here for a minute and a half build. Oh no, my build failed. That's not good. What happened there? I failed to deploy. What? I don't know. I trip over every time. I always forget to put my get hub token inside of Travis so I can actually access this and I actually tripped over this three times before I decided I wanted to put it in the demo so I was like if I'm failing on it this many times maybe everybody else would enjoy watching me fail at it too. So I go to my personal access tokens and I create a token for those of you that think you're going to grab this token it's already deleted. So I worked for a security company I know you don't lie to me. So then we just go in and then we add the get hub token as an environment variable in Travis it automatically says it won't display in the build log which is nice because the last thing you need is leaking credentials in build logs been there done that we restart the build it goes really fast because again on an amazing editor everybody's builds run that fast everybody would love it and then you go back to your repo and now this is automatically published on my personal get hub pages it actually just is completely continuous so I add another statement to it which would be I'm going to put one more time I did this a couple hours ago I still don't remember what I did we rebuild it it goes refresh it automatically works sometimes get hub pages is slow now we have a full automated process so I cut out the times me sitting there clicking refresh for like 20 seconds before it actually showed up and nope oh apparently if I hit the play button it starts over again let's go next can you try this yourself? the open source project that I created is called Unlocked EDU it's an open source project dedicated to creating free and open educational resources such as textbooks, curriculums, worksheets and stuff for use in public schools because as I'm a TEALS volunteer now I am finding out more and more that the availability of computer science curriculum for schools that does not cost an arm and a leg for schools to purchase is actually really low so this entire project is built around that all the books that I have built inside of this are built on markdown my brother and I are writing an AP computer science a Java book for this course and a couple of other things the cookie cutter is part of it so all of the systems code and stuff that I'm going to be building for this project will be open source along with the books themselves so you'll have access to them and you can just visit it here I'll put some stickers out on the table if you like that logo because I think it's a cool logo I've got a really cool graphic designer if they run out or if you want more I have plenty I bought a lot so sources that I use for this Docs Like Code is an amazing book if you are interested in this concept of actually being able to treat your Docs Like Code and get more examples inside of the book this is a great resource to use I did footnote a couple of times because I just shamelessly stole from this book but I cited it so it's not stealing it's research so that's how you do it it's a great book I highly recommend it final thoughts every job that I've ever implemented is workflow app both the developer experience and the user Docs have vastly improved it's been amazing how much better it is a short amount of time the Docs can get and the user experience can get stop making Docs as a punishment don't dump Docs on your intern because that's how you get terrible Docs they don't know what you did they don't know the architecture of the system but you want them to go out and write all these Docs like in reality the person who writes the Docs is the person who has to understand the software the most because you're trying to explain it to your users in a way that they can understand and you're not trying to make them drink from the water hose or the fire hose blow their face off so this is the third bullet is probably my favorite bullet if your Docs suck people will abandon your project if you had a lot of potential that died because they didn't they didn't do proper Docs nobody knew how to use their code and in the age of read me engineering where if it takes me more than an entire read me page to actually figure out how your stuff works I'm not going to spend that much time going into it to figure out what you actually did versioning Docs is great we should do a lot more of that we should do tons of that my slides will be they are already available on my website it's really easy to find I'm the easiest person on earth to find on the internet if you know my first and last name and luckily they're both five letters a piece so ten letters it's like a phone number and that's my twitter account if you want to see me tweet cats in useless crap that's where I go to do it how much time do I have left I have time for questions I will take questions fantastic I normally talk way too fast and that went great any questions I mean man everybody at my job said I wasn't going to hit it I said I was going to go over by ten minutes my question is related to public versus private doesn't define the difference in public and private methods but you only really want to document the public methods in an API so Sphinx has a built in thing I think it's called undock methods and you can say hey I don't want to document these methods inside of there so when you're laying out your restructure of text file you can say hey don't document these methods or only document these methods you can either be inclusive or exclusive and then that's the way you would do that alright I have no in for this so I take a small bow


Good morning, folks, Steve Rhodes coming to you live from the shores of sunny Delray Beach, Florida. This year, 11 a.m. uptake, and we have most of the US Indices trading the upside. The Dow is off 36, the other US Indices trading to the upside. S&P's up one point, NASDAQ three points, so they're basically flat. Russell's up 24 after poor day yesterday, Semi's are up 29.8, trend is up one to three tenths. That's 203. Gold's up 25 bucks, Silver's up 46 pennies, likes to recruit up a buck 19, natural gas up three pennies through the treasury, printed out at 12401, that is basically flat. Let's take a look at that nine panel, market update chart in the upper left-hand corner, you've got the ES mini, you do have a new profile. It's a bullish structure profile, support is between 43.94 and 4407, resistance up at the 44.46 level. Yesterday confirmed a sell the D point, a roadsman to indicator top. Yesterday was a four river evening star candle formation. So ideally, what price we'll do is go test support, that's between 43.94 and 4407. Now it's not going to test support. If the spot politics remains below its 50-day exponential moving average, that's where it's at right now. The level to be watching at day Zen is going to be 1550. Our price closes above that, odds favorite, get that move back towards that 43.94 level. In the case of the NQ, it also has a new profile, kind of hard to see. We'll take a look at it during the Trader's Edge show. But right down 14, 9, 69 is supporting 15258 as resistance, US dollar index. It does have a sell the D point, a Gartley sell pattern, prices back inside its profile. A close label of 102.28, we'll suggest a move to 101.76 to 101.93. Goldilocks, which has a, I should remember the bottom, a TD9 count bottom, I believe, is trying to get back inside its profile. The key level for Goldilocks is going to be 1943.90. That's the center of its bullish structured profile. If we can get a close above that, then we're looking, that's a bear structure profile. My apology. It's a bear structure profile in the sell zone range, is 1943 to 1956. So far right now, trading above the top of its daily profile. It's got a valid bottoming pattern as well. If we take a look like we've crude, if we can close today above 77 to 81, we should see move up to, I say 77, I mean 72.59, I'll get my numbers right, just to stay with me long enough. A close above 72.59 should get us up to 73.91. Folks, stay tuned for the Trader's Edge show. But if you have to start your Friday, please have a fantastic one. Thanks for joining us here. We'll look forward to speaking with you again. Take care now.


From Hollywood it's time now for Johnny dollar Sure sure you run that lunch room across the street from the warehouse that was robbed last night Yeah, that's right. Nothing as long as you weren't mixed up in it yourself. No.  I think I can take care of that. What do you know about it, Red? I see I'll have to sell out get away from this section. So I'll need some dough you follow me. All right I'll see you taking care of it. Now. Just what is it? No, I ain't safe. I'm talking from a booth You stay right there at your hotel. I'll see you in a half hour, right? Just you know cops Yeah Yeah, that's right. Mr. Beck. Mr. Big and six quarts of milk and two pounds of butter sure right away. Thanks, mr. Beck Hello Hello Tonight and every weekday night Bob Bailey in the transcribed adventures of the man with the action-packed expense account America's fabulous freelance insurance investigator yours truly Johnny dollar From special investigated Johnny dollar location Los Angeles, California to the home office mono guarantee insurance company Hartford, Connecticut Assignment the silver blue matter Expense account continued Item for 20 cents a phone call to my friend Lieutenant Garcia of the LA police and a call to Queen of the Angels Hospital Albert Crisman the night watchman who was slugged by the gang of teenage hoodlums during the warehouse robbery was still unconscious and Crisman unless Red Weller was ready to talk now was the only lead I had toward finding a hundred thousand dollars worth of silver blooming coats I Waited two hours and a half for Red Weller, but he didn't show Item five two dollars and eighty five cents taxi to the warehouse district at the south end of the railroad yards It was night by now and the area was almost deserted a lost lonely district shabby and worn even in the softening darkness and Haunted now by fear The only lights in the block with O'shining from the windows of the warehouse office and from Weller's lunch room across the street Good evening. What would you like sir cup of coffee? I guess? Just made some fresh good Would you like some cream? No, thanks? Is it foggy out? Yeah, a little not bad though Hey, this coffee is all right.  Thanks. The boss always has me make it when I'm here He says I do it better than he does. I'll bet you do Is the boss around by the way? No He called me and said he had to go out. That's why I'm working. I'm on in the daytime mostly You have any idea where he might be? No, no, he had to go somewhere. I guess What'd you want to see him about? He wanted to see me You know what he lives? Well, he's got an apartment over on Marina. It's about eight blocks from here. I think he'd be there No, he wasn't going home. He was going out somewhere. He acted kind of strange I Don't know what he was gonna do May I may I ask just what business you're in insurance? Oh? I'm a special investigator What do you mean? I'm working for the company that insured those furs The furs that were stolen the night before last from the warehouse across the street Something wrong. Oh, no, no, of course not. I I don't know what you mean. Oh Can I help you gather up that silver? Oh, no, no, that's all right Yeah, I don't know what happened. Just careless.  Well, yes.  What's your name? Carla? Alamante Why are you asking how long have you worked here Carla about a year? Do many teenagers hang out here? What do you mean kids 17 18 19 do many of them come in here for coffee hamburgers? Sometimes yeah I've never noticed much know any of them. No, no, no, I don't know any of their names. Are you sure I don't ask them their names Did I ask you your name dollar Johnny dollar? Well, I still didn't ask you if you want to tell me you What are you scared of Carla nothing I'm not scared you're not of course not Why would I be scared for the same reason your boss is red weller? He was scared when he talked to me this afternoon. I want to phone me later I don't know what you're talking about. Oh, yes, you do That's why he didn't come to my hotel. He was afraid to And why did you drop that silverware when I told you who I am because you're scared half to death? Oh, what's the matter with you people down here? What are you doing crawling into a hole because a half-grown gang of hoodlums starts throwing their weight around? You don't understand and suppose you tell me about it Do you think that's any kind of an answer in the long run? The puller covers up over your eyes and let them do as they please and just keep hoping they'll leave you alone All you're doing is making things worse. You don't know how it is You don't have to live here. No, no, I don't have to live here, but I know how it is Because I've seen it in other places where the mobs managed to take over and If you let it happen here, then you'll really have something to be scared of maybe Maybe they've already taken over.  No, they're not a mob yet, but they will be if they're not stopped It seems to me you'd have some sense of responsibility to them if nobody else maybe if other people had a sense of responsibility Kids wouldn't have to grow up in a place like this Have you ever thought of that mr. Dollar? Yeah, yeah, I've thought of it, but it doesn't hold water when you think so if you lived here All right, so it's a slum district and sure these kids start out with a strike on them But that's a pretty weak excuse for joining up at criminal bans and terrorizing a whole neighborhood for slugging people and looting warehouses Yes, I know most of them find other answers. It's only a small minority that turns to crime But if you let them get away with it others will join them and they'll grow until finally it's too late well, Carla Still nothing to tell me I Can't I Just can't I See There's a quarter for the coffee keep the change good night Carla Yeah Mr. Dollar suppose Suppose I I knew someone who might be able to help you I mean I mean who might know something about the robbery innocently of course if you talk to this person and They agreed to help you could you Well Could you keep them out of it depends on the circumstances? I do all I could that much. I promise Don't know. I'm not sure you're not sure of what of you Why I know better when I stop and think but I've lived in this neighborhood too long lived with these people and I'm bound by the law like any other citizen and I won't break it to help somebody cover up a criminal act But I figure it's up to me sometimes to decide whether a thing is a criminal act and if a person seems to deserve it Well, I could be pretty lenient You promise what you just said. Yes, I promise I've got to trust you. I've got to trust someone. Do you know such a person Carla? Yes, do you know where to find them? I think so Well, I'm sure they'll be at one of two or three places Not very far from here. And who is this person? someone who grew up around here a boy 19 what boy? my brother Expense account item seven two dollars and seventy cents taxi We went first to Carla's apartment where she lived with her brother But there was no one there then we checked out a drive in a few blocks away a teenage hangout. No luck Finally, we tried a pool hall down south of the yards just off Alameda Street. It was our last hope I know he comes here It's not a good place for him, but a lot of the other kids do too and he wants to belong Sure everybody does in one way or another gosh, it'd have been different if our folks had lived, but a Boy just won't take orders from his sister. Yeah, I know Thanks, he's not here then I just don't know where he There he is down near the corner the one with the dark curly hair all right Take it easy just tell him I'm a friend of yours. You want to talk to him or get him off to one side Whatever you say Eddie Well for the what are you doing here Carla? Eddie. Eddie. This is mr. Dollar a friend of mine We were I Wonder if we could talk to you for a moment. What about? Well, you know better than to come in a joint like this, but I want to talk to you Eddie I ain't talked to me at home man. Go on get her out of here with you mister It might be a good idea if you listen to her first. I thought it was her that wanted to talk to me Come on get her out of here. All right if you'll go with us For I like it here. It's a nice place Yeah, at least it's better than saying quit What are you talking about a warehouse robbery a hundred thousand dollars worth of furs? I understand you may know something about it innocently, of course, and I just had this guy was a friend of yours Well, that's right Eddie. He's just who is he he's an insurance investigator So that's the pitch.  You're not leaving, huh? All right, then I'll leave let him go. We can't force him to talk I don't understand Right I make ten cents phone call from the pool hall to Lieutenant Garcia at police headquarters He said there was no change in Albert Christman's condition yet. He was still holding on and he still hadn't talked But there had been another new development a big one and when I joined Kyle in the taxi outside. She knew it by the look on my face What's wrong mr. Dollar look How sure are you that your brother wasn't mixed up in that robbery? Well, I I want the truth I'm afraid he was mixed up in it then brace yourself Carla Your boss red-weller who was going to tell me what he knew about it Was found murdered in an alley an hour ago Now here's our star to tell you about tomorrow's intriguing episode of this week's story tomorrow I'll only broken-hearted girl a bloodstained shirt and a fight with a cornered rat Join us. Won't you yours truly Johnny dollar or is truly Johnny dollar starring Bob Bailey is Transcribed in Hollywood written by Les Crutchfield. It is produced and directed by Jack Johnstone Be sure to join us tomorrow night same time and station for the next exciting episode of yours truly Johnny dollar Roy Rowan speaking


been found and now it's time to go on the on the offensive You move it hostage and then you go. Yeah, you go fighting Uh You know most of the actual battles are pretty rote straightforward stuff just meant to set up battle plans like the fights throughout there It's a lot of back and forth. It's interesting enough Uh, cataclysm is shown to be like an excellent tactician Through like when he's fighting morons basically Like he's not sun zoo because he's fighting just like demented mad lunatics Um, the only the only chaos hero who was portrayed to have any brains in their head Is the dark oath war queen who they're clearly building up as a character because she survives the whole thing She's two campaign books. Yes. Yeah, she survived two campaign books now. Yeah, that's right and uh And so they like You know, there's It's like yes, cataclysm is really good at predicting how effectively like hordes of unthinking Mad men act is what it comes down to You know bite me in this canyon next to a river of like boiling metal or something Yeah, yeah, exactly and then and then a huge cliff that drops into you know into nowhere So but you know for the most part he's shown to have what it's it's interesting because he has a lot of like tactical prowess Lady olander gets chumped in there too. I don't remember her brings her down, but it's like um But somebody ends up uh Killing her off. Oh, it's belacor. Oh, that's right. Yep. You're right. It is belacor And Uh, I mean it doesn't matter. She comes back because you know it goes to reform but The interesting part is like cataclysm uses all these tactics and then he effectively has this big zanatos gambit Right where he's seeing how far in he can push before archion comes back and then like archion comes back and just Handles it just immediately There's no Like cataclysm the whole story is cataclysm being like very careful making these like really measured moves of like Choosing each battleground carefully aligning his forces. He has like false Fronts false retreats all over the place, right? Like he's portrayed to be very Tactical and he has to be to win Right because several times the sort of tide turns against him before he sort of brings it back But then archion comes in and does not bring tactics. He's just like nope.  That's it for that handled this So you're saying he marries Susan I mean archion is just he's portrayed to be this sort of unstoppable force of nature in there, right? Like Cataclysm sort of acts like a general would have to act and then archion just swoops in and is like nope I'm done with this. I'm done with all this nonsense. I'm chaos bitches. Yes He does have two red now so I can see that That's a really good point. It's a really good Yeah, once you once you have two red you're you're super good so Yeah Well, the mathematicians have come back on that one After a long time a call back in the business So, yeah, I mean overall it was cool because it did set up that now death has a a foothold In the eight points, right that they have this big unassailable fortress Um that you you do believe given it that even archion and his forces would have extreme difficulty assaulting um, and he would have to commit massive forces to to actually peel cataclysm back out of there And I like that Uh, you kind of get that you get some nice moments with cataclysm. You just see more of his character I think than anybody else is he's actually like the The protagonist of the story as it was. Yeah, right Yeah, I mean if after reading the description of the eight points in the war cry lore, um It is such a desolate and you know, uh blurred realm between You know the the realities the cal the calcification of magic Which is they're now the new realities and the realm of chaos And just to have death go in there just kind of sit there is is Cool. I mean, it's it's not the the typical Oh and the storm hosts have a by a shining bastion of light that the free folk will no no no It just places awful horrible. It's toxic death or it's killing you there's a statue that says memes all the time Talking again. It sounds just like mrs. Linnage voice I just like what that part of the story does too then to just give you that nudge of like where Where you want to place your games? So yeah, yeah playing versus chaos now You have rules for the eight points But now you've got that like you feel more part of what's going on If you're like, well now I can send my death army through the arcs terminus and go rampage into the eight points So that's yep a new cool thing that I wouldn't have you know thought to do in less You know games workshop told me I should right. I hope some people do pick up and use the the realm rules for Uh The realm rules for the eight points. I think it's a cool addition like a lot of tournaments use the realm rules I think it's perfectly usable Because the command ability basically will do or sign up the command ability the the spell does nothing If you're not using the the roaming spells or whatever. So who cares that's fine It's just that's just a non thing and you don't have to worry about it great The command ability is cool because it works with all in the spells and does a cool thing and more or less All of the realm abilities are really neat like there's one where All of the everybody can run in charge all the time Right, but if anybody runs in charges, they take d3 mortal wounds after the charge is resolved like what a cool Like that's a super cool, uh realm ability there Like uh, that's really interesting and how that works for the game. So Yeah, I I think that's cool. I like the eight points as a setting I like that we cracked it open that it's not just the realm of chaos because once that once the gate's open Like this you mentioned other people can come into now Right like narratively once it's not sort of this hegemonic control now. There's gaps because when too big You know things are fighting other people can then sneak around the edges a lot, right? Right, you can send fleshier courts through leeches and a gash. We'll go through now, right? Yeah, do any So I like all of that. Um I wish I we got a little more time actually just like with catacross not fighting just talking I like this sort of epilogue at the end because yeah, he walks into like a hall that has like 30 of his bodies Right and he's like keep at it. I'm gonna need more I'm gonna get splattered all over the place so many times in this in this campaign You know because he was sort of testing what archaeon was capable of basically Yeah, and chat mentioned that too that it hints that he wanted to see the full forest just to measure him Yes, uh, well, he was he did he he measured him real hard and then Right into the ground I was today days old when I learned how How hard he hits? Yes, exactly Uh, he got set back to his spawn point. He got hit so hard like He did he spawned Yeah, catacross is basically playing an mmo now at this point like he's invading and he He's gonna keep going until he dies and then can respawn Definitely as a raid boss. Yeah, absolutely. Yeah As someone who's desperately trying to paint night haunt for adepticon Uh, it did feel very motivating Just the the way they're portrayed in the story like they're Especially their initial assault. Oh, yeah Terrifying and overwhelming. I thought that was really cool.  I did dig that Stand ahead I do love how the cheater by the way on the cast side and the whole story is a gaunt summoner of zinch Who's just floating around causing problems all time and as soon as he sees the fortress is lost He like takes his silver tower and bounces. He's like This is lost. Bye Everybody else has to die but nope not that dude as usual they end up being the bad guys So, yeah, um overall, I think this book is is really worth it. I'm super happy with this Uh, obviously I play a lot of different chaos armies. So this has like a high value to to me because I have everything except nergal It's this video. Yeah. Yeah, exactly. This is this is very much written for me Uh, but I'd love to see another one of these Um, you know come like q3 or something. I think that'd be great I would actually it's clearly going to be destruction Sure fine with that Is that a prediction? Do we have a mean? I mean, it's just logic Because uh, we've had like an order release with firestorm We had malign portons. We had a death campaign focus and now we've had The all points basically which is mostly chaos focused.  I'd love if he got that and like he he was like, you know what azer's not worth it I'm just busting through the all points. We're getting into this. Look at all these lads. There's lots of good crumping over here Let's go.  Let's do this. Yeah in the yellow then They hold their their they Uh hold their gate that connects to the all right Like destruction holds their gate to the realm of uh beast or whatever Right, but that's not what we're talking about. No, I understand We're talking about like because like what's better than the green tide and by invading like a realm It's invading all of them. Yeah, I get it like them pull it pouring into the all points and then just spilling into all the Yeah, like running through the gates like scooby-doo in the old cartoons when they would go like door to door It's just them running that ram from like out of gir and then over into Into hi-ish and then coming out a different portal and then running back into wil-gu and then over into shai-ish They're just like just start that music as they go back and forth. Yep. Yeah. Yep Excellent. All right, any final thoughts from the re-rolling ones crew? Uh We we don't you want to plug Yeah, plug away anything you want to say Improval Oh campaign is um, yeah pretty soon. We're gonna be starting a new Uh, we're gonna be trying a campaign on our channel Um, you focused around a storm vault called the ember vault. It's kind of just something like We've been working on for a couple months and haven't been able to get off the ground yet We'll be something new and excited to look forward Definitely starting in marsha Tune in I'm gonna try something new and it's gonna be fun britain has worked overtime on this. I want to thank you He's uh, he's a writer and he wrote some great, uh, lore and stuff and I'm really excited about it The whole channel is excited about it. So, uh, yeah checks out march, but But I guess as this relates then to like the uh, the book to like putting that together Like the rules that we're gonna use for that now with wrath of the ever chosen to thinking about like future campaigns I feel like this book has Offered a lot of new stuff to play with that I think we'd be looking forward to using in other campaigns too So I'm glad that this material is, you know, presumably going to start coming out from games workshop that if we're going to start kind of doing this You know We're going to start doing more campaigns then they're going to keep, you know offering material that's going to help that Yeah, nice Dig it for jazz. Yeah in this book. Yeah, I give it a uh a solid a I agree for archaic Archeons All right, everybody. Well, thank you very much There he is. There's a big boy himself ready to smash catacross to pieces All right, everybody. Thank you very much for watching. We certainly appreciate it. Thank you re-rolling ones crew It's awesome to have you guys back on Uh, can't wait to see all of you at adept con. It's gonna be an amazing time Uh, for all of you out there watching, thank you so much Like I said hit like if you didn't already the more of that engagement It just helps more people find the video and we always want to be sharing with everybody out there So that is really deeply appreciated when people do that. So thank you for hitting that subscribing doing all that wonderful stuff That is super nice Uh re-rolling ones channel will be linked below if you're not already watching their bat reps Do go check them out as well as links to everything else We talked about earlier in the pick of the week segment But as always folks, I very much appreciate you watching this one and we will see you next wednesday