So, welcome to lecture number 35. In this particular lecture, we will start this modeling and management of groundwater. And under this, we will cover groundwater simulation models ground water management models, particularly for confined aquifer. So, under this modeling and management of ground water, it has got two aspects. One is simulation aspect, another one is management aspect. In simulation aspect, we try to see the physical processes by using our governing equations that we have derived in our previous lectures. And in management model, we try to see what if kind of scenarios, if we do certain kind of management or we put certain kind of restriction on the ground water use or restriction on variables, then what will be the situation in near future or in long term aspect. So, in flow equations under modeling that has got two components. One is the temporal component and other two parts are spatial based components. So, in this one, the first one this epsilon, this is basically porosity, then we have water saturation and fluid density. So, basically if this combined term, the multiplication of porosity, water saturation, fluid density, this is temporarily varying, then we can say that either we can model that density dependent or density independent phenomenon. For density independent phenomenon, the equation will be slightly modified because it will not be varying with the density aspect. So, other parameters in this equation, solid matrix permeability tensor, we have fluid viscosity, this is basically dynamic viscosity of the fluid, then relative permeability and fluid pressure, we have fluid mass source. So, in the flow equation, this rho value or this G value, this is having only component in the vertical direction. So, this is basically a modified form of our Darcy's equation if we consider it with the fluid pressure term. Next word is saturated, unsaturated transport model. So, this is basically porosity, water saturation density and this is dissolved mass fraction. Dissolved mass fraction, then volumetric adsorbate source, other things that is average fluid velocity, then we have apparent molecular diffusivity and identity tensor and this is dispersion tensor and this is our mass, solute mass in source fluid due to production reaction. And this is Q p into C star, this is C star is basically solute concentration of fluid sources. So, our solution methodology is basically solving the basic governing equations. So, what are the basic governing equation we have covered in this particular course? First one is Darcy's law, this is our most fundamental equation that is relates the equation of motion or if we say that is one form of our Navier-Stokes equation if we compare it with fluid mechanics. Then we have equation of continuity that is mass balance equation and finally, we have solute transport equation or advection dispersion equation. In advection dispersion equation also we can have other components like adsorption loading isotherms or our radioactive decay and these terms will be there to model the whole thing. Now, these three equations are our fundamental equations these are basically if you consider it in one dimensional then it will be mostly if you are considering a steady state case then it will be normal differential equations or ordinary differential equations, but most of the cases it depends on both space and time. So, these equations are basically partial differential equations then we need boundary conditions. So, boundary conditions and initial conditions. So, for a particular problem we can have either a initial value problem IVP partial differential equation IVP or initial value problem or BVP or boundary value problem or IBVP or initial boundary value problem. So, our equations are mostly in these two forms in these two forms. So, solution can be obtained for these two equations using either analytical or numerical methods. So, to solve these two or solve this equation in form of analytical solution we need to have some kind of simplified form of the equation otherwise it is difficult to find out the complex analytical solution for a complex hydrogeological system. Numerical solutions are easier to find out because we generally used a discretized form of the equation and we try to solve it with algebraic equations. So, in case of numerical methods either we can use this finite difference, finite element, finite volume, SPH that is smooth particle hydrodynamics, spectral methods or any mesh free methods for this purpose. So, what is the conceptual form of calibration? So, first we need to have some kind of definition or we should have proper definition of our purpose. What is our objective? Whether we want to model the thing or we want to model it for some kind of management strategy. So, we will have some kind of field data and from field data we can create the conceptual model that is conceptualization of the mathematical model. So, we need to identify the governing equations that will be required for a particular problem. So, identification of governing equation then boundary condition initial condition. So, next thing is numerical formulation. Numerical formulation we can discretize the equation we can write the computer program code verification. This part is important because we need to have some kind of verification of the code with the existing solutions. So, solutions can be either existing analytical solutions. So, or existing solution for a two dimensional problem, but two dimensional problem or three dimensional problem the problem is that if we start with the reality thing then there will be certain kind of errors. So, it is better to use that analytical solution for code verification. So, if the code is not verified then we can go back to the computer program and we can try to rectify or correct our errors. So, code selection is important. So, either one can write is or hard own code or one can select a proper code which is either a open source or a commercial one. So, if code verification is complete or code identification or code selection is complete then we can go to this model design part. So, with the field data we can design the model then calibration, calibration comparison with the field data. So, one way model verification is done and calibration is done and this calibration should be supported by the sensitivity analysis. With the sensitivity parameters, with the sensitivity of the parameters there should not be much change in the model results because if we are identifying the parameters in such a way that it is not a proper identification for which there will be not much variation then it will be a problem. So, we should have proper identification and sensitivity analysis with our problem and then after model verification we can go for simulation. With simulation also we can correct our sensitivity analysis and final is presentation of the results. If there is some kind of monitoring network then finally, we can monitor the thing and we can correct our assumptions or conceptualization with those monitoring data and again we can start from the initial part and we can conceptualize the thing and we can redo the whole process so that we can correctly adjust the model to get the proper results. So, a code selection in this case is an important part of the modeling exercise either one can have their own code or they can readily select some codes which are available in public domain. So, standard simulation models that are available in the public domain or with some restriction or in commercial domain this is one comprehensive list of those models. So, first model is the mod flow this is basically three dimensional finite difference based simulation flow simulation model this is FEM water this is 3D finite element model for saturated unsaturated flow through porous medium see what this is saturated ground water modeling or density dependent ground water modeling in coastal aquifers. Sutra this is saturated unsaturated flow and transport model with this we can model it the ground water flow and transport in any kind of aquifers. Empty 3D MS this is for contaminant transport with multiple contaminants RT 3D this is reaction with reaction mod plot is flow path identification thing in ground water then sharp this is two dimensional quasi 3D simulation model for salt water intrusion modeling and this is based on sharp interface then H S 3 3D this is this includes also that heat transport part other models that can be aimed here are this hydro term fast this also include the chemical reaction part tough to flow through fractures media flow trun ita the inverse tough thing bio plume this is one hydras this is also important software to model the flow in unsaturated porous medium. So, the identification or selection wise we can select any of these models for our modeling purpose or we can discretize our governing equations and we can use our standard discretization methods to get the solution. So, this is the starting of our modeling exercise. So, in modeling and management of ground water we have two aspects one is the modeling aspect in modeling aspect will see what is the simulation results and the policy aspect or management aspect we try to formulate some kind of management strategy. So, for hydraulic management I am talking about the hydraulic management because if we are talking about the flow part only then only we say it as hydraulic management otherwise we need to have certain kind of management models with transport mechanism. So, in case of hydraulic management hydraulic management we can have equations in the form of embedding technique embedding approach in embedding approach the governing equations are directly discretized and these are used within the optimization model or decision models to get the solution. Next is our linked simulation optimization simulation optimization and linked simulation optimization the simulation model is directly linked with the optimization model or decision model to get the solution. So, first approach in embedding approach we generally write the equation in discretized form and we directly use it in the decision models to get the results, but the problem with the embedding approach is that as we are discretizing it for a number of points or for a number of grids so number of decision variables, number of variables that is crucial for this kind of approach. But in case of linked simulation optimization the simulation model is doing the simulation part separately and only with a limited number of variables we can solve the decision model. So, first approach concern is variable number of variables, the second approach the concern is simulation time. If we are setting up a complex simulation model then for each simulation it will take significant amount of time and that will be a limitation for this linked simulation optimization. Then the third approach which can overcome these two limitations that is called meta-model approach, meta-model approach. In this meta-model approach basically the third approach basically meta-models are trained with the simulation results from original simulation model and we try to minimize the meta-model errors between the meta-model output and the output from original simulation model. So, at each iteration there will be correction in terms of correction of errors and that can be assessed with certain kind of indicator reference functions. So, in meta-model approach the most primitive approach is response matrix, most primitive approach is this response matrix. So, response matrix approach what is the advantage advantage is these are basically linear, linear type. With the linear type of response matrix thing we can easily form some kind of linear model based decision model and we can quickly get the solution, but the problem is that response matrix will always give you some kind of linearized results and one way we are compromising with the accuracy of the simulation model. So, for a complex non-linear general equations or general problem we cannot represent it properly with our response matrix approach. So, we need to have certain kind of approach in which we can consider that linear model thing, non-linear model thing. So, nowadays people are using this ANN SVM GP based models. So, what are these ANN is artificial neural network SVM is support vector machine and GP is genetic programming. These models can consider or can represent the non-linear behavior of the complex hydrogeological system. So, now we can have the approach where we should be defining our equations, then some optimization methodology and then we should have the solution. So, first part is symbolic. Simulation model, simulation model that is original simulation model or a meta model, then identification of objectives, identification of objectives, constraints. So, from simulation model to identification of objectives, constraints, then based on constraints and objectives whether they are linear or non-linear we can find out the optimization approach slash algorithm. So, this is the process where first identification of simulation model, then identification of objectives, constraints, then depending on linear or non-linear behavior of the objectives or constraints, we can identify the optimization algorithm. So, let us start with the simulation model. So, for as per Darcy's law we know that Darcy and flux V for any confined aquifer that is for any confined aquifer can be defined as V del H by del L. So, this is basically head loss per unit length per unit length per unit length. So, now with this we can have one finite difference grid. So, these are basically nodes. So, black dots are nodes. This is level say J plus 1, this is J, this is J minus 1, this is Ith cell. So, del X I and let us say that Q 3 is entering, then Q 2 is leaving, Q 4 is leaving and Q 1 is entering and this is your del Y. So, basically this is cell to cell water transfer. So, here we can say that this Q 1 is basically minus T X I minus J del Y J by del X, this is 1, this is 1, this is 1, this is 1, this is Q 2 is basically T X I J del Y J del X second one, this is Q 3 is minus Y I J plus 1 del X I del H by del Y third one and the fourth one and the final one. So, this is T Y I J that is del X I del H by del Y 4. So, in this case T X J is the transmissivity in the X direction of the element I J. So, and T T I J is the transmissivity of the I T I J and this is two element I plus 1 J. So, from this point to this point, so in this direction this T X I J that is acting. So, rate at which water stored that is rate at which water is stored that is considered as Q 5. So, S I J where S I J is your storage coefficient, this is del Y J and this is del H by del T. And in addition to that flow rate flow rate Q 6 for constant net with draw all withdrawal or recharge. So, Q 6 is basically Q I J and T. So, Q 6 is basically Q I J and T. So, Q this is varying with T. So, by continuity equation may be with the continuity of the flow we can write it as Q that is entering Q 2 that is leaving plus Q through Q 3 that is entering minus Q 4 that is leaving the thing and Q 5 is again that is the rate at which it is stored. So, it is equivalent to the storage plus Q 6. So, with this if we replace all this Q 2 previous expressions for Q 1, Q 2, Q 3 and Q 4 we will get this is T X this is del H by del X 1 this is del H by del X 2 this is del X I and this is T Y with this del H by del Y del H by del Y 4 and this is del Y J. So, S I J del H by del T plus Q I J T divided by del X I and del Y J. So, for X I and del X I and del X I and del X I and del Y J. So, in finite similarly in finite similar values of del X and del Y we can write the equation as T X del 2 H by del X 2 plus T Y del 2 H by del Y 2 S del H by del T W. So, if we talk about finite difference thing then we can write this equation as del H by del 1 and this is basically J T and H I J T del X I del H by del Y 2 S del H by del T W. So, del X for second phase that is I J T minus I plus 1 J T divided by del X I. So, del H by del Y third one or third phase that is I J plus 1 T minus I J minus I J minus I J T divided by del Y J and the last one that is the fourth one is I J T minus H I J minus 1 T del J. So, with this and del H by del T is H I J T minus H I divided by del X I J T minus 1 divided by del T. So, if we substitute these 5 expressions in our previous equation, then we will get a compact form of the equation in terms of A I J H I J H I J by del X I T plus B I J H minus 1 J T plus C I J and H I plus 1 J T plus D I J I J plus 1 T plus E I J H I J minus 1 T plus F I J T plus D I J plus 1 T plus E I J H I J minus 1 T plus I plus 1 J T plus D I J I J plus 1 T plus E I J H I J minus 1 T plus F I J T equals to 0, where these terms are basically coefficients involving our known values of the equation or provided information. So, this can be solved using any standard numerical technique like A D I or alternating direction implicit method, alternating direction implicit method. So, this is the form of the discretized equation, these can be directly used for embedding purpose. Now, we are concerned about the management model and ground water management model, there we are concerned about the confined aquifer. So, in case of confined aquifer, let us say that our configuration is like this, this is the base or lower portion, then we have in between the impermeable part q 1, this is q 3 and this is q 4. So, basically, this is the aquifer material there and this is the water material. Water height which is H 5 at this level and all are having equal del X difference and on the left hand side, we have H naught value of the water level. So, it is a bounded problem, both cases we have specified boundary condition, this is also called as Dirichlet kind of boundary condition. So, for this kind of equation, we have del h by del t, del h by del x equals to w by t x, where for a steady state condition we have t equals to del h by del t equals to 0. So, for this kind of equation, let us discretize it using our normal finite difference method. For second order finite difference, we will get del x square w i t x. So, this is the discretized form of governing equation and we have 1, 2, 3, 4, 5, 6, 7, 8, 3, 4, 4 pumping from this particular aquifer and this H naught and H 5 bar to water levels on left hand, right hand side. So, our objective is to maximize. So, first we have completed the simulation part. Now, we are concerned about identification of our object. Now, objective function. So, objective function is maximization of our total head, total head for i, for i that belongs to the set of i, that is the set of wells, set of wells, set of wells. And this is subject to or subject to or s t, we can write it as this i, this w i is greater than w min and h i is greater than equals to 0, del h i is greater than w i is greater than equals to 0, again i belongs to that set i, that w min is the minimum total production rate. So, rate for the well. So, the total rate should be greater than or equal to the minimum rate that is specified. So, unknown for this problem are unknowns H and w. So, once the model is solved, this can be determined w min, w min, w min, w min, w min can be determined as q i divided by x i del x s square. So, head objective that thing is for managing the aquifer. So, the above formulation one limitation is there that is it considers, considers negligible well diameter and negligible well losses. So, for any example problem, we can define the same thing, we can define the same thing using our this particular approach. So, for our original problem, we can write the equation as the maximize z equals to h 1 plus h 2, h 3 and h 4 and this is subject to our finite difference equations and that is minus 2 h 1 plus h 2 minus del x s square by t w 1 minus h naught. This is h 1 minus 2 h 2 plus h 3 minus w x s square by t w 2 equals to 0. So, this is h 1 plus h 2 plus 2 h 3 h 4 minus del x s square q 3 0. This is h 3 minus 2 h 4 del x s square t w 4, this is minus h 5. So, we have defined our we have defined our constraints, we have defined our constraints and the final constraint is this one that is there is a minimum value of total pumping in production wells and h i greater than 0 that is i equals to 1 to 4 and w i that is also positive. So, in this model additional constraints, we can put that h 4 should be greater than h 5, then h 3 h 4 greater than 0 that means, h 2 h 3 greater than 0 and h 2 h 3 h 2 h 3 h 1 minus h 2 that is greater than 0 and finally, h 1 is greater than or less than h naught. That means, your head on the upstream direction or you can say that where we have a higher head value that cannot exceed or that cannot be a lower one compared to your down gradient value. So, these are the additional constraints that will be required for solving the thing and the full equation as because this is linear in nature, we can solve it using a p p. So, this is all about the management of confined aquifers. Thank you.


