I am a brutally honest mature beauty blogger. Sometimes I get in trouble because I really like to tell it like it is. Whether I get things in PR or not, I will make sure that you know that, but I also make sure that you know the real truth about it, whether it's good, bad, or indifferent. So these are the things that I purchased. Well, there is actually one thing I did get in PR here, but most of these I purchased myself and I just really wish I had saved my money. So I'm trying to get you guys to save your money if you can. So we're going to get right into the things that I really just did not like in the month of April. All right. So let's do start with the thing that came from PR and it's from number seven. It's the Airbrush Away Poor Minimizing Primer. This actually has a fantastic texture and it reminds me almost identical of the Hourglass Vail Primer. The texture of it is so close to it, just like the Angel Vail from NYX, but what I don't like about it, and I don't know whether I just got an old tube or what the deal is, it smells like it's gone bad. And every time I put it on, I'm like, what is with that? It almost smells like, you know, when you get an old rag and you know that you need to bleach that thing? That's what it smells like. And so I just feel like I couldn't do it. I don't care if I had to put it on for five seconds and then the smell went away. I couldn't do it. But the texture is so good. So I'm wondering, I'm hoping that I just got one that was old and that the other ones aren't like that. If any of you guys have used this and you feel like it's a really good one and you don't have that fragrance, will you please let me know because I'd be happy to go purchase it myself. They did send this one to me, but I would be happy to go repurchase it myself and you know, try it because it is a lovely primer as far as how it just glides across the skin. So yeah, I could not handle the smell and I don't think it's good to put that kind of stuff on your skin anyway. I have three foundations that were such huge fails for me. Now, the first two are such huge fails because of the way they went on and how thick they were. This one is the Becca Ultimate Coverage Foundation. I did report on this earlier. I did get this one from Octaly. Two things. Sorry, I got NPR, but I did get this one from Octaly quite a long time ago and I talked about it before. This is not a good foundation if you are dry skin, mature skin and you don't need a very full coverage foundation. It just, it looked terrible going on. It was so thick and it just felt really super heavy on my skin and I'm, and did not wear well either. The color was okay. Color on both of these was okay actually, but it says 24 hour wear. I believe that these are very long wearing. That's what they're going for and they're going for that ultimate high coverage, but that look right now is just, most people aren't going for that. Most people are going for a more natural look on their skin to where a little bit of their skin shows through, but they get really good coverage that evens out. This just goes off. It goes a lot on a lot like the All Nighter from Urban Decay, which I used to love before I went through menopause. Maybe I would have loved this before I went through menopause too, but this one is from Smashbox Studio Skin Full Coverage 24 Hour Foundation. They're both 24 hours. They're both full coverage. They're both very thick. They're both very cakey and they both do not work well on my mature dry skin. Wear time on it too wasn't that great because it got patchy really quickly. I don't know whether it's that I have dry skin, whether it's menopause, whatever it is, it didn't work. Then this one right here is from Doll 10 and this is their foundation and this is their Anti Stress Skin Protector. Skin Perfecter. Excuse me. This is in light. I was so bummed about this, you guys, because I had heard so many people talk about Doll 10 and how nice it is. This, first of all, was a super duper yellow, yellow color. Let's see if we can get to see that. Super duper yellow color. She doesn't have a huge shade range where you can go in and you can go, okay, I want light neutral, not light warm, which is what this is. The shade range was not good at all. Then we had the fact that it went on too thick again, but the coverage was terrible. It did not cover at all. Talk about patchy. Oh my goodness. It got so patchy so quickly. I was just really disappointed in that because I did purchase the whole entire, as much as I could, of the Doll 10 makeup because I was really intrigued. I watched it. I can't remember whether I watched it on HSN or QVC. I think it was HSN. I watched it and I was so intrigued with all of her products and the way she talked about her products. I'm like, that sounds really great. As I got them, I'm just, I'm not that happy with them. I'm still trying a few of the other ones. Then I was really excited to see Zewava come out with their Authentic Skin Perfecting Concealer.  Fantastic. This doesn't deliver like that one does. It's an okay color. It's actually quite a good color. It's very neutral. I don't know what I picked. I'll make sure I put it up on the screen, but it's very neutral. But the problem is, is that it just, it got super patchy on my really bad dark circles. It did turn a little bit weird and a little bit separated and a little bit patchy. I'm pretty picky about my concealers because I have a problem there anyway. There is not very many concealers that I can wear even drugstore high end. I was excited to be able to try one that was more high end because usually I stick with drugstore because I want the cost effectiveness of it, but this wasn't that great and I was really disappointed in it. Then from Stila during Ulta's 21 Days of Beauty, I did get their brown liquid eyeliner. I actually absolutely love their black, but this one was just a little bit too light. I use these to line my lash line so that my lashes look longer. If I put this brown in there, it actually kind of makes my lash line look a little bit reddish, which is kind of weird. I'm not super happy with this color, but I will tell you guys that I do love the black one and I actually really like the navy one too. Maybe this is just about color. This is the Stay All Day Waterproof Liquid eyeliner and it doesn't budge. It's really good as far as that goes, but the brown color really disappointed me and I wish that I had gotten it into a different color. Then the balm was having 50% off, so I ordered quite a few products from them. I have some that I really liked. You can see those in my monthly favorites, but I have some that I really didn't like. The first one that I really didn't like was the Anti-Orange Bronzer. Take home the bronze. This one says Thomas on it. This is supposed to be anti-orange, but you guys think this is the oranges bronzer I think I've ever seen. It is so, so orange. It's beyond orange and I'm like anti-orange bronzer.  I was so disappointed in that because that is the only reason that I bought it was because it said anti-orange. Yeah, very disappointed in that one. Then I had heard a lot about this highlighter. It's the Mary Luminizer and I was really excited to get this one and I don't mind the texture on it. The texture is quite nice. The problem was that it really just wore off really, really quickly. I keep having this hair fall down, driving me crazy. Then as I was trying to build it up, it started to look orange like the bronzer. It wasn't a good color for me. It wore off a little bit quicker than I wanted it to. I was just kind of disappointed. There were a few products from the balm that I am disappointed in and honestly, you guys, I probably won't purchase from the balm again just because of the few products I did weren't products that I could just say, okay, well, these were great. I love them. I fell in love with them. It wasn't like that. Okay. The next one, I really wanted to make sure that I told you guys about because I have raved over and over again about the LA Girl Pro Palettes in the 16 Pan Palettes. These colors are fantastic and they're beautiful, but this latest one that they did and this one is the Pro Artistry. I think the other one is the Pro Mastery and I've worked with all of those other ones a lot and those ones are really good. But this one I was working with today because I wanted to do a look out of it for you guys today. I ended up taking it off and I'll tell you why because this color right here, this color right here and this color right here are so chunky and they have, it's not that they have glitter in it because that doesn't bother me, but the chunkiness of them, there's major fallout. I don't even know if you're going to be able to see this or not, but it's going to fall all over my mirror as I'm rubbing my fingers together. Major fallout and then when you put them on your eyes, you get so much, it's just so weird. It's just so weird because all their other palettes aren't like that. So I even tried like wetting my brush, different things. So here's the thing. I'm not going to get rid of this palette because all the colors in here except for the ones that are the high metallic colors. So it's this one. So it's the gold, the bronze, the white. There's a peach in here and then there is this silver in here. So there's about five colors in here aren't usable to me because they're just not great. But the other colors in here, they're beautiful and they work so well on my eyes and I love them. So I am going to keep this and continue to work with the other ones. I might declutter it at some point just because I love the mattes in these. They're fantastic. But I would actually say steer clear of this because normally these, these palettes from LA girl that are going like this, the 16 pan palettes, they go across your eyelids. The high, high shimmers go across my mature eyelids. They're a little bit creepy and wrinkly and they're just like butter and I can put a little bit of spray on there, my finger and just wipe it across there all day long, last, no fall out, just beautiful, but not this baby. It is just such a disappointment. I wanted to make sure that I told you about that because I had spoken about it before and wanted to make sure that you knew that most of those in there were chunky and that they weren't working for me at all. So that is it for today's video as far as what I wished I'd saved my money on and not repurchased. Very disappointing products to me. I hope that you guys are all doing well. Thank you so much for spending a little bit of your time with me. Please give, please give this video a thumbs up. Please take care of yourselves. Please stay sanitized, stay safe. I love you and I'll see you all in my very next video. Bye guys.


Hey, welcome back everybody. Jeff Frick here with theCUBE. We're at security in the boardroom. It's a Chertoff event. They go all around the country and have these kind of small intimate events talking about security. And today it's really about the boardroom and escalating the conversation into the boardroom. So it's not a tech conversation. It's not a mobile phone management conversation. But really how do we get it up into the boardroom? And I'm really excited for our next guest. He's Michael Chertoff. He's a co-founder, executive chairman of the Chertoff Group with a long established career. And I'll let you go check out his LinkedIn. He's been Homeland Security and it's a long, long list. I won't even go there. And Jim Flaging, he's the principal technology sector and strategy performance lead also for the Chertoff Group. Thanks, Jim. Kick it off this morning and welcome both of you. So first off, Jim, a little bit about this event. What is this event and what is Chertoff trying to accomplish with this little bit of a road tour? Well, so I think it's important to know that we're passionate about the importance of security. I mean, with Secretary Chertoff and Chad Sweets' background, they were at sort of the ground floor of seeing the importance to our country. So we created the firm to focus wholly on security and to help firms with the whole life cycle of issues as a risk, as a business opportunity, as a catalyst for growth.  There's a bunch of interesting identity technology issues that are coming to the surface and other technology issues. Why don't you bring a group together and do it? We said, well, we're not an event company, but we went ahead and had a conversation back in DC. It was a big success. And then it was a little bit like that line from the Godfather where they say, they keep pulling me back. They keep pulling me back.  We've been to Silicon Valley three times, New York, Houston, and then DC. And each time the idea is make it topical to the local community and make it topical for the issues at hand at the moment. It's interesting the relationship and security specifically between government and technology companies. We do a lot of big technology shows and at IBM and HP, they're like, with the customers that we have distributed around the world and the regulations and compliance issues, in some ways we know more from a broad base of these global international customers than the government. On the other hand, the government's driving the compliance and has the privacy issues and hopefully looking out for people. So how do the two work more closely together to deliver better solutions? Well, in fairness to the government, the government also has access to information and intelligence that the private sector doesn't have. So there's kind of, each brings to the table a certain set of capabilities. And part of the challenge is to have people speak the same language. The government has tended over the years to develop a very rigid system of procuring, of interacting with the private sector out here in Silicon Valley and in other tech centers. There's a lot of focus on being innovative and nimble and sometimes those two cultures need to be bridged. And actually one of the things we started out doing was trying to bridge those cultures, helping the technology companies understand some of the objectives that the government had in terms of security and the economy and helping the government understand what's out there, what are the capabilities and the techniques that you might use. Because without an awareness of the art of the possible it's very hard to lay out a strategy for securing cyberspace. Right. And the whole security space to me, we talk a little bit before we turn the cameras on, feels like insurance. You know you gotta do something, right? You can't go unprotected. But by the same token, you can't be 100% but do you invest forever, right? Because at the end of the day for a private company, you know you have limited resources, government too. So when these conversations are happening and then what we're talking here about the boardroom, right? The worst way a board member wants to get involved is when you read the Wall Street Journal on Monday morning and he sees that his company has been breached and he's in the big, big trouble. So how is the relative importance of security investment changing in the boardrooms? What are you seeing? How is that evolving? So from my standpoint, it's about first of all understanding it's a risk, not security. You're managing the risk. You're not guaranteeing people nothing bad will ever happen. The analogy I use, as I said to people, it's like physical health.  The doctor would throw you out of the office or you'd have you committed. What you do is you say, look, doctor, I'd like to be healthy. I'd like to have a healthy immune system. I'd like to keep most of the bacteria and the viruses out of my body, but I'd like to know if I do get invaded by bacteria or viruses, which will inevitably happen. I've got a system that can detect it and the white blood cells will eliminate it. That's why I get vaccinated. That's why I do other things to keep my immune system up. And that sense of managing expectations, I think, is critical for the board. If the board wants a guarantee we will never get hacked, then it's not realistic. If the board wants to understand what are the most important parts of our body politic, our corporate body we have to protect, and how do we build layers of defense to keep us healthy, then I think you can have an intelligent discussion about how much investment is enough. Right. But then as you said, you want to be healthy, but then we still go to bars and have a drink and we eat ice cream when we probably shouldn't. So in the security, so many of the percentage of the security problems are caused by people that didn't update their patches or they're responding to this great opportunity to get a bunch of money out of an African prince. So how are we changing the culture on the people process? You made an interesting comment about culture. We always talk about people process and technology, but you threw the culture piece in, which I thought was a pretty interesting twist on just people. I think that's a key piece and it's an area where the board can actually lead and this is when it has to start from the top. If management and the board says, hey, this is a technical issue and we're just going to leave it for that security team down the hall, I think you failed out right out of the gate. You need a CEO led cyber conscious culture, security conscious culture that shows that we value it and that ultimately you're going to spend time and money to reward the behavior that you're looking for to then retain and grow that organization. But it's then looking at it both as a risk, as Secretary said, but increasingly, it's part of an opportunity. It's part of an opportunity to engage your customers in a new way, show that you're really a trusted partner, you value and will hold private the information that you're collecting about them. As we hurdle into IoT and driverless cars that are generating massive amounts of information, more and more people are going to want to do business with people that are good stewards of that information that they collect. And I think the interesting thing that came up as well is it's not read the technology, it's not even the breaches, we talked a little bit about the whole iPhone encryption thing, now we all have Alexa sitting in our house, is Alexa listening all the time? I heard of a case where they actually went back to the Alexa on a domestic dispute or domestic violence to see if Alexa had collected evidence and listened into this domestic violence attack. But the privacy issues are tremendous. So as all these things get weighed, again, you made an interesting comment. How do we define success? What does success look like? Because it's not never, in the financial services industry, your worst nightmare is too many false positives as you're turning down people's bank account credit card. So what does success look like? How should people be thinking about success? Well, so I mean, and I think there are a couple of different dimensions to this, as Jim mentioned earlier, I mean, to the extent you are a steward of other people's data, your ability to promise them it'll be secure, it'll be private, and then execute on the promise is an important part of your business proposition.  But you're raising something with different issues, which is we do make deliberate decisions sometimes to bring into our homes and to our lives the kind of collection of information that is a feature and not a bug. That's gotta be deliberate decision because once you collect the information, as an example of the Alexa recording of some domestic disturbance, that's gonna be there for somebody else to get using a lawful process or otherwise. So part of, again, the process of culture and education is always asking, why do we wanna collect? Why do we wanna hold? What are we connecting to? You can make an intelligent decision, but you've gotta ask the question first. Right, right. Although I heard an interesting twist on that one time where even if you go through that analysis and you say, okay, based on these, on yes, yes, and this is why, we're gonna collect this data, which you don't know is what someone else might do with that data in a different scenario down the road. So even if you're a responsible steward of that activity, there's always a chance of something else could happen. So it's even kind of a double. I mean this is one of the byproducts that people talk about with big data. And it's a techie term, but people talk about a data lake where we're collecting this, we're collecting this, we're collecting that. In and of itself, there's not sensitive information. But if you connect different breadcrumbs about a person's activity and their identity, wow, all of a sudden that can be incredibly sensitive. So that's one of the issues that we've been dealing with in the tech community is how to enable us to collect that information, make good decisions from it, but understand the resultant security issues that come. That's a fascinating issue because I think what a lot of people don't understand is, although individual items collected may seem fairly benign, the ability to aggregate and store all the amount of data is huge. And the perfect example is, people always walking around taking selfies or pictures or putting things in their social media. And the third party's never really get into that. And I normally say, well, let's find someone who took a picture of me, it's gonna be in their house or whatever, who cares. But if it's all up in the cloud and someone has the ability to aggregate all that, and all of a sudden get a picture of everybody who's ever taken a photograph of me or mentioned me or I've had some interaction with, all of a sudden, unbeknownst to me, someone could really get a 24 seven picture of all of my life. So how do you deal with those issues? Some of these are legal questions, some of them are technical questions, but I do think we're on the cusp of having to have some serious conversation about this.  And I thank you for taking a few minutes to come sit down with us. So I just want to kind of wrap up again with the board. As you talk to the boards, and we've talked about kind of things that are happening now, things that happened in the relative recent past, as you look forward, what's kind of your takeaway for them as you've sat around, you've talked about all this kind of crazy scary stuff and how they should think about it, as you tell them to look forward, what's your advice? Well, if I could start with that. So today we released some results from a study we did around this topic, is what do boards really think about security? Is it discussed? Is it a boardroom competency? And we interviewed over 100 senior execs, a vast percentage, 40% who were responding as a board member. And what we found was there's a tale of two cities, two cyber cities. If you're in a large public US company in what would be called critical infrastructure, finance, healthcare, telecom, yeah. The directors and the board, they're very well versed in cyber. It's been discussed, it's part of a risk management program, and they have very good CSOs, good interaction with the board. Then there's everybody else. And I would say this actually reflects the boards that I sit on, is that, you know, cyber's not discussed. It's maybe in reaction to a breach, but it's a technical discussion. And most directors self report, we're not where we need to be on education. So then just quickly as a finish, what we launched today was a seven point plan, a blueprint for directors to help guide areas that they can ask questions, document, review, kind of move them up their cyber literacy curve. I think the other thing I would say is this, and I really sympathize with this small and medium enterprises, which simply don't have the money to invest in terms of building up a whole standalone security system. I think that takes us more and more to outsourcing some of these functions. Some of it is the cloud, because you put your data up there. Some of it is outsourcing the intelligence and information to know what's coming. It's managed services, because most of these smaller companies, even if their heart is in the right place, they just don't have the scale to do what a major bank, for example, can do in terms of an operation center. Yeah, I think that's such a big piece of the cloud story, you know, sitting through some of the James Hamilton Tuesday night at a Divis or event, if you ever get a chance to go to that, and he talks about the investment into infrastructure, security, networking, you name it, that Amazon can make at scale, that nobody else, except for a very small group of companies, can make that type of investment, they just don't have money. All right, well, we'll leave it there for now. Really appreciate you stopping by, great event, and thanks for having theCUBE. Thanks for having us. All right, it's Michael, Jim, I'm Jeff, you're watching theCUBE, we'll be right back.