The second I started applying to schools, I knew that I wanted to do engineering and I knew that I wanted to dance. I've been dancing my whole life and math and science have always been my favorite subjects. A knee injury when I was 12 forced me to pick between the three sports I was playing and I chose to focus on dance. I decided then the dance was going to be more than just a hobby. I've started to realize just how many parallels exist between the two. I'll spend hours meticulously working on a sequence of code. Line by line it has to be refined until it works correctly. I'll practice choreography for hours dancing until every part of my body is sore. When both of those things click and the hours of work pay off that feeling is the exact same. When that happens I know this is what I want to do. This is why I want to be here. I've always had to resist the pressure to pick one thing. Bright brain or left brain. Science or the arts. The UVM has given me the space to prove that I can do both. I'm a biomedical engineer and I'm a dancer. And I hope that one day my engineering can help find ways for people who need the assistance to enjoy the experience of dance.


Daniel Smith sent me a little care package that had a tube of yin-min blue in it, brand new color, and I watered some of it out to see what this color looks like, and oh, yum. I thought I'd ask you, what should I paint with it? Wrong answers only. I want to paint something that's not blue, and just see what the range of value looks like. Give me some suggestions in the comments.


Hi this is Julia and welcome back to my channel and for today's video I'm going to be bringing you guys my Spukathon TBR. Basically Spukathon is a readathon that runs from the 16th to the 22nd. It is hosted by Paige Shannon and Kayla also known as Lala and they host this every year and it's kind of like around Halloween obviously to read thrillers because that's their favorite genres and things like that. So I love this readathon. I participated in it last year and now it's a tradition for me to wear black lipstick during the TBRs for this readathon but I'm not going to be doing all the challenges because a lot of these books are from my October TBR because I'm not like I'm not doing super great with that so I didn't want to pick a bunch of new books. And just our read a thriller, read a book with a spooky word in the title, read a book based on a childhood fear, read a book with orange on the cover and read a book that has a spooky setting. So really cool challenges, really excited about this readathon. Yeah, if you guys want me to blog let me know down below because I'd be up for it. So first up here I have Slash Your Girls and Monster Boys edited by April Geniemi Tuchelke or Tuchelke, not really sure. But this is a YA horror anthology and I'm so excited, I've heard really great things about this and it has a lot of popular YA authors in it but I just heard great things and I don't know how many stories there are in here but I'll read one every little bit and hopefully I can get this done during the week. Everyone who reads Stephen King when they were way too young, me, me when I was 10. 14 short stories so I would read two a day, that sounds awesome, I'll do that hopefully. And next up here I have The Dread Hotel of Prosper Writing by Alexander Bracken, this isn't middle grade books so I think it would be a pretty fast read, it's about someone like a boy who gets like possessed by a demon or he has like a demon in him, which sounds fun, I'm up for it, I don't know what challenges this could go under, thriller, there's no spooky word, is Dreadful spooky? No, okay, no spooky word, there's no orange but I mean it's a thriller, right? Let's hope, okay. And this one here I'm really unsure of because I don't even know if it's glass but it's a thriller at all but I mean, oh there's not orange. You know what, it's fine, everything's fine. I really know, someone disappeared from her family, blah blah blah. She survived. Okay, this. This is The Child Founder by Renee Denfeld, I read her other book The Enchanted and I loved it so much so this came out recently, very excited for it, I just haven't gotten around to it yet so hopefully it's good. And then if those get done, which I don't, they'll all get done, that's me being hopeful because my reading, I don't know, I've just been reading, I don't know, well I've been reading The Godfather for the past little bit so I'm not the past, like the past like five days, I don't know, I've been reading The Godfather so it's kind of like, it's a slow dent, it's not slow or it's not dent, I don't know how to explain it, it's just a book that I don't want to rush through and I'm like really enjoying it so yeah. But just in case I finish those, I would like to get a start on Sleeping Beauties by Stephen King and Owen King. This book I'm so excited for, All I Know Is It's About Prison and Death Row, that's all I want to know. I'm gonna go into it that way. I'm not like in a super big rush to read this but I would really like to read it soon. I haven't really heard many people talk about it yet because it is huge and it did just come out recently but I'm sure people have read it and liked it hopefully. But just in case, I'm gonna put this on my TBR. There you guys have it, that is my Spookathon TBR. Let me know if you are participating down below and what you are going to be reading. Thank you guys so much for watching and if you're new here be sure to click the subscribe button and click the notification bell to be updated for when I post new videos and all that sort of stuff and I'll see you all there soon with a new video. Bye.