Over the last couple lectures, we were looking at how we can use the Hammett equation as well as the Hammett plot for a particular reaction to figure out the nature of the intermediate or the transition state in a particular reaction. And we had seen examples where the Hammett equation could be used to get information about the intermediate and the transition state and we had also seen how we could use the Hammett equation to distinguish between mechanisms. We also saw that in reactions which involve conjugation of a positive or negative charge with the aromatic ring, there is a need to introduce two new scales and I had introduced you to the sigma plus as well as the sigma minus scales. So, before leaving in the last lecture, I had asked you a question, I had asked you to think about why for this particular reaction which is formation of a semi-carbazone, two different rho values are observed. So, for electron releasing groups, you have a rho value of 3.5 and for electron withdrawing groups you have a rho of minus 0.25. So, the first thing always would be to write the mechanism for the reaction. One hint I can give you is that in this case the difference is seen due to different rate determining steps. So, for those of you who have the mechanism written down and in front of you, what I would like you to do is now look at the mechanism carefully and identify whether rate determining steps could change depending on the substituent. So, it might happen that for an electron withdrawing group, one step is rate determining whereas for an electron releasing group, it is a different step that is rate determining.  So, if you are trying to write the mechanism for this and you were having trouble, let us walk through the mechanism. So, you start with the aldehyde and you have a substituent at this position. So, this is the aldehyde and it is reacting with. So, you have a large group here, but I will just place this, put this as R. So, I am not writing the rest of the molecule. So, in the first step what will happen is you will have attack of the NH2 lone pair and what this would generate would be an intermediate as shown here. So, this would be the intermediate that is generated and then you have this proton transfer and it will give you, so it will give you this neutral molecule. Now, once you have this, you can again have protonation to give you, we are just converting this to a better leaving group and then you can have water leaving to give you this charged intermediate. And once you have this charged intermediate, again it can lose a proton to give you the product. So, this is the mechanism for this reaction. Now, in these, in this mechanism, these steps occur pretty quickly. So, this would be a fast step, this would also be fast.  Now, let us look at the situation when you have X as an electron releasing group and X as an electron withdrawing group and I will let you think about this first before I tell you the answer. So, if you have an electron withdrawing group, which of these steps will go slower? Will it be step A or step B? So, look carefully at both these steps and try to rationalize which step will go slower if you have an electron withdrawing group. Similarly, if you have an electron releasing group, which of these steps would go slower? So, if you want to spend more time thinking about it, you can press the pause button in the video and think about it. So, what you would see is for an electron withdrawing group, what happens is your reactant here has an electrophilic center here, delta plus, where the NH2 lone pair attacks. Now, if you have an electron withdrawing group, what it would do is it would increase the electrophilicity at that carbon. In the case of the intermediate, because you have this zwitterionic kind of intermediate, there will not be much of a difference between an electron releasing or an electron withdrawing group. But the reactant, there would be an effect if you have electron releasing versus electron withdrawing. So, now a question to you is, in which case will the reactivity be more or in which case will the electrophilicity be increased in the case of the electron withdrawing group? So, in the case of an electron withdrawing group, because you are now pulling electrons from the carbon, what happens is you increase the electrophilicity or the delta plus. So, electron withdrawing group would be more reactive. Now, whereas if you have an electron releasing group, what it does is it decreases the delta plus at the center and because it decreases the delta plus, the reaction would be slower. So, step A would be slower for an electron releasing group. So, we will call this RDS for electron releasing group. Now, let us look at step B. Now, what is happening in step B? You are generating an intermediate here which has a positive charge. So, if I were to write the resonance structure for this, it would be, so it would be a carbocation which is now in conjugation with the ring, alright. So, now in this case, what happens is when you have an electron releasing group, it will stabilize this carbocation and the reaction will go quickly whereas if you have an electron withdrawing group, it will destabilize this intermediate and the reaction will go slowly. So, essentially this step would be, so this is destabilized by electron withdrawing group. So, this would be rate determining step for electron withdrawing group. Now that you have both of this information, can you now figure out why the row value is different for an electron releasing group and an electron withdrawing group? So, when you think of an electron releasing group, you only think of step one. So, if you look at step one, in the case of step one, the lesser electron releasing the group is, the faster will be the reaction rate. So, now again think about the scale that we were talking about earlier, as the group becomes more and more electron withdrawing, the rate increases. So, you have a positive slope and the value is given by 3.5 whereas what happens is for an electron withdrawing group, what happens is that step B becomes the rate determining step and in the case of step B, as the group becomes less electron withdrawing or in other words more releasing, the rate increases and you have a negative slope. So, this is a very interesting example where you have a fine equilibrium such that depending on the substituent, you can change the rate determining step from step A to step B. So, now I have another question for you. Now that you know the values for ERG and EWG, what will the Hammett plot look like?  So, you have log of Kx over Kh versus sigma where rho is 3.5 for electron releasing group and minus 0.25 for electron withdrawing group. So, you can go ahead and do this exercise. So, now if we try to draw the Hammett plot, so you have log of Kx versus Kh and on your x axis you have sigma. Let us take this as the point where you have 00, so your hydrogen would be somewhere here. So, as before sigma greater than 0, you have electron withdrawing groups, sigma less than 0 you have electron releasing groups and sigma 0 is hydrogen. So, what you see is you have a positive slope for electron releasing groups, so electron releasing groups are, so we are talking about this quadrant now and you have a positive slope, so it will be and a slope of 3.5 which is pretty large, so it will be like this. So, for electron withdrawing groups you have a negative slope and the value is not much, I will just delete this hydrogen, so you have a slope which looks like this. So, another thing you can see is that electron withdrawing groups do not have as much as an effect on the reaction rate as the electron releasing group. So, in this case you have a negative slope and in this case you have a positive slope. Remember since hydrogen will have to be 0, you cannot have anything with a negative slope coming in this quadrant which is to the left and top of hydrogen which is this area. So, you cannot have anything coming there. So, this is one illustration where there can be deviation from linear free energy relationships and here it is because the mechanism is same, but the rate determining step changes. Let us look at another interesting example, so in this reaction you have an acid chloride getting converted to a carboxylic acid and here again what you see is you have different row values for electron releasing groups and electron withdrawing groups. So, now the question here is why do you see different row values depending on the nature of the substituent. Here I will give you a hint, it is not because the rate determining step changes, but it is because the mechanism itself completely changes if you have an electron withdrawing group or an electron releasing group. So, what I would like you to do is I would like you to think about this and see what could be the mechanism for each of these reactions where you have an electron releasing group as a substituent or an electron withdrawing group as a substituent. So, go ahead and you can write these out on your sheet of paper. So, let us think of possible mechanisms. One mechanism could be where you have, so you have an electrophilic center at the C here and then if I attack water here and then you have subsequent steps of proton transfer etc. would be faster. So, I am not going to write the rest of the mechanism, you can do that yourself as a homework. So, this is one possible mechanism. What would be another possible mechanism? Another possible mechanism could be, so you can imagine this giving you, you can either imagine it coming like this to give you or you can think of it. So, this is an alternate mechanism. So, now let us carefully look at each of these mechanisms. So, if you have x as an electron withdrawing group, what would be possible? So, if you have x as an electron withdrawing group, the electrophilicity here would increase and so this would end up being more reactive. So, an electron withdrawing group, so just as we had seen in the earlier case, an electron withdrawing group increases electrophilicity whereas if I have an electron releasing group, so since you are not talking about a very strong nucleophile here, if you have an electron releasing group, it would be not as reactive as when you have an electron withdrawing group. So, you can say that this mechanism favored for electron withdrawing groups. Now, if you have an electron releasing group, what it would do is, it would stabilize this intermediate. So, it would stabilize this intermediate which is why the alternate mechanism would be favored for electron releasing groups. So, now that we have these two alternate mechanisms, can you rationalize why you have a row of minus 4.4 for electron releasing group and row of 2.5 for electron withdrawing group. So, in the case of an electron withdrawing group, we are talking about the mechanism where you have water attacking. So, again as I told you earlier, if you have the energy versus reaction coordinate diagram for this, what you would see is that if this is hydrogen, if you have an electron withdrawing group, what happens in this case is that the energy of the reactant or the electrophilicity is increased, it is more reactive and the effect on the transition state is not much. So, let us say X is equal to NO2. So, what you see is the reaction is favored and which is why you get a row which is greater than 0. In the case of an electron releasing group, what you have is you have an intermediate which looks like this. Now, here if you have electron releasing groups, this will highly stabilize this intermediate and which is why. So, you see that the value of row is less than 0 and the magnitude is also very high because you have direct conjugation with the aromatic ring. One can also imagine a scenario, say you have an electron releasing substituent such as OME with your acid chloride. You can also think of a situation where you actually generate a ketene like intermediate, alright. So, now that you know how this reaction varies depending on nature of the substituent, can you go ahead and sketch out what the Hammett plot will look like. You can pause the video and go ahead and sketch out the Hammett plot. So, what you would see is, let us say this is the point where you have your 00 of hydrogen. In this case, you have a negative slope for electron releasing groups, which is why here where you have electron releasing groups, remember on the left side of your x-axis you have a negative slope and you have a positive slope for electron withdrawing groups. So, on the right side what you have is you have a positive slope. So, this is what your Hammett plot will look like. So, now we have seen two examples for deviation from linear free energy relationships. One is where the rate determining step changes but the mechanism remains the same and the other example is where the mechanism can switch depending on the substituent on the aromatic ring. So, to summarize what we have seen so far with LFER, we have seen the Hammett correlation to give you substituent constant sigma, sigma minus and sigma plus. Now, in all these cases you have a standard reaction or a basis reaction which gives you the x-axis of your Hammett plot. So, this basic reaction is benzoic acid ionization or dissociation for the sigma scale and the effect seen is inductive mainly but we have also seen a resonance contribution when we compare the sigma values and if you were to use this to determine how the intermediate looks for an unknown or new reaction, the correlation factor is rho which is also called as the reaction constant. For reactions which involve conjugation of the positive or negative charge with the aromatic ring, two new scales have been introduced. One is the sigma minus scale. In this case, the standard reaction or the basic reaction is phenol ionization because the phenoxide ion is in conjugation with the aromatic ring. Here the effect seen is resonance effect mainly and you also see a small inductive effect. And here again the reaction constant is rho. And the third one that we saw is the sigma plus scale. In this case, the standard reaction is dissociation of phenyl dimethyl chloromethane similar to what you see in an SN1 reaction. Here again predominantly the effect is resonance because you have the positive charge in conjugation with the aromatic ring. And here again the reaction constant is rho. We also looked at variations of the Hammett equation in terms of the Yukawa Suno equation and the Taft-Topsom equation. Now all of these mainly look at resonance and inductive effects. So in the next class what we will do is we will look at correlations which can give you information about sterics in a particular reaction. So thank you and see you in the next lecture.


So welcome to how to charge the TurboCharge, the Cloud Foundry API. I wanted to talk about a problem that I feel like a lot of organizations have, not just with Cloud Foundry, but dealing with large amounts of applications in general, wherever they may be deployed. And that is, how do you understand meta information about those applications? Not just what's deployed, but the properties, the interesting facts about the application. How can you ask the system what's true about some set of applications? And what can we do about that in Cloud Foundry? So hi, I'm John Fominela. I'm an advisor for Pivotal. So I work with mostly financial services and insurance clients, mostly in the Americas. But we have a pretty broad portfolio of folks that I talk to. And it's those folks who I think have run into this problem the most. They have very large portfolios. They have very diverse portfolios. Some applications that are really new, some applications that are really old, some applications that are Java, some applications that are .NET, some applications that are Node, totally different levels of sensitivity, and so on. So they are interested in understanding at any given moment what's actually running in Cloud Foundry and being able to ask questions of Cloud Foundry tell me how many of these applications are sensitive or tell me what billing code I should use for this particular application, and so on. And this is a problem that may not be apparent at first glance. I want to kind of show you the way that I think about it to maybe reveal what kinds of solutions might be appropriate to it. And then we'll see what I did with a couple of case studies for those clients and hopefully you can apply them to your own Cloud Foundry foundations. So like I said, the fundamental problem is one of metadata. What I mean by that is we're interested in, if we have some application, being able to tell the foundation or foundations about that application properties that are true that aren't part of the application itself. So for example, you might have a contact person for an application and you might want to tell Cloud Foundry, hey, the contact person for this application is Bob or Alice. You might have a billing code for the application that describes how the foundation should charge back money to whichever line of business is deploying that application. So that's another fact about the application you'd like to store close to Cloud Foundry, ideally. And then you may also have things like the details about the sensitivity of the application. Does it contain classified information or a personally identifiable information that might be subject to higher levels of regulatory or auditing and compliance scrutiny. So all of these things are facts, are examples of facts that we would like to record about the application with the application or at least very close to it. So we have that application. Now it's not good enough just to store those facts, because later we want to be able to ask a question like who's the billing contact for this particular application or maybe you want to ask a question not just of one application at a time, but a set of applications, maybe all the applications running on the whole foundation. Which of these applications contains sensitive information? I need to make sure that they're on this isolation segment or which of these applications has this billing code because we're going through a financial restructuring and we have to send that charge code to somebody else. So there are lots of kinds of questions you might be interested in asking not just of one application, but of many different applications. And you might have many different kinds of questions you want to ask your foundation. And ideally we have some mechanism by which we can verify that the facts that we said before about the application are or are not true for a specific application. So that works for like one or two or three applications at a time, but what happens if you have a lot of applications? Right now we're maybe going to rely on something like the APIs that are provided by the foundation to make sure that we can answer those questions. But there's some problems with that. So let's say that we have a collection, not just one application, but many applications running on our foundation, right? And let's say that some of those applications have a property that we're interested in. Maybe it's an application with a specific billing code, for example. And we'd like to find all the applications in our foundation that have that property that have the property of interest. So all the applications with such and such billing code or all the applications with Alice as the contact and so on. So we again have some way of identifying those applications. We are querying something, we don't know what it is yet, but we're querying something to get us the answer to that question. And then ideally we get some set of query results that is in fact the set of applications that that represents. So the kinds of questions like I said before that we might be interested in are things like chargeback, who gets billed for this application or contact info, who's the responsible party or the security contact, who gets notified for this application if there's a breach. Maybe you have a global security contact like security at mycompany.com for vulnerabilities, but maybe you have a specific contact for that application that needs to be notified. Maybe you have questions about sensitivity, which applications use personally identifiable information or MVUS, which applications are subject to hyper regulations or regulations about how we store healthcare data and private information about people getting medical treatment. Or maybe even more technically, which applications are using a particular dependency? Maybe you're interested in tracking something like I say dependency, I don't mean something like the root FS, but rather something like among all of my Java applications or all of my Python applications, if they use this specific library, it might be interesting to track which of those applications has those dependencies. But if later we get a CBE about that specific library, I'll be able to tell all the owners of those applications, hey, you have a vulnerability in this and we know that you're using this library. So it sounds like I think a useful ability to have, so a natural question might be, can we get this in Cloud Foundry? So the way that metadata kind of works in Cloud Foundry right now is that it doesn't. So the closest thing that you can really get is the manifest and it seems like a maybe a natural place to put this information. Like you'd want to, we already described properties about the application in the manifest, maybe that's a reasonable place to put some of this metadata. And so you might have something like, okay, maybe there's a metadata section that we add to the manifest. So how might something like that work? Well, when you see that push with that manifest, you know, of course we're gonna zip up the directory and everything that you're pushing from, then we're also gonna include all the manifest data and then together that will form a payload that we'll send to the Cloud Controller API. And so that payload is going to, you know, go over HTTP to the Cloud Controller API. But what happens when it gets there is that the manifest isn't actually stored anywhere. Instead, the manifest is read for properties that match one of a set of named keys. And anything that's not in that set of named keys is just dropped. So you can have anything you want in the manifest, even if Cloud Foundry doesn't know what to do with that and that won't be a problem. But those properties will not be stored anywhere. So the Cloud Controller API is not remembering anything that we put in the manifest. So this doesn't really work, even though that seems like it would be a great place to put it, it's not really gonna be useful for our purposes. So if we can't use the manifest, what are the strategies we could use if we wanted this sort of flavor of capability? Now, whatever strategy we come up with, we'd want it to basically have three properties, I think. We don't want it to be invasive to a user's workflows. We don't want the user to have to do something weird or different about pushing applications just because we've turned this feature on or enabled it in some way in our foundation. People have to totally change how they push apps. We're probably not making their lives better, right? We're probably complicating things for the sake of adding this feature. So we also want the experience to be seamless and that ideally there should be API compatibility. We don't want to do something that, if there's some other downstream tool chain that doesn't know about the fact that we've got this capability turned on, what we don't want is a situation where now that we turn that feature on, we've broken some tool like concourse that depends on a specific response or the API response. Whatever that format is or whatever that structure is, we don't wanna break that in our future responses. And we also don't want querying. So when we ask questions, we don't wanna have to ask the question of each application in turn. So if we have 5,000 applications, we don't wanna have to ask 5,000 questions. We wanna ask one question to all the applications simultaneously. So we wouldn't probably be satisfied with a approach where we wanna know, like show me all the applications that have Alice as a contact and then that requires I have to ask each of the 5,000 applications one at a time. That probably wouldn't be a good experience. We'd wanna be able to ask one, we wanna send one API request and get one API response back with ideally all of the applications that match our criteria. So I helped write a proposal that has been shipped to CFDF, which the link is in the slides, which I've uploaded. And you can read more about that later. But essentially the proposal is to make it such that if you have an API resource, whether that's an organization, an application, a space, et cetera, whatever that, I'm using resource here in the restful sense of the word resource. And whenever you have a resource of something that the cloud controller API tracks or is aware of, ideally we should be able to put metadata on that. And that metadata could start out really simple. It's just like a label tagging sort of system of just this key, this value. But that's sort of the first maybe place to start. That's not here yet though. So if you wanted this, what would you do? So the first thing you might try is something like environment variables. Like that seems pretty close to having a key value store. And in fact, because that's part of the recognized structure of the manifest, we will get that stored in the cloud controller or through the cloud controller API. So it won't be discarded, it will actually be stored. So you might say, okay, well that gets gonna work because obviously you can set environment variables and obviously you can use that as a key value store. Now what are the problems with that though? So one problem is that you've made, you've added information about the application, facts about the application that require that application to restart, right? So you've said, oh, the billing contact for, or the billing charge code for this application has changed. It's now X instead of Y. Well, in order for that to actually take hold, you have to restart the application. But nothing about what we're telling the application here has anything to do with the state that would be needed by the application itself. It's not like we're wiring up a service or we're changing some property the application depends on. In fact, there are no references to this environment variable probably within the application. So if that's true, then that seems kind of a bad idea to make applications have to restart just because we added some metadata. That's also bad because if I'm an operator, ideally I'd like to be able to set metadata that you don't have to care about, right? Like maybe you as a developer, you don't get to decide what the billing charge code is. Maybe that's something that the organization decides. And maybe you shouldn't even be allowed to change the billing charge code, right? You shouldn't be able to change your bill to get paid by somebody else. So that's true then. You probably don't want to use environment variables for that because you can set one environment variable when you can set any environment variable. So that's probably not the right place to put this. It would technically work, but not ideal. So another approach would be, what if we wrote a CFCLI plugin that shadowed push? So in other words, what if you installed a plugin that somehow overwrote the push command with this new version that would like siphon off the part but have the metadata and store it somewhere? So what if you could say, for example, cf push and then some extra variables at the end that would be interpreted as metadata in some form? So you could do that, but that's actually not, you could write the plugin that is, but you wouldn't be able to actually install it because you can't shadow cfcli command. So you can't overwrite push or bind service or anything that's a cfcli command. So that doesn't work. And maybe the next best thing is, what if we write a plugin but you don't shadow it? So you have to change your workflow then, right? You're not typing cf push anymore. You're typing cf metadata push or something like that. And then that could work, but again, now we're asking people to change their workflow. Every place that we use that API would have to be updated every place. So my continuous integration pipeline that was pushing applications to Cloud Foundry I'd now have to also say something like, yeah, please use cf metadata push instead of push. So it would technically work, but again, not the greatest idea just because, well, first of all, you have to convince everybody to install this plugin, right? I mean, now you have 5,000 developers making sure they all do that correctly, keeping their plugins up to date. So you kind of have a different sort of a problem. But again, it technically would work. So all of these approaches that I've described before that technically would work, they kind of fail that third test though, which is that we don't want querying to require enumeration, right? So you can get the data in there into Cloud Foundry, but when you want to get it out again, there's no API that says show me all of these, show me all the applications that have this property.  So they're taking the package as is and they're running Cloud Foundry as is. So they're not going to have the ability, they're not going to have the ability to do this third part. So is there a way to kind of do that third part? And the answer is yes, there is, it requires a little bit more elbow grease than the approaches we've seen before. And this is one that we use them in case study, but I'm going to describe later. So the way this works is that you, everything's the same from the developer experience. So nobody changes anything about that, but the end point, the Cloud Foundry API end point is proxied through an HTTP proxy before you actually get to talk to it. So it's almost like there's a route service interposing in the way, but whenever somebody says CF push or CF anything, they're really making a HTTP request to the Cloud Controller API endpoint, right? So when they do that, they're hitting an HTTP endpoint. So that means that if you're hitting an HTTP endpoint, you can also proxy HTTP. And what this proxy does is it looks at any information in the manifest that you've sent over and it will read the manifest first before it gets to the actual Cloud Foundry API. So there's a step in the middle that looks at your manifest and decides if there's metadata in there that you're updating or changing or whatever. And then this step is owned by the continuous integration pipeline. So people aren't typically pushing their applications directly to some production foundation. They're maybe updating a source control somewhere and that triggers the continuous integration pipeline which then triggers a push to the production foundation. But importantly, this pipeline stores the metadata that's been extracted from the manifest into its own separate data storage. It's nothing to do with Cloud Foundry. So it's separate wherever you would store the rest of the information about your application in the continuous integration pipeline. You're also storing some additional metadata about that. And this is, I would say, a fairly natural fit for most organizations because they often use things like Artifactory or some other repository of stuff that represents the inventory of all their applications. So it's usually a fairly simple matter to say, oh, yeah, well, I'm also gonna store some extra key value pairs in my Artifactory or in some entirely new data store. So that takes care of the storage part. How do we get the querying part? There's a couple of ways to do that. In the case study, we wrote a small API shim that all it does is provide a few Boolean type operators for being able to ask questions for this data store. But depending on what that data store was, you could very easily just use the continuous integrations pipe, use that data store's native operators directly. So for example, if that's MongoDB, there's a fairly expressive set of operators you could already use, or if it's Redis, there's a fairly expressive set of operators you could already use. But we wanted to put something in front of it so that no matter what you chose, as the storage engine, you would have this sort of, as long as you used a compatible storage engine, no matter what that was, you'd have some way of sort of querying the data store where the metadata wasn't. So we just wrote this very small API shim. It's about 400 lines of go. So if you want to ask a question now in the future, you just use that API shim. So later, after you've pushed the metadata, after you've updated something, now you want to say show me all the applications that have Alice as a contact or show me all the things that have such and such person as a security contact or this billing charge backcode, et cetera, then you're gonna use the API shim to do that. So how did this work? So what I did was I sort of proposed this idea to folks who were interested in the CFDF proposal but were not able to, they wanted it now, basically they didn't want to wait for the proposal to be implemented. So I said, well, okay, the proposal isn't implemented yet. Here are some strategies we could try and we basically went through the list of the stuff in section two that I told you about and I kind of rejected all of them except the proxy approach. And what we tried for our trial methodology was these three firms that expressed this interest and I asked them for one non-production foundation and one production foundation each. So let's try it in non-production and let's try it in production under the hypothesis that the kinds of questions you might be interested in asking about non-production applications are different than the kinds of questions you might be asking about production applications. So we wanted to make sure that if they were doing these kinds of queries that we sort of covered our bases on both fronts. There's a fairly broad range of number of instances that were covered by each firm. So although they were each doing one non-production one production foundations or the number of foundations was the same the number of application instances being covered by those foundations was quite different about a 2.5x to 3x difference between the smallest and the largest. They also chose different data stores. So one chose at CD which is a fairly simple key value store RAF consensus all that stuff. So clustering and then the other two chose Redis. Again relatively straightforward key value store much better querying and much better I would say higher level sophistication in terms of the operators you can use then you can use with SCD. And so what actually happened? So they basically all followed the structure I showed you before everybody exactly the same API shim everybody is their own separate continuous integration pipeline but they're all using a different data store or choosing which data store to use. And for the trial we basically said you can have either SCD or Redis. So they had to choose one of those two. So how did this work out? So the mean query time was the time it took to ask questions and get responses as compared to the baseline of record everything as environment variables which I thought was the closest thing that will be worth comparing to in terms of what you can do right now in Cloud Foundry with no work. That was about 1,000 times faster than using the API because you don't have to enumerate all of the different applications to get to an answer. You can ask one question and get the answer. So instead of waiting, if you had 450 instances you have to ask each one of those or if you have 450 applications you have to ask each one of those 450 applications do you have this environment variable? Do you have this environment variable? Do you have that environment variable? And so on. There's no way to query and mass environment variables as a key value. And you certainly can't do things like show me which applications lack an environment variable or show me which applications have an environment variable whose value partially matches the substring that sort of thing. When we, so we did this for about eight weeks. I mean at the end of the eight weeks we said how's it going? How's your, how's the strategy working out for you? And the result was about 94% approval that most people said, almost all people said that we would want to continue using it and all three of the firms said that they are rolling it out to all of the rest of their production foundations. So there's nothing that really changes on the foundation side. All you do is add more things to the list of endpoints that are being proxied and then sent to the, and then sent to this data store. So these firms are really excited about this approach because I think it gives them a capability that they don't have today which is really valuable. If you look at Kubernetes or CFCR you're seeing, I mean you see people take advantage at the fact that Kubernetes has tagging and labels all the time on their applications. It's like a very heavily used feature. Once you get above a set, once you get above a sort of the number of pods or number of instances that you can kind of keep in your head at the same time which is everybody running a production foundation of any reasonable size. Then you start needing to be able to ask questions like which of these applications has this property. And so that's why you see people in CFCR and Kubernetes using that capability. So the fact that we don't have it in CFAR or in the Cloud Controller API specifically I think represents an opportunity and I think we're realizing that by implementing the CFJEP proposal I talked about before. So I think there's a reason that all of these firms are excited by that because it's a capability that is needed by operators to be able to provide this as a service to their users. So thanks very much for listening. If you have questions I think we have about four minutes to take them. I know there's a microphone that might be floating around but if not I will listen to your questions and then repeat them for the benefit of the camera. Any questions? Going once. Do you have a sample of your implementation available on GitHub or something? So the API shim is available. The proxy implementation is specific to the three firms and I'm working on extracting that out of their specific implementations. So you can see that on GitHub at github.com slash FJ slash CF API shim. So I will update my slides to include a link to that on this slide. And maybe one further question. You talked about the attributes being provided by the manifest and extracted by your API shim. How do you ensure that for instance the cost center you're referring to is not manipulated by the developers? I'm not sure I understood the question. How does it ensure that? You talked about there are properties which are set by operators in contrast to set by developers like the cost center you're charging to and when you're extracting information from manifest it's provided by developers. Oh, so a couple of things. The API can be used by developers through the manifest but operators also get to use it. And because it's controlled by the continuous integration pipeline they get to act last. So in other words, if you try to set a property you can do that in the manifest but then it will get overwritten by the continuous integration's idea of what the correct value of that property is. You can say my billing charge code is one, two, three, four, five in the manifest but the authoritative source isn't your manifest it's the continuous integration pipeline's understanding of what the correct value of that is. Certainly the operator could make a mistake like nothing would stop you from doing that but there's no role-based access control or anything.  Yes. I had a question because these metadata features has been asked for a long time by users I was and I'm surprised that now that we're trying to pollinate three things like Kubernetes as you said that's native tags are native feature of Kubernetes and your solution does not seem in the core cloud for me. We'd expect a tag to be first level citizen inside the core cloud for me and being able to tag and the solution you propose seems around the core of cloud for me. Do you have any insight of why we don't tackle this inside the API and the data bundle of cloud for me? I'm sorry. So I think I understood the question. I think I understood the last part of your question but is it why, could you sort of repeat that in one question for me? I'm not sure I understood. I wanted to understand why we work around the V issue which is real. It's a lack in Cloud Foundry and we're managing it with proxies and things like this. Yes. Whereas we expect that feature metadata to be core in Cloud Foundry inside the API inside the database so we have something consistent. I think. I'm sorry, I'm still, I couldn't quite understand the rest of that. I'm still recovering from a little bit of cold but I think you're asking what's the relationship essentially between the proxy and the developer? Like why do we use it that way to get the metadata? Is that what I'm understanding? No, no, I was asking why we need a proxy? Why do you need a proxy? Why not just change the API and the data model of Cloud Foundry? Oh, why don't you just send the data to the API directly? Because that would require developers to change their workflow. Right, because if you did like CF push but you had to do it in a special way to get the metadata on there, well then you have to change your workflow. So I wanted all three of those properties. Like you don't change your workflow, it's seamless and querying doesn't require enumeration. So that would break the first rule. If I didn't have the proxy there then developers would have to do something different to get their data into the data stores. That's why the proxy exists at all. Why isn't that just part of the official API? Oh, I think that's the CF Dev proposal. That's what that would be. Okay, so that's the way I understood it as well. At the moment it's this proxy, right? At the moment it's this proxy. Right, at the moment it's a proxy. The CF Dev proposal would make it so that you don't need the proxy because it would be part of the API. But because the CF Dev proposal is not yet here and because Fortune 500 firms are impatient, they said, how can we get this now? So that's the reason for the proxy. That would all go away when if the CF Dev proposal that I mentioned is implemented, you're absolutely right, like you don't need the proxy at all if it's part of the API. But we don't have the API yet. So this is the next best thing. Yeah, right, yeah. Sorry, I can't hear you at all without the microphone. Do you have an idea when this will be available in the API? Oh boy, I don't know if I can comment or I don't know the answer at all to future schedules or anything. I do know that Zach Robinson who is leading part of that effort is here at CF Summit. So he would be a good person to talk to. What's the state of this proposal? Is this still in discussion? Can we contribute anything to it or is it already closed and? Sorry, could you repeat the question one more time? The proposal you mentioned. For changing the Cloud Controller API. In what state is it? Is it still open for discussion or is it finished and waiting for review? So I believe it was published in June or May. Don't quote me on that, but I think it was published earlier this summer. I am sure it's still open for discussion, but my understanding is it's being actively worked on at this point. That's my understanding. Thank you. So if you follow the link in that slide to the proposal, you'll be able to see the actual Google document that has the people's comments and stuff like that. I mean, I did not include a link to the mailing list post where it was discussed, but there's also a small thread on that as well. All right, I think we're a little over time. So if you have more questions, I'd be happy to stay after this and talk to you, but otherwise I hope you enjoy the rest of CF Summit.