Hi there, and welcome back to another episode of Visual Studio Toolbox. I'm really glad to be back here, and today I have one of my colleagues, so I'm excited, Erika. Welcome to Toolbox. Hi, how are you? Good. It's going to be, I think, a great day. We're going to talk about an app that we built for the recent Connect event, and Erika is the mastermind behind the demo. So why don't you kind of introduce yourself fully and tell us about what we're going to look at today. So I am Erika Erli. I work in the product marketing team. I am very passionate about Visual Studio Nashor, and I work on keynote demos. It's not just me, it's a group of people working on the apps. It's not just you, you're not the only person coding the whole thing. No, it's not. It's a really good set of people working on this. So, and this is kind of our baby, and after the keynote, we were asked to share the code, and so we are excited to show it to people, and I tell a little bit more about how we built it, and what's in it, and share the URLs for GitHub, and just have it out there so people can use it. Okay, awesome. Yeah. The big thing that we want to take away from this, I think, is, number one, we have lots of things that we built as demos for various events, but for the big events that connect, we always try to share the source code out. So the big thing about this video is that, at the end of the video, folks can go and actually go and take a look at the source code. It's going to be up in GitHub. We try to publish everything we can. Not every single demo makes it up there. As we know, not every demo is perfect, but we've got some great repos, and you have a great overview, so I want to jump in. Okay, let's do it. So, I mean, the very first thing I wanted to share is, like, go watch the Keynotes. If you haven't watched them, they're on Channel 9. There's two amazing Keynotes. One is a Scott-Cousry Keynote and a Hanselman Keynote. Two Scots. Two Scots, and we have 15 amazing demos. Not all of them are based on the scenarios. Some are just showing on the tooling, but they're all awesome, and you should go watch them. And our first Keynote is based on application innovation. So, you'll see, like, the world we're living. You know, it's a world of mobile apps. Like, everybody has their phones and their tablets, and, like, the mobility is important. So, we try to show how to build mobile applications. And then, they're also everywhere, so they need to be on the cloud. So, we talk about mobile first and cloud first. Also, we live in a world where we have, like, lots of languages and tools and platforms, and, like, iPhones and Androids. Too many. Windows machines. Too many languages. Too many, so we, I mean, we're, like, we're pushing openness. And so, we're, like, a platform for any developer, you know, any application, any platform. And the last thing that I think is very interesting is the intelligence of the apps. Like, you need apps that, like, get to know you and personalize the experience for you. So, that's what we try to build on and show on at the first Keynote. So, again, the context of the audience is that we had all these requirements come in from our management and the things we wanted to talk about. And your job was to actually go and build out demos that were, you know, we're not building production applications, but things that are realistic enough that we can share the code as a demonstration to the audience. That's why we're doing this video for you folks. And then, we're publishing all the code we can and it should work with the bits that are public. We're not publishing things that are based on sort of, you know, Puffware. Nothing is gonna be, oh, you can't do this yet. If it's published, you can go ahead, download it and run it with the bits that we have available. And you're gonna go for some of the scenarios and how we broke it up, basically. Yeah, that's exactly right. So, our second keynote was based on productivity and we shared a little bit more of, like, what you can do with different tools. During Connect, we announced Visual Studio 2017 RC and also Visual Studio for Mac and Visual Studio Mobile Center and TFS 2017. So, with all these tools, you can build a lot of different applications, of course, and, you know, you can take advantage of the cloud and Azure. You meant to mention cognitive services and PSTs in the cloud and a lot of the stuff you had to work with. Yeah, exactly. So, that's our second keynote. So, the story I wanna tell today is, like, why is it that we build these demo applications and what is it like you get with it? So, we are trying to inspire developers, right? We live on a world where, like, the most important person in the enterprise today is the developer. We definitely think so, at least. Yeah, of course we are. So, we're not biased at all. And no, not at all. We're just focused on developers. No, exactly. But, no, but really, I mean, think about the world we live in, right? With, like, Uber and Netflix and, like, all, like, banks that are, like, using all these technologies. So, you really have to think how to innovate, right? It's very important. So, we try to build a scenario that is inspiring and that can show how you can integrate different technologies and platforms into building something that is, like, for the real world, right? So, in this case, I mean, what you're gonna get, right, is, like, an application that we build where we're using backend services. So, everything is on Azure. We have mobile applications. People are on the go, so you need people to get something on phones. Then we have websites. Websites for, like, people to get to know the company, but also, like, the actual company has a website to understand their customers and the business. Yeah, it's a full-enterance scenario. I mean, just on the slide here, we can see kind of how we broke it up, right, logically, and how folks will be able to integrate into this experience for GitHub and start looking at the code. And we have cool stuff like bots. We have, you know, good hype words, like microservices, but, I mean, all this stuff is built on top of things that we've just released or released at the event. So, the bot framework, right, we've got functions in Azure, all this stuff that you're gonna kind of talk about and go through. And it's all built on ASP.NET Core, I believe. All the backend stuff. Yes, yes, we have .NET Core. And so, it's just like using the latest of the latest, which is super nice and fun. I'm sure there were no problems getting all this ready before the bits shipped and before it's all available. Folks, I don't think I appreciate something like how we, as behind the scenes, people have to struggle with the fact that you're still working on stuff that they're gonna ship, and we have to start preparing demos and writing scripts and building apps and things that we hope, like you said, inspire developers, but it's not easy to do. And I'm always amazed at what we come up with at the end. But, yeah, let's keep going here It is a really good partnership with engineering. And actually, just talking about something else, this is built by a team of people that are from engineering and marketing and different product teams. And also, we work with our MVPs, MVPs and our customer team. So, we all work together on this. So, we all brainstorm and get the best we can on these scenarios. And then, the idea is that you can use it as sample code later after the keynote. Or, if you wanna do the most, like, I mean, you have some good samples. Yeah. I don't think it was always our goal to sort of publish all these demos out. I mean, I've known plenty of events where you saw something like on stage and some build years ago and you never got the bits afterwards, but we, at least our team, is really trying to make sure that we build things that we can share later. It's part of the investment. I mean, these things are not cheap to make from a people perspective. And there's graphic designers and all the stuff that has to go into making a very beautiful keynote. Now, we're making sure it also is something people can access. Yeah, it's out there. It's for the people, like, we build it for them. So, the scenario, so this year, like, every year we change the scenario. If you've just used the apps we built before, we've done a health clinic and my shuttle, which is kind of an over-like scenario. The two previous demos we showed. Yeah. Oh yeah, my drive was the build one we did last time. Exactly. And then we did, like, a little shopping app for Samarine and Asher. So, but this time we wanted to build something around bikes. Bikesharing is a very popular concept that is growing in a lot of different cities across the world. It's an easy thing to understand, but it's also a really good scenario that enables to show how we can build something that is intelligent, both for the people, like the customers, right? And also for the enterprise. Yeah, there's a lot of scenarios that the bike theme sort of works with, right? And that's where you build a lot of apps that don't feel kind of contrived. They do feel like, oh, these are real scenarios that if you were building just the system, this is what you'd build out. So that's what we try to accomplish. Yeah, exactly. And actually, there's a lot of really good companies who have done some of this. And what we're trying to show here is how you can use all these technologies and products we're announcing to improve your business and make it better experience for your customers. So, I mean, the whole idea is that it's a smart bike sharing system. It's in New York and in Seattle. So you'll see all our apps, say, New York and... It's your favorite city. It is. And then the idea is that the experience is both personalized, but it's also very modern and intelligent, right? So we have apps that work on different devices and platforms. The funny anecdote here is I always find like there's small pictures of people in our apps and that's always somebody from the team or somebody from engineering. I've had my face in there. It's always fun to see our folks in the limelight. Yeah, and I mean, James is there because he was like one of the masterminds, of course, behind like the submarine applications. He then would connect at the keynote. And so, yeah, you'll see James and Beth and Lara and like all my phones and my apps because, you know, we work together on doing this. I like it. James Montenegro, the mastermind. That should be his title in the gal. We should see if H.R. lets us... I'm sure he'll like it. Yeah, he'll vote yes, but it's harder. Anyway, so basically that's the concept and like what we're trying to show is we have to think about the enterprise first. You know, how is it that they can take advantage of technology, you know, for managing their business? So in this case, just imagine, you know, you have 10,000 bikes, right, distributed in a city. The bikes have IoT devices so you can track them. You can know where they are. And you want to manage your business with intelligence.  Also, with cognitive services, you know, now you can do a lot of fun things and are great. For example, think about like, not just the bike sharing scenario, but any scenario where you need a kiosk. You can just show up.  Have interaction with an application through voice recognition, speech recognition, without even having to type anything and then do a transaction. So, so. It opens a lot of scenarios up for folks. It is, I mean, the AI, the whole concept of AI, like it's really changing the way we think about like apps of the future. So, I mean, it's just representing that.  And, and it's. You have a mobile experience that really suits your need, just like Enterprise has their, you know, kiosks for you to interact with or has their, you know, analytics to make sure that their system is working well. It's cool.  So, just think about this, like, how you interact with your customers. So, I'm the thing, the thing we thought about doing here is customer service, like personal assistance through a bot.  Like you're on the go with your bike. So, you talk to a bot and the bot interacts with you and like, I mean, I think, I think that also changes the way, you know, we do things and we interact with technology and apps. Yeah, I've heard some people kind of say that bots are just glorified search engines and that, you know, there's some truth to that. But I think the reality is when you're building an experience around a bot, you can actually integrate it quite deeply into your application that the bot can know where you are, just if you allow it automatically, the bot can understand the context of the business transaction that's happening. You could know, well, you just took out a bike. So if you're saying some search query, it can know how to react to it. So bots are just very flexible things and I think folks shouldn't ignore them just because it is, it's some way, something that we're familiar with, but it is creating this whole new world of like integration that's possible from the application but then like Skype, right? So you can Skype to a bot or whichever IM service you're using. It's really cool stuff. Yeah, definitely. So a little bit of like the architecture and of course, you know, I mean, you have no idea about the brainstorming sessions, like the things that we come up with, but we have to find- This takes work, is what you're trying to say. No, it just- Just building this diagram, it takes a little bit of time. No, it feels, but it's also like, there's so much stuff, like I can tell you, like there's a million other things that we thought about that are not here. Like in a way, we have to keep the scenario simple enough that it's easy to explain and to understand, but like you can envision expanding and adding like more blocks of technologies to expand this business, right? Yeah. Generally speaking, like as I explained earlier, so you have a bike rider that can get like a marketing website to get to know like what's going on with this business and how do I get in? How do I sign up?  And that's where you can rent the bikes and you can interact with the application. You also have the Kiosk, I mentioned this, where you can just go and rent a bike without even typing anything. And what do we use to build the Kiosk app, is the UWP app? It's a UWP app and we're using cognitive services and I'll go through that, but basically, yeah, so the idea is that you can get that kind of interaction for the customer. In the middle, of course, we're like cloud first, right, and so Azure, Azure is a big thing. Everything's in Azure on the backend. We try to create an architecture using microservices. So we have microservices on.NET Core and Node.js, and we're using Azure Functions, Sub-Service, ACS for multi-container apps. We store our data on SQLDB. The IoT device, like that's an interesting thing, so obviously we don't have like 10,000 bikes, right? But like here the idea is you have, you know, an IoT device on the bikes, right? And you can get all that data and think about it, it's a scenario of big data. Like think about like all the GPS coordinates that you get from all these bikes, right? So we have a scenario where we use Azure Data Lake and to store all that and then you can use SQL, for example, to like get queries on where is this specific bike on this exact time? Yeah. So I mean, that's kind of what we're trying to show. And then thinking of the enterprise where you have like your private website where you have like Power BI, for example, embedded, and then you can get analytics on like what's going on with your business. You also have a maintenance application. So if someone is on the road and reports an issue, you get a notification. We wanted to have also an example using Cordova. So we build a Cordova application for maintenance and also works on all the different platforms. So basically, I mean, in like high level, this is what we have as the applications. And in previous years, like we kind of released all these apps together. We bundled them into a GitHub. This year we decided to split everything in seven different repos. And so that's what I'm gonna share about like next. But the idea is that if you want everything, well, you know, you have seven different repos. But if all you want is like to work with summary apps, for example, you just go to the mobile repo and then just get the code from there. So that's the idea. Cool, yeah. And we'll have all the links to all the repos in the previous demonstration that we published out there so folks can see. So folks don't have to worry about the little URLs we have here and there. They'll have it all. Yeah, so we also will have a blog post that goes through like all the end to end scenario, the description will have the links there. But the idea is that if you want, for example, websites, you know, this is what we have. We have, I mentioned the marketing website and this is the company website. That's the dashboard. That's the Power BI, yeah. That's the Power BI, exactly. And so we use different technologies. These websites in particular, we actually built it using NBC and also.NET Core. So we have two versions of the same websites. Cool. Then this is very interesting, the microservices. We announced Visual Studio Tools for Docker during Connect. You can do like single container apps, multi-container apps and CI CD. Donovan did a really amazing demo or set of demos on this and like, you should definitely go watch the keynote and watch them, right? Yeah, we have demos of this. But we bundled like two different repos with the two applications. So you can like download the code and like play with the tools where are now available and you can like work with them. Cool. Then this is a beautiful, like good looking mobile applications on Samrine. So this one, I think this is a very interesting application. It is what the consumer will use to interact with the company, right? So basically the idea is you have an application where you can book a bike. You can have some integration also with events. We have an API that we use from Ticketmaster. So you can get like all the events on the CD and from your same application, you can like say I want to go to Cirque du Soleil or like any like Broadway show, you select the event and then you can rent the bike from like one station to the other and get the transaction, all that in the same application. It's a cool idea, definitely. Like the ability to sort of map public data or data from other data sources in the application while demonstrating the power of keeping you productive and getting a bike and returning the bike or finding something that you need, getting support. Yes, then also something else you can do is like when you create a profile related to that is you can scan your credit card so you can like get like the transactions for whether you are booking an event and you can purchase the tickets or you can also just like pay for like the subscription that you're using from the bicycle. Also you can report incidents like I said when you're on the road. For example, like say you lose your bike and then you can talk to a bot, right? So you can get all that from the same application. We have the watch. We made a like a version of the watch, I have it here. But why don't we switch to this machine? Sure, let's go over to them. And then I can show you a little bit more of this application. Cool, there we go. We switched over. Okay, thank you. Perfect, so what I have here is the emulator for Windows and here I have this application that is responsive, you know, that we build. The same application works on Android, works on Windows phone. And so here is my summary project where I have the solution. Right, this is the actual source code we're publishing some folks can get started with it. Exactly, same thing. So we have the backend. So we have like the events I was telling you and then profile information. Then we have the wearables. So here's where I have like my watch code. It's a very simple application on this one. What we did is that basically you're on the go and you want to rent a bike and you know where you are. And so you say I want a bike from A to B, rent it and basically you get that from your watch. Then, I mean, the nice thing about building the application on summary is no matter what platform you're using, you can use SAML and you can like call your application. For example, this is my login page and this is what I build. The other thing is, you know, you can use C sharp. It's native code. It works everywhere. So this is my, for example, my iOS application. And for example, you can reuse views. For example, I have a view controller here I'm using for credit card. So have you seen those like applications where you actually scan your credit card from your iPhone? I've never actually seen that. I mean, I've seen the reader thing in every cap I've been in recently. Basically, like, I mean, we are reusing a view controller for that in our code where you can just take a picture to the credit card and then that's how you register the information. That'd be cool. I definitely think the whole swiping thing is kind of dying breed. Right. And if we switch to the phone, actually, I mean, I have the application. This is now on an iPhone, right?  It's kind of chilly outside. I'm in Sammamish. But I'm pulling the events from New York City because I'm going to go to New York City. Yeah, because it's a demo app. That's the real thing. No, but let me tell you something interesting about this. This is coming from Ticketmaster. So something we're publishing is that we have a little tool that we use to update the feed of data. So we're releasing that so you can update your own data for events. You can make your demo more relevant to your GEO. Exactly. That's cool, right? So basically, you say, I want to go to this event. So I want to see you can buy a ticket and you can rent a bike. So you can book a bike. And basically, this will give you a bike and it will tell you where the bike is, right? You can also have your profile information in there. You can see your rights. And then you can report incidents. So this is more or less the screen. So if I do something like, for example, I have a flat tire. So flat tire on the front. So I'm going to report this. So these, I mean, we're using push notifications. So you're going to get a notification that this was reported. And then with the other application that we have, the Cordova application, which is like the maintenance app, like the enterprise will get a notification on, like, hey, this user, you know, has a flat tire, like this is helping, right? So a tech could respond to the field. That's cool. Exactly. So that's more or less the submarine application. So you're welcome to use the code. If we switch back to this machine, I'll show you very quickly the repo. We're not there yet? OK. Back to the Surface Pro. Can we go back to the Surface Pro? OK. So this is my repo. It's one of the seven repos where we are releasing the same code I was just showing. So we are also trying to create documentation around it, you know, like how to use it, what to demo, where it's everything. So we're working on that. And we are happy to know that you can use this as well. Yeah, like right now in this screen, you can see it's a private hunt up of the repo. That's because we're recording before you're ready to publish, right? So you guys are still finalizing it with the team. And by the time the video is out and the blog post will be out, the repo will be out, and we'll be able to ship everything at the same time. So if you're watching this, you can get the code already. That's a good point. Yeah. OK, so let's go back to the presentation and keep talking about the rest of the app. So we talked about the Cordova application. This is the one where we are like, I mean, that thing I just said about like, hey, I have a flat tire. Yeah, it will show up in that application. Exactly. So we have notification examples on both the Cordova side and the Xamarin side. These are backend services. So again, the way we split our architecture, we're using microservices. We have Azure Functions. So we have all these microservices. We have feedback microservice of not a core, a rights microsaver of microservice on Node.js, and so on. We have others, right? The partner providers, like what I was explaining about Ticketmaster, we have the External Events API and the Weather API, which tells you that I'm really cold in here. So yeah, so that's another repo and you can go play with it. Also, we have like Azure Functions code in that same repo. That's the demo that Beth Masi did. And this is kind of my next thing. So I want to talk a little bit about Visual Studio Tools for Azure. So one of the things that I think is like a commitment from the Visual Studio team is better integration with Azure. We want to build tools that make it super easy and simple for you to work on Azure from your Visual Studio. I mean, you're writing code, and at the same time, you don't need to switch the portal to the things. You can do them from Visual Studio. Stay in the US. Make the US the full experience where we can, basically. Exactly. So two things I want to show is the updated acquisition experience from 2017 for the tooling crusher. And Visual Studio Tools for Azure Functions Preview. So I want to show that quickly as well. So let me go here. And the very first thing I'm going to show you is our installer for Visual Studio Enterprise 2017 RC. So before, with previous versions of Visual Studio, if you want the Azure SDK, it's a standalone installer. Right now, our latest version is 2.9.6 of the SDK. You can get it. You win a prize. Yeah, so the SDK for 2015, I mean, you can download it. It's available. We released it also after Connect. So you can go get the standalone installer. But if you're working with RC and you're wondering, where's the tools? Well, guess what? It's now integrated as part of the workload. So we have an Azure development workload. And basically, that's all the tooling you need for Azure. That includes ARM. It includes, for example, the data lake tools, what you do with your SQL, used to analyze big data. And then if you're wondering, where's the Docker tools? And the Docker tools that Donovan was showing, we have the Docker core and Docker preview. So if you install here, let me just I'm going to deselect this and just have this. This is what includes the Docker tooling. So this is what you need to get the tools we use during Connect for the demos for Docker.  Like if you select the top one again, the top workload, at first I kind of missed this when I was playing around with it. But you do have the option sometimes to select additional things that by default aren't enabled. We try to make the installer as compact and as fast as possible. I tested the installer myself after we released RC and as the final RC bits. I was able to get up and running for UWP in my home desktop machine of 10 minutes. I mean, that was really like eight and a half minutes, something like that. I wrote a blog post about it.  So this installer, much more flexible than before. It's even smart enough to tell us that you're already running Visual Studio. One instance, you got to close it. But yeah, it's definitely something we're investing a lot into. Yeah, and again, a lot of people were asking, where is ARM supported? And like 2017, it is. Like you just need to get the right workload. All right, so that's my first thing. But if you're still working with 2015, something really exciting we just released is tooling for Azure Functions. It's a preview. And I think that's one of the most exciting things. So Beth Massey during her demo at Connect, she talked about functions. And basically what we have, this is also integrated with the phone. On the actual phone, on your profile, you can get a selfie, get your profile picture. And basically we do two things with that picture. Like we analyze it and we use cognitive services. So you can figure out like the age and the gender of a user. And we also process image. So it looks prettier on your phone app. So we do the two things. So we have a function for that. It's in Azure. So this is the Azure portal now. You're showing the code in there. So this is the code in Azure. And now I'm gonna switch to Visual Studio. I installed the tools. To make the tools work, you need the Azure SDK 2.9.6. And you need to install the Azure tooling for functions. And basically it's the same exact same code for my application. And the nice thing is like, you can work on it from Visual Studio. You can right click and publish and deploy your function to the portal from here. And also, you know, as I mentioned, like Visual Studio is integrated with Azure. So you can use a cloud explorer, for example, here like the scenarios that we are, you know, taking these image and we are moving it to Azure storage as a blob. Right? So from Visual Studio, you can explore your storage. Right? And you can see your input and your output. So yesterday I was playing with this and I got my selfie in there. So it's processed. And then the last thing is like, how will the company use this information? So I have this dashboard, right? Which is the private website I was talking about. And basically here, if you can see, I can get like people like rights by date and gender and like by age. So I can start understanding like, how is like the population of like my customers? Like what age range? So I can predict things like, hey, I need to buy smaller bikes or bigger bikes or like bikes for college kids. So I think this also helps a lot of business. I mean, and that's just with taking one picture. Yeah. It's amazing and terrifying at the same time. More technology is heading soon. I know, but think about- We're all gonna be in trouble. Think about like how like when you're shopping online, that's the way it is. Like you buy something and immediately you start getting like all these ads about like related things. Everywhere you go, that surface dial that you might have looked at at the Microsoft Store follows you around. Not that I had that experience. Yeah, and in the end, like, I mean, it's sample code. I mean, we use it so we can show the power of cognitive services and like what kind of information you can get. It's also in Azure, everything's on the cloud. So, you know, there's like a good scenario. Yeah, real code. People can see how we did all this stuff. Exactly. So the last two things that we did were like two applications just thinking about AI and like how we are gonna like go change the world in the future. The developers have that big mission. Yeah. So as I mentioned, we have this like kiosk application. Lara showed it like on the keynote. It was the last demo. And it's a really fun demo because basically what you do is like you have the application open. It's a UWP application. You get close. There's like a camera view. It recognizes your face. So we're using the face API to recognize your face. There's our boss being recognized. Yeah. You get his picture in there. Yeah, and so basically you get like the application knows who you are because you have your profile picture. Like it's everything all tied together. So you got your profile picture. Now we know who you are. So when you get to a station, imagine you forgot your phone. Right. But you really need to go to work, right? Yeah. You really, really really need to go, right? So you type in your username and password and you're using the unscreened no. No, so you just go to a station and basically you approach the kiosk. It will recognize your face. We're doing like a two-factor authentication. So basically we make you like say a sentence. So we're using speech. Right, sometimes security phrase and then. Exactly. So we have a security phrase. So we have like the two-factor. And then once you are authenticated, then the application will ask you well what do you want to do, right? Like you may not want to rent a bike. You may want to do something else. But if you say rent a bike, the application already knows who you are. They have all your like information from your profile. So they will credit your card. Your credit card they will just say, okay we'll do the transaction for you. And we will unlock the bike 25 from the rack and then you can go get it and then that's it. All you have to do is show up. Yes. It's a really nice application. We are releasing the code. This was built by our customer team from Visual Studio. And I think it's an amazing app. I mean, it's one of these things that it's like fun to like just go do it again and again and again.  And that's it. The whole simple find sign in thing is huge. I mean, just Windows Hello on my service book has been the most amazing experience. I really, like I'm the type of person like you, right? We get to a meeting, then we go to the next meeting, then we go to the next meeting. Your machine is constantly going up and down with the lid. But every time I open it, it just logs me in. I had one time I forgot my password, I'll be honest because I was using this visual login in my pen. And I was like, oh, I have a password. I forget what that even is, but it does make it much more kind of secured. The last thing you want to do is type your password, full password to your network resources and the airport or something, right? It's much safer to do this kind of analytics and nobody wants to be typing on some on-screen keyboard, you know, whatever, right? That's the last resort. This is- And like the reality is like there's companies who are already using that, like Uber. They use the face recognition.  So you know that and they have to use, they're using actually- These are real scenarios. We're not saying that the way we implemented is the most ideal security protocol or whatever. We're showing technology. Our point is to demonstrate tech, not demonstrate like security practices, but as a concept, this concept is being fought through by other companies in the real world, and I think it has a lot of potential, so it's cool. Yeah. So the last thing is like the bot. So we built the bot and the scenario we thought about is customer service. So here's like some screens on like me chatting with the bot about like I lost my bike, when did it happen and where did it happen and let me help you. But the very interesting thing is this bot is both talking to a customer and it can determine intent.  And in this case, it will tell them, hey, you need to bring a bike to experts and who is there, right? And that's what- It's a very Uber-like experience. Your car is about to arrive. Your tech's about to arrive. Exactly. So like here, there's a help desk incident, right? And then the ETA is determining on like where's the employee and how long will it take that person to get where the customer is. Yeah, this thing can be very intelligent. And I think Uber has taught a lot of us what the future could be like for other things beyond just renting a car and this is really awesome. It's both on top of our stack. Yeah, exactly. So, but what do we use to build something like this? So something is interesting. We release also during connect the Azure bot service. So let me show you, you know, in case you haven't like seen it. So this is a new service. It's on Azure and, you know, it helps you build bots, right? What's very interesting is on these bot service, you have different channels. So you can pick, you know, from any different channel that you want. You know, in this case- What is like a channel in this context? So in this context, for example, it's like where will the interaction with the customer happen? So for example, I have my, in my personal phone, I'm using Skype, right? Because, you know, I work at Microsoft and I use Skype all the time. We love Skype. And there's also Microsoft Teams now. So you can use that, but you can use the web chat or we also did like the demo that we did at Connect with it, with the Facebook Messenger, right?  So you have different channels. And it seems like you can even chat with your own bot here in the line, right? Yeah, you can make your custom bot. So in this case, the bot we're using, we're using Luis, which is a cognitive services and it's just to determine intent, right? So we have the code of the bot in here. And the idea is that you can figure out, you know, what is it that the customer will want to do and then have some responses, right? So the application actually, if I show it to you, it's exactly what I had on the screen before, but just like showing you how it looks in reality. Can we switch to this phone? There you go. Okay. So I have my bike sharing incident with my bot. So this is the Facebook Messenger bot using that same service. I'm signing on this phone as Lara. So it's asking when did this happen about 90 minutes ago. And so it will figure out like where my bike application, my bike is, right? And this, we were making the joke that Scott Hanselman stole the bike and so oddly the bike is in Chipotle, right? That would be very strange for Scott here, if that's the right, he would never go there. He must be somebody else. Inside humor there. Yeah. So I am at Spring Studios right now. And so this is what will kick off like the support incident. If you see there was a delay in there between the two messages, this is because the bot sent a message to the enterprise saying that I lost my bike. And it's figuring out it's gonna take 14 minutes for someone to come and bring me a bike where I am. This isn't static text, basically. It's actually trying to do the full set of transactions that we do in the real world. Yeah, yeah. And so some of the responses, of course, it's a demo. It's not a full bot, it's not a full application. We're here to inspire, not provide. Yeah, but in the end it's a sample you can use. It's in GitHub too, we published it. So I mean, you're welcome to use it. So just wrapping up here. So the code is now on GitHub or you know, we'll be in a few days, right? Imagine fast forward like when we're actually publishing this video or this recording, right? And then we are having a blog post and we're linking to all the repos. Again, it's seven different repos. You can get all of them if you want them or just the one app you want. It's all for you. Like I said, this is a group of people working together. It's our MVPs, people from engineering, from marketing, from like a lot of different product teams. We work on this like for two months before the keynote using agile technologies and like having daily stand-ups and like using what any developer team will do. But it's an exciting thing for us, you know, and like we're still working together on releasing all the code. And we are looking forward to the next one. Yeah, it's cool. It's a big team of people with lots of familiar names there. The app looks awesome. All right, and you know Microsoft loves developers, like I said, the developer. That's my favorite slide right here. Yeah, it's the best one. It's a good time to be a developer. I mean, you get to change the world like doing these kinds of things for the real world, of course, but it's out there and it is statement. It's a reality. Yeah, it's what we believe and what we try to enable. That was awesome. Thank you so much for coming on. Well, thank you so much for having me. Yeah, it's been great and thank you folks for watching. Thank you. I hope you enjoyed the episode and we'll be back in another show. I'm sure before you know it, so keep watching and thanks again and go check out all the source code. Thank you. Thank you.