The Tabernacle was divided into three sections. The Outer Court, the Holy Place, and the Holy of Holies. The Holy of Holies contained the Ark of the Covenant. That was the pattern that Moses saw in heaven. Now concerning the Holy of Holies just above the Ark, God promised, I will meet you there. The High Priest could only enter the Holy of Holies once a year, and only after having undergone a series of strict protocols. Separating the Holy of Holies and the Holy Place was a curtain. This curtain was torn in two when Jesus died.  And behold, the curtain of the temple was torn in two from top to bottom, and the earth shook and the rocks were split. From top to bottom, God himself announced that through the blood of Jesus, his children have access to his presence. And now we carry the presence of the Holy Spirit with boldness.


Welcome to the series Sustainable Monetized Websites. I'm Aurora and I work in policy education for publishers at Google. My team explained the policies, restrictions and best practices to users who monetize their online content. Before going any further, I'd like to ask you a question. Do you create or manage content online and monetize it? Hi, I wish I could hear your answer.  You agree? Then stick around for this series because there's definitely something for you. Throughout the episodes, I and I Organica, the search champion and I Monetized, the publishing guru. We'll take you through the policies, guidelines, best practices and tools available to you, the one-person show, to ensure you're creating sustainable monetized websites. There's a lot of names used to define who you are. Website owner, business owner, SEO, blogger, webmaster, content creator, content manager, content marketer, publisher. You might identify with some, all or none of these terms. And that's fine. Do you get what I mean? The web is full of terms, such as webmaster or publisher, and that might overwhelm you. In a nutshell, it's not the name or tag you're given. It's what you actually do that matters. At the end of the day, if you're a business owner or a blogger that provides advertising spaces on your site for advertisers to bid on, then you're creating or managing content for online users and hopefully generating revenue from it. I'm aware that if you're doing both, there's a lot of things you have to bear in mind. If you want your site to do well on search, you have to follow a few technical guidelines. Well, if you want advertisers to be able to bid on the ad space on your pages, you have to hold yourself to another set of policies. Sometimes your activity on organic search might receive a manual action, and this could affect your site's performance. Others, your pages might be demonetized due to policy violations. I will not get into technical SEO here. You've got the SEO myth-busting series for that, or the ad content policies themselves. You can find out more about that on the Google Monetized Policies Lightning Talk. What I will talk about are those policies, guidelines, best practices, and tools that will help you have a sustainable, holistic online presence. And what do you mean by that? I mean that throughout this series I'll address policies and guidelines around navigation or unique and original content, for example, best practices to prevent policy violations and how to address these if or when they happen. I'll talk about tools such as the Publisher Policy Center, Search Console and Site Kit useful when used together to improve your online presence. Because although you might think that the organic and monetized worlds are very different, the truth is, no matter who you are, everything can be distilled into this mantra. Focus on your users. Create great content. Are you still there? In the next episode, I'll talk about the importance of healthy navigation. Make sure you subscribe to this channel so that you don't miss it. Like, share, and leave a comment if you have any cool topic suggestions for future episodes. Until the next time, goodbye.


Welcome and Happy New Year. I hope you all enjoyed your holiday break and are back and feel refreshed and renewed and ready to jump into 2017 and make it a great second half of the school year. This week's Wednesday webinar presented by Molly Eschoff is on World Book Web Science and Social Studies Power Modules. These are not brand new modules. We've had them a couple years, but I just want to refresh people's minds that they're there and that they can be used. They're really great online modules that students can work through at their own pace. It really fits in well with blended learning, especially if you have a device or devices in your room for students to work on. I'm going to mostly be showing you in the science power today, but just know that the Social Studies module looks and works just the same way only with Social Studies topics. So the first thing we need to go to the ESU-8 website. I have that right here. Over here on the side panel is the World Book Web button. We'll hit that. And here's the homepage to the World Book Web. Right here your school should show up. As long as your kids or you are in school, you won't have to log in, but if they would want to work on this at home or if you wanted to work on it at home, then you would have to log in with the username ESU-8WB and the password would be orders. So like I said, we're going to look at science and social studies power. Since most of what I'm going to show you is in the science power, I'll just quick pull up the social studies power so we can see the topics in there. These two modules are built for upper elementary, they say. So you'd have to look at it and know your students, but I would say anywhere between four and seventh grade could be using these. And the really nice thing is I'll show you that they have a differentiation model so that students maybe with a lower learning or a lower reading luck style level can also be participating, but same concepts, but a little bit easier reading. So here's the social studies power. We've got community and government, parts of the world, people and cultures, world history and war and conflict. So that kind of gives you the topics and then you will see that it works very much the same. These parts of it, the student center, the assessment, how you would set it up as the science center. So we're going to go back into the science center and look at that one. All right, the science power module covers these areas or topic areas. And I'm going to click on one and I will explain this a little bit more later in the tutorial, but I don't think they touch on it enough. So this little triangle with the rainbow, this is where you would go to differentiate a lesson. And each lesson has that. So if I could quick on living things, you see under each one of here, we've got animal behavior, behavior and survival. If I click on one, it shows the lexile level and a little bit about what's in the topic of that section. If you click down, so this was a 670 lexile, if you click on the rainbow below, you see that it drops the lexile to 420, but still covering the topic of animal behavior. And so students really wouldn't know the difference, the activities are the same. It's just the print reading material is at a lower lexile level. So if you're differentiating within your classroom, you tell your students either to click on the rectangle on animal behavior to do work through the lesson or the rainbow depending on what that they would need. So I really like that feature that's already built in to personalize the learning for the students. I'm going to go back here to the front page. Now I've got a little tutorial that we're going to watch that really explains all the features within the science power. And it's very similar to the socialized power, like I said. So right down here under support under the online tutorials, and you can go and look at these, we're going to look through the science power one. The student center one would be a great, if you decide to do this, a great video to have your students watch and kind of follow as they learning how to use the module because it goes through every step form that they need, including how they can build their profile and everything. So we're going to start right here with science power and supplemental science learning site for upper elementary age children. The site is correlated to popular science textbooks as well as state or provincial standards. It includes differentiated content to help struggling readers master the material and features easy to use navigation for young students. Science power is comprised of lessons across six different units, living things, ecosystems, earth, weather and space, matter and forces and energy. Click on a unit to view its lesson. You can drop to a particular sub-unit using the navigation in the left index column. Each lesson appears in a box with a prism icon below it. Mouse over any lesson to get a preview of the content and see its lexile level. Click on the lesson box to go to a lesson's home page, or click on the prism below to go to the home page of the lessons differentiated version. Every lesson has a podcast of the entire lesson being read aloud available as an mp3 download, links to curriculum and textbook correlations, an extension activity, an experiment and explore more page, critical thinking questions and two quizzes, one on vocabulary and an interactive quiz on lesson content and concepts. The podcast for the lesson contains all the lesson text and has been read aloud by a professional voice actor. It is available in mp3 format and serves as a quick run-through of the lesson content for the teacher and as a study tool for students. The extension activity offers a new challenge to talented students who quickly master the lesson content. Many extension activities will require students to use a chart, map or graphic organizer to record observed data. The experiment explains or illuminates concepts taught in the lesson text. Each experiment lists the procedure in clear steps and uses items that can be found commonly in the home or at your local store. Some of the experiments also contain videos demonstrating the concepts even further. The explore more page offers links to related content. This includes a listing of world book web related sites as well as external sites that have been reviewed by world books dedicated editorial team. Go to any of the world book websites by clicking through the navigation that you see in the portlet. Go to the external sites by clicking on other websites. All of these links can be used to further the teaching of the lesson. Critical thinking questions invite students to take what they've learned from the lesson and investigate it further. The questions draw on science standards and employ scientific reasoning and inquiry. Often they will direct students to world book web articles for further information as a basis of the work. The quizzes for each lesson offer an engaging and fun way of testing students' knowledge of the content with a pressure of track results. Each lesson has a vocabulary quiz and an interactive visual quiz and a variety of formats. The lesson content itself is multimedia rich and uses lexile levels to assure the content is tailored to young learners. Click the arrows at the bottom of the screen to navigate through the lesson itself. On the plains of Africa, hundreds of zebras are huddled together for protection. Toggle the voice audio on or off by clicking on the button in the far right corner of the site. Click on the home icon to view all the screens for the lesson at a glance. Select a screen to go directly to it or click on the home icon again to close the list. You'll notice that the voice audio is still turned off. It will remain that way for the duration of the lesson unless I click it back on. The main idea checks shown at the bottom of each page are intended to give a quick review of what was learned on the page. Click on a button to see the question, then click to get the proper answer. Close out of the window to return to the lesson content. Each lesson also contains a test, which has 10 questions that directly examine the vocabulary and concepts taught in the lesson. The test can be accessed through the finished page following the summary page in each lesson. Students can sign in to take the test and track their own results through the student sign-in located in the upper right navigation of the site. The next few steps depend on the teacher's discretion. If a class has been set up in the teacher center, which we'll discuss next, the student will see this available in the drop-down menu. After selecting the proper class, the student then either will select his or her name from the second drop-down menu or type it in if student names have not been added to the class. If no classes or student names have been set up, the student can still take the lesson test, but results will not be tracked. Only the final score at the end of the test will be displayed, and the information will not be stored. Manage the test results of classes and their students through the teacher center, which can be accessed through the teacher center link in the upper right navigation or through the bottom navigation of the site. Create a profile with the relevant information. Here we have already created a profile, and we'll have signed in for demonstration purposes. Next, establish your classes. In My Classes, you can add, edit, or delete your classes. Click View Reports to see all the lessons that your class has taken so far. Click on a class name on the My Classes page to see a list of students. Edit or delete the class or view classes reports. You can also upload a CSV file of your students or enter them manually. To break down test results by student, choose a class. Then click on a student to see his or her individual test results. In a student's test results pages, the tests that the student has taken will be displayed by lesson. Questions that the student has missed appear in red and are marked with an X. Mouse over any question number to see an overlay appear with the question and the correct answer. Sort the information by lesson title, score, or date taken. Click on the lesson link to go to that lesson's homepage. Now let's view reports. Click on My Reports to see all the tests taken for each of your classes. Select the lesson to see which students have taken the test, their scores, and the cumulative class score. Here you can see which questions your students are answering correctly and which they are missing. These results also will be shown as cumulative scores at the bottom of the report. You also can see an individual student's work by clicking on his or her name. This will take you to a page where you can see all the tests that student has taken, including all his or her results. The Teacher Center also contains links to the curriculum and textbook correlations for the site. For curriculum correlations, simply choose your grade level and your state or province, then see the standard test results returned after clicking Go. Next book correlations, select my book title or cover to view all the content to which science power is correlated. You'll also find teacher's guides and student study guides available in the Teacher Center. These are available as downloadable Word documents and are intended to give the teacher a quick glance at the lesson content before teaching the lesson and to help students study for the site test or the class tests that the teacher has prepared. In addition to the lesson and test content, the site features a new speed that refreshes periodically throughout the day. It also has a biography section titled featured scientist. A new scientist will appear every time the page is reloaded. Use the navigation arrows to get a quick glimpse of a scientist's biography. Click on a biography of interest to read the extended text. All biographies are written to the appropriate grade level and feature a photo or illustration of the scientist. You can also select a new scientist through the left hand navigation. Science power also has an exciting new feature called ask a scientist. View one of numerous videos that answer questions from students around the world. Answered by one of our many panel experts. Mouse over the video to see the question being addressed. Click to play this video or click more ask a scientist to go to a page listing all the videos for the site. You can also submit your own questions through the ask question button in the right hand corner of the page. Finally, the site also offers graphic organizers that are available as a PDF downloadable document. These graphic organizers can be used as seen fit to teach the lesson concepts, aid and scientific investigation or serve as a launchpad for students to create their own experiments and activities. Click download and print. It's that easy. The graphic organizers are available in the science lab section off the homepage and in the teacher center. Science power represents a thoughtful entry into digital classroom learning using a broad range of media text and content that was designed to engage young minds and assist the quest for learning. OK, great. I hope that gave you an overall look at what you can do. If you look on those online tutorials, there's also a teacher center and assessments. It's really great. If you think you're going to do this to watch that it shows you how to set up your classes. You can import your students with a CSV file or you can set up the class and then the students can log in. The one thing is really nice that when the students start a profile or to log into your class, they don't need an email. So if you don't have emails for your younger students, that's OK. They just log in with their name and they make a username and password. And so that's really, really nice about this. The social studies module works very much the same. It has a lot of the same features when you go through it. I would encourage you to spend some time looking at this and deciding how it can be used in your class. And if you need any help, please don't hesitate to contact myself. Molly Ash off here at ESU 8 and I'd be happy to sit down and help you set up your classes. Talk about how you can incorporate this into maybe a center into your classroom. But I think it would be a really great added online learning component that you could put into your classrooms in the new year. Now, if you've maybe covered some of these things, they wouldn't have to do them all. They could just pick and choose a topic to go through the module. Once again, any questions, please let me know and I'm happy to help you and I hope you have a really, really dynamic 2017.