In today's lecture we are going to discuss the covert narcissistic abuse. The narcissistic abuse, mitted out by covert narcissists, is not the same as narcissistic abuse typical of overt or grandiose narcissists. These two subspecies of narcissists differ so dramatically that there is a debate going on in the profession whether overt grandiose narcissists are actually a type of psychopaths and the only real narcissists are the vulnerable, fragile, covert ones. But we will leave this debate aside, I have a whole video dedicated to it for those of you who are interested and today we are going to discuss the special variant of narcissistic abuse, this pernicious, specious, horrible, penetrating, or pervasive, poisonous, toxic variant of narcissistic abuse that has little to do actually with the overt grandiose narcissists variant. And variant it is because it's a bit of a virus as I have said in a video a few years ago. We are also going to discuss coercive control. There's a multiplicity of misunderstandings regarding this word. It's being misused the same way as gas lighting is. And so I thought a bit of clarification with academic background would be useful, should be useful for those YouTubers open to learning, very few admittedly. Let's start with covert abuse. Strictly speaking, abuse typical of covert narcissists. Number one, such abuse is passive, aggressive, obstructive. It has to do with sabotaging, undermining, preventing, derailing, challenging other people's wishes, hopes, tasks, assignments, agendas, et cetera, et cetera. There's a lot of passive aggression involved. The covert narcissists creates intricate webs and coalitions of flying monkeys and kamikaze, kamikaze suicide bombers, these bombers. So the covert narcissists puts together networks of people and then activates them against the selected target. Now, the covert narcissist is a narcissist. He has no empathy. Although he fakes empathy, he pretends to be a rescuer or a savior or a healer or a codependent or a victim. In reality, the covert narcissist is even more vicious and more psychopathic and more dangerous than the overt and the grandiose narcissist. And this kind of narcissist does not hesitate to sacrifice other people, to put them at risk, to compromise their interests, to ruin their lives, to put in danger their nearest and dearest, anything to obtain the outcomes of impacting the target, destroying the target, the target of vengeance, the target of envy, the malicious envy, the target of narcissistic rivalry, the target of some imagined fantasy, gun, or eye. When a target is settled on, when the covert narcissist decides this is my target and I'm going to destroy him or her, this kind of narcissist recruits people in a variety of ways, sex, money, flirtation, pretensions, pretending or faking, as I said, a savior, a healer, a rescuer, a good guy or a good girl. And so this kind of covert narcissist puts together coalitions and attacks the target in the process, destroying the very people he uses without any reboss or regret or second thought, hiding behind the patterns of women and children as kind of human shields. This is typical of the covert narcissist. Now, this is one element of what I call the occult narcissist, the hidden narcissist. It's a narcissist who hides behind, hides behind people, hides behind a facade, hides behind fake behaviors, hides behind social norms, hides behind cultural mores, hides behind superstitions and conspiracy theories and misbeliefs and misinformation, hides behind hidden occult narcissists. He fakes empathy. He pretends to be what is not an expert, a rescuer, a savior, a healer. He is helpful, ostentatiously helpful. He is smarming, absolutely smarming. He is altruistic or pretends to be altruistic and compassionate when actually this is prime manipulation. Being a covert narcissist, he is adept at mimicking, imitating people, resonating with them, knowing not only which buttons to push, but how to become one with a flying monkey, how to create or generate the impression we are the same. We are a brotherhood. We have the same goals and the same enemies. Let's go for them. The covert narcissist is manipulative and it usually is nonverbal. There's a lot of body language that goes into the covert narcissist Machiavellianism. So whereas overt or grandiose narcissists are either cerebral and then they use their intelligence or they are somatic and then they use their bodies, the covert narcissist is almost always somatic because the covert narcissist is a collapsed narcissist. He's a narcissist who has failed at obtaining supply using, for example, his intellect or his personality or his character and temperament or his accomplishments or his biography. What's left? His body. So the covert narcissist doesn't have to be a somatic narcissist in the classic sense, but he is likely to emphasize body language, facial expressions, micro expressions, kind of friendly hugs, imitating the body language of empathic, accomplished, beautiful, kind, loving, nice people. The main instrument, the main tool in this arsenal is the body. So most covert narcissists are nonverbal when it comes to manipulating, conspiring, colluding, and then striking at the target, exactly like a snake in the grass. The covert narcissist exercises punitive avoidance and withdrawal. The aim is to increase or enhance the abandonment anxiety in the target. The covert narcissist gives the silent treatment, withholds affection, shows no emotions. This is called reduced effect display, has usually flat attachment. So the covert narcissist is more of an absence than even the overt or grandiose narcissist is more of an absence is more of a void or vacuum, more of a black hole than even the grandiose overt narcissist. And as I said, he creates secret coalitions against you, smear campaigns hiding cowardly, cravenly behind others. And all this is intended to control the situation, to control you and to obtain favorable outcomes, for example, to get you back or to render you contrite and remorseful or to punish you punitive vengeance. Be the case as it may. These are the strategies used by covert narcissists. Now, many people attribute to covert narcissists and to overt narcissists coercive control. Coercive control is an exceedingly rare phenomenon. And no, it is not typical only of narcissists. The vast majority of people who exercise coercive control over their intimate partners are not narcissists or psychopaths or otherwise diagnosed with any mental illness. This, these, these are the statistics. So coercive control is a strategy, a strategy of subjugating, subduing, taming, domesticating and housebreaking someone who is significant to you. Now, some narcissists, of course, use coercive control consciously and unconsciously. Psychopaths use coercive control to some extent, borderline. I'm not saying that coercive control is not an element, not an element in the armaments, not a weapon in the arsenal of the narcissist, but very few narcissists do, do it. Very few narcissists use coercive control because it's a highly, highly defined term, clinical term. So coercive control is another much misused phrase. Exactly like gaslighting or narcissists. 99% of the videos about gaslighting online are trash, wrong, nonsense. Because they are not backed by academic research. They're not based on studies and on 100 years of literature. So same goes for coercive control. Coercive control must include the following elements to qualify. Number one, the victims of coercive control. They are terrified, they are terrorized to the point that they alter, they change their routines and modify their behaviors. The main motivation in coercive control, the main emotional landscape and background is terror, extreme, extreme, extreme, extreme, extreme. The main emotional landscape and background is terror, extreme, fear, even fear for your life as a victim. Number two, social isolation. In coercive control, the victim is totally isolated from the environment on pain of extreme punishment. Now coercive control takes place only within long term committed relationships. Not in dating, not in a fling, not among friends, only in long term intimate relationships. Get it? It involves social isolation and the constriction of life. In other words, the victim is gradually or not so gradually cut off from everyone else in the environment. The only contact the victim has is with the coercive controller, with the abuser. It's the only lifeline, the only pipeline into the world, the only reality testing, the only interface with the universe. No one else is allowed to see the victim. The victim is not allowed to meet anyone, to socialize, to fraternize, to go out. No, not allowed. Life itself is constricted. One by one, the victim sheds her previous hobbies, interests, occupations, jobs. She resigns, she stays at home. And there she does essentially only what the controller approves of. If he disapproves of a hobby, she drops it. If he is irritated or annoyed by an interest she has, she doesn't have it anymore.  Life narrows, is constricted more and more. And this is known as life constriction. Next, invasive monitoring and supervision. This is possibly one of the most critical aspects of coercive control. When the monitoring of the victim and the supervision of the victim by the controller, by the abuser, is all pervasive, ubiquitous. The abuser has the passwords to the victim's digital devices, smartphones, laptops, tablets, you name it. The abuser has the right to open the victim's post and read it first. The abuser senses a speech. The abuser monitors everything she does, comments on it, or forces her to change her habits and her behaviors. She wants to watch television, it tells her not to. She wants to drink some wine, it tells her not to, et cetera, et cetera. Monitoring, supervision, criticism, like in an externalized, harsh, erstwhile inner critic. Sadistic, a sadistic superego, reified in an intimate partner, reified in the abuser. The abuser becomes the victim's superego, externalized and sadistic. Now the monitoring and supervision are micro. They go into every possible detail. The abuser does not let the victim shut the door of the toilets when she uses them. I will not go into details. Or when she takes a bath or a shower, he is there, curtain drawn, watching the proceedings. She can't change clothes without him being there. She can't go anywhere alone. She can't make phone calls without him listening on an extension or next to her.  Nothing, not even open the door, not even say hello, not even buy a loaf of bread, not even watch television, not surf the internet, nothing. Everything is monitored and supervised. He installs spyware and other types of malware, key loggers and everything on her phone, on her electronic devices. He insists on reading her email, her chats, WhatsApp, you name it.  This is typical of coercive control. Next. And this is what renders, the next thing is what renders coercive control criminal. Coercive control is a criminal offence in the United Kingdom and several other countries, but not for example in Canada yet. So but gradually I think it will become a criminal offence in the vast majority of jurisdictions because coercive control to qualify as coercive control must include a deep privation of needs, a denial of the gratification and satisfaction of basic needs like hunger or thirst. The victim is denied food, not allowed to drink, not allowed to satisfy or to meet even the most basic requirements of existence without the say so of the abuser and the abuser has a veto power. He can deny her food for three days or drink for one day, fluids for one day. I'm not mentioning other needs like sex and love and compassion and affection and contact with other people and contact with the family, interaction, I mean I'm not mentioning any of these social dimensions, social needs, none of this. I'm talking about the most basic things, if you don't obey me says the coercive controller, your punishment is you're not going to eat today. So the deep privation of needs, the denial of needs is a crucial component of coercive control which renders it criminal actually. Coercive control involves the control and micromanagement of choices, decisions, behaviors, actions and micro behaviors. Everything is totally managed, everything requires approval, explicit or implicit, everything is subject to punitive measures, punishment, if you deviate or diverge or disobey or display any sign of autonomy, agency, independence and self-efficacy. So control and micromanagement, there's a denial of access, denial of access to money, to friends, to family, to help, to the authorities, to SACOR, to water, to food, to television, to internet, to your children, to your ex, denial of access. The denial of access is a major control strategy and it is coercive in the sense that if you dare to oppose it or to try to haggle, bargain and negotiate, you're punished. And the punishments in coercive control escalate and they can and often do reach the physical. So physical violence is very common in coercive control, terrorizing, degradation, humiliation in a variety of ways, including sexually. Multiple modalities of abuse, verbal, physical, financial, sexual, they're all employed in order to control the victim. There is a strong element of conditioning, I have a video about conditioning the victim on this channel.  So conditioning, compliance, automatic submission, unthinking, non-critical is rewarded. If you act as a slave or as a programmable robot and you respond immediately to the wishes, expectations and commands of the abuser, you're rewarded. If you don't, you're punished. And this conditioning, operant conditioning, leads to automatism and to impaired reality testing. The will is broken. You learn to react the way Pavlov's dogs reacted. You salivate when you hear the sound of your abuser's voice.  You believe that your abuser is the most and only faithful rendition of the world. And so you become conditioned. Your submissiveness, your subjugation is also conditioned in the sense that you cannot contemplate any other alternative.  You no longer control your behavior. It's just there, automatically, beyond the ken and the realm of your ability to modify, to kind of negotiate a compromise or something. You don't even think about it. The abuser or the coercive controller uses a specific look of, I don't know, dissatisfaction or disapproval. You immediately follow to the line, kowtow and obey, obeisance, automatic obeisance, total obey obedience. To qualify as coercive control, the whole strategy is premeditated. And that separates coercive control from the same phenomena in the narcissist's shared fantasy. The narcissist's shared fantasy is not a premeditated psychopathic strategy of control. The narcissist is as much a hostage of his shared fantasy as his victims are. He believes in his own deception. He adopts his confabulations as real. He doesn't future fake because he fully trusts that he will realize his promises. So coercive control, on the other hand, is goal-oriented, premeditated, called, calculated, scheming, Machiavellian. That's why coercive control is much more typical among psychopaths than among narcissists. Although, as I said, there are many coercive controllers who are neither psychopaths or narcissists. Coercive control is therefore not the outcome of mental illness, such as a psychotic disorder like schizophrenia or narcissistic personality disorder or bipolar disorder or some other personality disorder. If the coercive control is the outcome of mental illness, then it is not coercive control. Coercive control is a cognitive premeditated strategy. Some victims misperceive coercive control as love, as an expression of interest, as a display or manifestation of attention and or as the abusers in security express dysfunctionally. These are all excuses. There is no reason or excuse or justification for coercive control. It's criminal, it's horrible, it's soul-racking, and it should be fought against by any and all in every means possible. There is a big difference between typical abuse, even narcissistic abuse, which is the most extreme form of typical abuse. These types of abuse are interactive, they reflect dynamics, most of which are unhealthy and dysfunctional. They are usually not malevolent. These types of abuse are not malevolent, they're not scheming, they're definitely not goal-oriented. They simply reflect badly damaged people. They reflect the dynamics of badly damaged people, not so with coercive control. The coercive controller knows exactly what he's doing, and he keeps doing it. He knows that he is isolating his prey. He knows that he is denying her food and water. He knows that he is punishing her disproportionately. He knows that he is conditioning her. He knows that he is terrorizing her and degrading her and humiliating her. He knows that he is altering her behaviors, decisions, choices, and actions. He knows that she is no longer the same. He knows that she had become a robotic, automated machine responsive to his cues and his needs. He knows that he is doing all this. And he doesn't care. He doesn't even bother to justify it to himself or to anyone else. That's just the way it is. It's a reflection of a power asymmetry. So coercive control is qualitatively different to any and all other types of control, including loss of cystic abuse.