It's time for the home run derby. Up first in this head-to-head matchup, representing the New York Yankees. Number seven, Mickey Mantle. The round has officially begun. That's his first home run, just one minute remaining. That's a home run, his fifth in the round. 30 seconds left. Number seven, ends the round. He ends the round with seven home runs. And he will have to wait to see if that's enough. And now, the challenger, representing the New York Yankees. Aaron Judd. Let's see what he can do. Not that one, his second home run. Just one minute remaining. 30 seconds left. His third home run, meaning that will do it. He finishes with three home runs. That's not quite enough. He's been eliminated from the competition. Hitting first, representing the New York Yankees. Alice Rodriguez. The round is now underway. On to the home run pull. And it's remaining. Another one, go, his sixth home run. 30 seconds left. He ends the round with seven home runs. And he will have to wait to see if that holds up. Hitting second, the challenger, representing the New York Yankees. Edward Encarnacio. The clock is now running. And he's gone, his second home run. Just one minute remaining. On to the home run pull. 30 seconds left. That's a monster home run. Not that one, he takes on the deepest part of the yard. And that ends the round. He finishes with eight home runs. And he has earned a trip to the semifinal matchup. Now hitting, representing the New York Yankees. Number three, Bay. Ruth. Let's start the clock. That one in the bullpen. His third consecutive home run. Just one minute remaining. It's out here at his park. That is now five in a row. Seconds left. That's a monster home run. The time remaining, that will do it. He finishes with a total of nine home runs. And he'll have to hope that's enough to advance. Up to the plate. Not challenger, representing the New York Yankees. Number 24, Gary Sanchez. Alrighty, let's see what he can do. Second home run, one minute remaining. On to the home run pull. There's another one. The draw is six home runs. A first in this head-to-head matchup from the New York Yankees. Number three, Bay. Ruth. Just one minute remaining. Thirty seconds left. That one is gone. His second home run. Deep part of the wall. Time's up. That will do it. He finishes with a total of four home runs. And he will have to wait to see if that's enough. Now hitting the tiebreaker from the New York Yankees. Gary Sanchez. Just one minute remaining. On to the home run pull. Thirty seconds left. He finishes with three home runs. And that won't be enough to advance. Unfortunately, he has been eliminated. Hitting first, representing the New York Yankees. Number four, Lou. Gary. Let's note the clock. Just one minute remaining. Thirty seconds left. No time remaining. That will do it. He finishes with just one home run. And he will have to wait to see if that holds up. And now, the challenger representing the New York Yankees. Number 25, Laver. Chore. The round is now underway. One minute remaining. And that ends the round. He finishes with two home runs. And that means he'll be moving on to the semi-final matchup. Up first in this semi-final matchup. Mickey. Mantle. The round is now underway. The bullpen. That one is gone. His second home run. His third home run. Thirty seconds left. Lever. That one's in the bullpen. Times up. That will do it. He finishes with a total of four home runs. And he'll have to hope that's enough to advance. Now hitting the challenger in this semi-final matchup. Number 30, Edwin. Encarnacio. The clock is running, and the round has begun. One minute remaining. A home run for 30 seconds left. That's his fourth home run. And that ends the round. He finishes with five home runs. And that will put him in to the championship round. Up first in this semi-final matchup. Number three, Dave. Roof. The round has officially begun. That's his first home run. Monster home run. To the deepest part of the ballpark. That's number four in a row. Six consecutive home runs. Just one minute remaining. 30 seconds left. Seven. No time remaining. That will do it. And he ends the round with ten home runs. And he will have to wait to see if that's enough. Now hitting the challenger in this semi-final matchup. Number 25, Labor. Choray. The clock has started in this semi-final matchup. One minute remaining. 30 seconds left. Will do it. He finishes with three home runs. That's not quite enough. He's been eliminated from the competition. Hitting first in this championship round. Dave. Roof. And here we go. It's John. His second home run. His third home run. His fifth in the round. 30 seconds left. There's another one. Got his sixth home run. He ends the round with a total of six home runs. And he will have to wait to see if that holds up. And now the challenger in this championship round. Number 30, Edward. Encarnacio. The round has officially started. So here we go. First home run. One minute remaining. On to the home run point. 30 seconds left. Now hitting from the New York Yankees. Number three, Dave. Roof. Just one minute remaining. On to the home run point. 30 seconds left. That one is John. His second home run. No time remaining. That will do it. He finishes with two home runs. And he will have to wait to see if that's enough. Now hitting the tiebreaker from the New York Yankee. Number 30, Edward. Encarnacio. Just one minute remaining. On to the home run point. 30 seconds left. Times up. That will do it. He finishes with two home runs. And we are still tied. He will enter a three swing swing off to determine the winner. Hitting first in the swing off. Number three, Dave. Roof. And that ends the round. He finishes with two home runs. And he will have to wait to see if that holds up. Hitting second, the challenger. Number 30, Edward. Encarnacio. Let's see what he can do. No time remaining. That will do it. A disappointing effort that time as he's unable to hit any home runs. Ladies and gentlemen, your home run derby champion, Dave Roof.


from San Francisco. It's theCUBE, covering DevNet Create 2017. Brought to you by Cisco. Hey, welcome back everyone. We are here live in San Francisco for theCUBE's exclusive coverage, two-day coverage of Cisco's inaugural event, DevNet Create, an extension of the core DevNet community founded three years ago by our next guest. I'm John Furrier with Peter Burris, our next guest. Rick Taiwaniak, senior director of Cisco DevNet, also the co-founder with Suzy Wee, who's on yesterday. Congratulations on creating DevNet three years ago. Thanks John. Very successful. I said it's blowing up, I'm in a good way, going and doing great, robust community, and also creator of DevNet Create. Congratulations. Thanks. Thanks John, appreciate it. So why DevNet Create? I mean, just give us the quick, why DevNet Create versus DevNet? What's the difference? How should people look up those two events? So yeah, so DevNet Create is our event to reach out to a new community of developers. Typically, an audience that may not have thought about Cisco in the past, may have thought of us as a hardware company doing routers and switching, and we want to try to reach out to that new community to help them understand that Cisco has got a great platform for them to develop on, and there's great opportunity to work with Cisco. And so we want to get to that new audience, and that's what the inaugural vision of DevNet Create is all about. Before we came on camera, Peter asked you a question, you were getting rolling, but we decided to wait. Go ahead, ask the question. Why Cisco? Why Cisco? You know, and we were talking about, so there's a subset of developers, let's call them ISV, independent software vendors, and when you think about the plethora of platforms out there, there's a lot of people that they can develop on. And so you got to think about why Cisco. So when I talk to developers, there's a couple of things. First of all, you start with the platforms, right? So is the technology cool, and are the APIs cool, and can you do something innovative with them, right?  And so the first thing we do is we start off with the technology. And you know, to be fair, a lot of the developers, when you start talking about the technology that Cisco brings to market, they weren't even aware. They just thought it was routing and switches, hardware, they weren't even aware that the network had APIs that they can use, right? Especially in the area of IoT. So educating the developers on what the technology is, is extremely important, but it doesn't stop there. Because, okay, it's cool technology, but if I'm an ISV, eventually I need to make money. So what can Cisco offer me that's unique and different? And there's a couple of things that we do with Insight DevNet, which takes you sort of the partnership area. So if you're out there developing a software product, and you integrate with our platforms, and you develop some APIs, the second thing that we also bring to our developers, who have companies, you see, is introduction to the field and the channel, okay? So how do you, you know, we have one of these, yeah monetize this, we have one of this, so we help them monetize their app. Now obviously it has to be a good app, it's got to be tested and certified. And it has to have some customer traction, but once you get your customer traction, my group is also responsible for introducing them to the field and our channel organization to help them get out to market. And then we also have 13 innovation centers throughout the world where you can do co-creation and get, even if you're early stage, get introduced to customers, Cisco's got a lot of customers in the enterprise, right? We help, depending on where you are in the world, if you're in Latin America, you can go to Brazil, if you're in Europe, you can go to France, and in England, you can get involved in these innovation centers and get out to the customer base and get opportunities. If you go from there, say you get a lot of traction, many times we will put applications on the general price list, so our field and channel can actually sell those applications and get compensated.  And you want to take advantage of, you have to have a good application, right? It has to have the customers want it, but then you can start to leverage some of the field and the channel out there to get your application out to get bigger. Great, great explanation. Thanks for taking the time to lay that out there. My question for you is, and we talked about this on our opening today and our wrap-up yesterday, is Cisco's a huge opportunity. I mean, you have network guys who are really great. They know the operation's cold, and it's known that not everyone has the operation skills. And DevOps has an ops piece, so this is a great direction for you, so we're both very complimentary of that. Question is, what value does Cisco bring to the table because certainly, yeah. You've got monetization, that's going to be great for the startups. What value providing up the stack? Because you have the networks, that's the crown jewel of the operations. Making it programmable, how is that valuable to the developer? Well, so applications that are developed inside the enterprise have to run on the network, right? So everything you have or all the devices that you have in an area of IoT all have to run on the network. So you start with that core sort of functionality that we provide, and then you start adding the APIs, right? Because all the intelligence that was in the stuff that runs the network is now as exposed in an API layer.  And if you go back to the original vision of what we had, so why did you start this thing and what was the vision? So this idea of taking two groups that may have never talked to each other in the past, the networking professionals who really understood the network, software professionals inside an enterprise who really understand how to build software. How do you bring them together and sort of create a community where those two are starting to understand what each other does, understand the skill levels that they have worked together, break down the silos, right? Get out of their tribes, come together in a DevOps environment. How do you run software more efficiently? The innovation's there. You got open source, you got dominated in the app developer market big time. So you bring network guys who know ops to the application guys who don't want to know ops. They don't. And they want to make a share. But increasingly, we talked about this yesterday the network, the evolution of a lot of IT componentry, especially if you look at for example hardware, those server storage, there is a regular cadence of how it's improved. The network has always been a step function. You know, we go from IP forward, IP five, whatever else it might be. There's always a step function and developers have always looked at the network since it's too big and we don't know when the next big change is going to happen as a stable unchanging thing and it never impacted their vision of architecture or how they did things. And we're not too far off from another big step function. It's just goes going to be right in the middle of and having those two groups talk about how to do things today, but also how to do things in a planful way to anticipate some of the big changes that are going to happen in network technology is going to be really crucial for developers to build stuff that's got more than a three month life to it. Right. Do you agree with that? Absolutely. All that came when we took that intelligence and moved it into a software layer because you have the opportunity to make it unstable, not what you want to do. So you have to plan it out, you have to figure it out, but you have to, once it's in software, you have to be able to leverage it and that's what it's all about. You know, the other component of DevNet is an educational component. So what we want to do is teach software developers the value of the network and a little bit about networking and more importantly, what those APIs are. But we're not trying to turn the software people into networking guys. And then for the networking guys, we're teaching basic coding skills, right? So we're not necessarily going to make them a coder unless they want to do that. They could. There's no change to DevNet. But no, it gives an appreciation for what the other group does. And so we have a big educational component. And how each impacts the other. How each impacts the other because they can start talking to each other and working together. And when you start looking in a DevOps environment, it is crossing the hallway to go talk to this other guy in another department. And if we can educate these guys on how to work with each other, I think it's kind of that high level. The ops sharing is happening. We're seeing people sharing the operational roles and you need the people who know the network to do that. Okay, the question for you is how are you going to get the folks who are watching or in the DevOps world, cloud native world on board? Is there a strategy? Or is it going to be a loose affiliation? Is it going to be a formal program? Obviously developer.sysco.com is the site. But this is a great tagline. Infrastructure meets applications and interesting applications meets infrastructure is a really good vision. How do I get involved if I'm not a part of that? Well, obviously come to developer.sysco.com and get involved. Not everybody can hear- Do I raise my hand and say I'm an app developer or is there like a- Yeah. Profiling kind of thing? Yeah, yeah, no there is.  If you come into our learning area, right? There's a learning track. I'm an app developer. I want to learn about networking there. If I'm a networking guy, I want to learn about app development. We have learning tracks that we'll take you through either, yeah. So it's declarative because I can say it and get it. We have events. DevNet create is big, but we actually have events all throughout the year and around the world. So we call them DevNet Express events. We're at Cisco Live. We're also going to be at various DevOps conferences. So sometimes we just have to go to where the developer is. So you'll see us there with our developer, Evangelis. So yeah, no, there's definitely a plan to get the word out there and you're going to see a lot more of Cisco. You know, we've only been three years old, right? If you think about what we've accomplished in three years, pretty significant. But we still have a long way to go. What's the big learnings that you could share with the folks? It could be anecdotal, personal, business from the process of three years.  You weren't sure, the reaction was overwhelming and congratulations for that. Now you got DevNet create. As I said, middle of the fairway for you guys. Did a good job here. Yep. What'd you learn? What's the learnings? It's risk-taking, you know. You got to take risks. You got to fail and you got a mistake and you got to learn from them. So, you know, a lot of us that are in DevNet, including myself, came from the startup world. Okay.   Yeah. Don't be able to take a risk. Don't be able to take a risk. When we had our first, when we started DevNet, we had our first event at Cisco Live. We invested a lot of money to put a developer conference together in five months as a brand new organization. And literally, I remember walking into that event that the Moscone thinking, this could be empty. It could fall on the floor and I'm out of a job. Luckily, when I came up that escalator at 10 o'clock, the place was packed and we knew we had something. And in a classic startup way, you double down. We double down. Yeah, now, and here we are yet. Now we're getting out of Cisco Live doing DevNet create, which is kind of separate from Cisco by design. How do you feel about this event when you walked in here? Did you feel like it's working? I mean, what's the vibe? What's your take on that? Yeah, and I think that the cool thing is we are getting people that would not necessarily come to Cisco Live. Some of them do. And we still have some of our loyal audience here. But yeah, we're talking about new topics. And so, yeah, we see this definitely as the future. We're going to do more of these events and we're going to do them in Europe in places like that, so. We certainly want you to come into our studio and talk more about it. It's something that we're passionate about. As you know, we're glad to support you guys here. It's a great direction for Cisco. And we love DevOps. We love cloud data. We love big data. You guys are on the right track. Congratulations. Thank you very much. Thanks for coming on theCUBE. Really appreciate it. Congratulations. The inaugural event for Cisco DevNet create exclusive coverage from theCUBE. And of course, DevNet, check it out. Go to developer.cisco.com. We'll be right back with more exclusive coverage after this short break. Hi, I'm April Mitchell and I'm the Senior Director of Strategy.


In a case report of the successful management of type 2 diabetes with a lifestyle intervention, a 45-year-old fellow took responsibility for health into his own hands and sought to defeat his disease and get off the drugs by eating foods purported to be anti-diabetic. But how strong is the evidence for, let's say, ginger? Diabetes is reaching pandemic levels and requires safe, affordable, and effective therapies. So what about the potential of ginger in the prevention and treatment? Well, in a Petri dish, increasing exposure to ginger compounds improves blood sugar uptake of muscle cells, almost as much as the popular diabetes drug Metformin. And in rats, ginger might work even better than Metformin, but weight and blood sugar reduction observed in rodent models does not necessarily translate to humans. In this study, a combination of nutraceuticals caused mice to lose 30% of their body weight in one month, but in people, no benefit compared to placebo. I mean, you don't know if something works in humans until you put it to the test. If you feed people refined flour white bread with a cup of water, this is what happens to the blood sugars over the next two hours. But drink some unsweetened green tea with that white bread instead and there's less of a blood sugar spike, same with cinnamon tea. And same with ginger tea, made by mixing a tablespoon of grated fresh ginger in a cup of hot water. OK, but these were healthy, normal subjects. What about the effects of ginger in diabetics? This was the first study of its kind. Diabetics randomized to take a teaspoon of ground ginger a day for two months, hidden in pill form, so they could compare it with identical-looking sugar pill placebos. And ginger supplementation decreased the levels of insulin, which is a good thing, and lowered triglycerides in LDL cholesterol, but without a significant effect on blood sugars. Now, LeCard disease, the leading killer of diabetics, so a 13% drop in LDL-bad cholesterol, would be reason enough to shell out the nickel a day, it would cost to add that much ginger to your diet, but it would have been nice to see an improvement in blood sugar control. I mean, there was that drop in insulin levels, which suggests improved insulin sensitivity, and indeed there was a significant drop in insulin resistance, so maybe they just didn't give ginger long enough time to work? Well, that was two months. How about three months? Even less ginger, just 1.6 grams, less than a teaspoon a day, but for 12 weeks. And maybe ginger can reduce blood sugars, after all, and decrease inflammation, cutting C-reactive protein levels in half. OK, what about going back to just eight weeks, but this time using a higher dose? Three grams a day, or about 1.5 teaspoons, and a significant decrease in fasting blood sugars and long-term blood sugar control in the ginger group, thereby showing the effect of ginger in controlling diabetes. Check it out. The placebo group continued to get worse, the ginger group got better. Similarly, amazing, randomized, double-blind placebo control results for a teaspoon a day for 12 weeks, and for a teaspoon and a half. All better in the ginger group, all worse in the non-ginger group. All significantly different, just because of a little cheap, safe, simple, side-effect-free spice. Put all the studies together, and they clearly demonstrate that ginger can lower blood sugar levels and improve long-term blood sugar control, and at a totally manageable dose. I mean, you could just dump a teaspoon of ginger powder in a cup of hot water and just drink it down. So, overall, adding a little spice to our life may serve as a delicious and sensible way to maintain a healthy body.


Just about your requirements at this moment, but your requirements for the future. Not this future necessarily, good music, but the actual future. And you don't always know those at the time. Jamie, why is my slide not going forward? If you know future requirements, it's a good time to talk about them right now. Because the future applications and enhancements you want to make can affect the decision for the technology you're doing at this time. At the very end, Paul and I have a bunch of examples we're going to give you. Good and bad that we've experienced at Phoenix where we've made decisions and how they've come out. You'll see that there was one where we deployed Drupal, made a decision. Future requirements later dictated it was a bit of a retrofit. So had we known those future requirements at the time, we wouldn't have built it in a specific way. You don't always know that, and we recognize that. So if you know future requirements, it's important to share them as part of the initial build. So let's talk about some of the benefits of Drupal. You want to choose Drupal when you have content management needs, like you spoke about, multi-lingual, portals, file management, image galleries, news, events, content type theming, responsive, compliant, DK, there's a bunch of these types of requirements that fit really nice for Drupal. Drupal is a powerful tool that matches all of your requirements very, very well. So if your project meets those kinds of criteria, Drupal rises to the top very, very quickly. Customization would be an isolated component of what you need, or you don't need customization at all. Budget always plays a role. If you have a limited budget and a limited deployment time, Drupal will work well, because Drupal gives you things out of the box that can get you up and running quickly. Those are some of the criteria that we use to choose whether you're choosing Drupal or not. Some of the benefits of using Drupal include quick deployment times because you leveraged the tools that exist. It's very resource rich. Drupal comes with lots of modules, a huge developer community, patches and upgrades ongoing. You can hit the ground running with Drupal. You don't have to start from scratch necessarily. You get to start with something you've built or configured. Also, Drupal has a number of modules that you can deploy based on your need. These modules you can review and test before building them. So there's less unknown with Drupal. You can take a look at a module, read its requirements, you can even deploy it and test it internally to see if it actually needs your needs or not. You can do all that before you choose it so you can give it a bit of a test run. Drupal is really good for enterprise level clients. Don't think that Drupal can only be used for small brochureware sites. We've got lots of enterprise clients that we've been using Drupal for. You can't handle Drupal. We're going to talk about that a bit later. Drupal is used for all industries. I often get asked, what is the most appropriate industry for Drupal? And quite honestly, it's the entire spectrum. Association, secondary for secondary education, healthcare, government, private sector, technology, health. I'm going to say health twice. Health is important. You can use it for all industries. It doesn't matter. What matters is your requirements. Some of the use cases. So we've talked about this a couple of times already. Do you want to manage content? Or does your client need to manage content? That's a good use of Drupal. Do you have multiple content types? Different types of content that require unique layouts? Do you have multi-lingual requirements? We live in Ottawa, at least by lingual, but we've done websites with, in one piece, 86 languages. So multi-lingual will fix Drupal really, really nicely. Portal login areas, if you are from an association or a member-based organization or require extra net channel capabilities, Drupal is well-leveraged for that. You use the CMS component for the public side and password authentication and login area for all the unique content and tiered content in the backend. Of course, Drupal has UK compliance capabilities, SEO capabilities, responsive theming. And, basically, you're looking for a website. Now, what are some of the drawbacks of Drupal? Depending on what you're trying to do, Drupal comes out of the box with inherent workflows. You can speak up anytime. I just don't want to make you feel like I'm a bargain. I don't know. Inherent workflows. So, depending on what you want to do, you're going to have to follow those workflows or change them. That could be a drawback, depending on the capability of your team or your vendor. Future enhancements. Again, we talked about this with the wrapper future. You have to think about your future enhancements. Will Drupal be the right solution in the future? If you know those future enhancements and requirements, and it's a no, then you don't want to have to rebuild something. There are updates required, as with any software. Drupal requires updates and patches and releases ongoing, and to be secure enough to date, you shouldn't. Yeah. And there has been problems with an upgrade process. I know Drupal 8 is looking to solve that. But typically, if you've gone from Drupal 5 to 6, where we started, 6 to 7, 7 to 8, it's a rebuild. So it's, you know, you get locked into the version that you're on. So that's Drupal. One thing I forgot to mention. If you have questions at any time, just ask me. This is not a chit-chat at you. Just put up your hand if you have a question or interject where necessary. I'm just going to comment, too. Just about that. Good job. When to choose custom? So we talked about Drupal. When do you choose custom? To build a custom application, which means starting from scratch, you're building it in a framework like Lareville or KPHP or anything, but you're starting it from scratch, you have to have a project that requires pretty much a 100% unique workflow and functionality not offered by any existing commercial, off-the-shelf product. So a product. Nothing exists out there that you can leverage. So you have to go custom. It's almost forced into custom, because you can't leverage anything. At least to the point that it makes sense. Maybe you found a tool that gives you 20% of your needs. That's not nearly enough, right? Maybe you have to build custom because of that. The site has a long life expectancy. In our experience, when we build custom applications, they're so tailored to the workflow and requirements and functional needs of the client that they last for 10 plus years. We can enhance the number one, but the base application we build lasts a long time. So you invest the time and money in building something custom and tailored so it's going to last for a long time. Typically, custom applications are enterprise-class applications. They will be used through the business. They will be used every day by certain departments within the business, multiple departments throughout the business, because you're building it to solve business problems. Workflows, automation, streamlining, etc. And so essentially when you have a heavy amount of customization required that's not well served by any cost, you have to go custom. So some of the benefits of custom, it's a really tailored solution, like a nice tailored suit, it fits your needs and requirements to a tee, it looks good, it fits you perfectly. You're not fighting with the CMS and the way it works, trying to force the CMS to work in different ways, and you get exactly what you need right away. Typically it's nice and stable, long-term, if it's well built, because it's built to meet your needs. For the most part, in our experience, we've seen excellent ROI for our clients who have invested in custom applications. We've had a client which we'll talk about later who saved millions of dollars in the first six months of launch by implementing a custom application. That's how much money it saved them. So they can be cost-saving a lot, but they can be good cost-saving measures. And it's typically an enterprise tool. So how do you determine if you need to go custom or durable? Well, if you need a specifically tailored solution where there is no costs available, commercial off-the-shelf tool, you go custom. See to the art application that doesn't exist already, you typically have to go custom. If it needs to be precise and follow a very specific workflow methodology that is internal to your business, it typically has to be custom, unless you're willing to compromise all that and change your processes to work toward a tool. It has to be custom. You're looking for tailored growth. You know that on-going, your future requirements will require very specific custom implementations and enhancements. And let's not forget that custom costs more money because it takes more time to build and it takes a lot more intensity because we're not giving ourselves a leg up with starting with the framework like Drupal. Everything is from the start custom. It's going to cost you more money in time. We always have to top budget because if you don't have budget and time for Drupal or for custom, sorry, then there's really no use talking about it. You're going to have to compromise your requirements of workflow to fit with the tool at Drupal because the budget is for custom. Well, there's a longer build cycle. Obviously, because we're not leveraging a tool and starting midway. Depending on the team that you're working with, whether it's an internal team or a vendor, there could be a high rate of error and inefficiency as the team has to figure out how to build things that are native to Drupal like user profiles and login, file management, all that kind of stuff that's out of the box with the ways. All that stuff that's out of the box with Drupal that you can just use and tailor as you need to build a custom. You have to think about how to build all these features.  So if your team isn't used to building custom applications and it's their first time out, be prepared for a lot of starting over and we've seen it happen. Higer class. With all this tailored solution you have to have more time and effort to build so it costs more money. Often you'll have to have a reliance on the vendor that built the proprietary tool for you so they're the ones that know the tool you're going to have to go back to them for and that could be good or bad playing on a relationship with the vendor. And then any of your enhancements on going will also be custom. If you built the custom solution you can't then leverage Drupal for the enhancements you've got to keep doing everything custom so the cost is relative there. So we've done Drupal we've done custom applications midway in between when you can actually take a tool like Drupal and customize it to your needs. The best time to benefit from this is when you get a project where a certain portion of your needs are well met through Drupal. There's content management needs, there's image management needs, there's maybe the login area, there's lots of needs that suit Drupal well, multilingual, perhaps e-commerce, solar search. All these things are well served through Drupal but there is a component that requires tailoring and customization. Perhaps there are tools and modules that Drupal offers that you could deploy and customize those or there's nothing existing that you have to build it yourself. You have to have a conversation whether it's with your client if you're a vendor like us or with your team if you have an internal web team about these nuances. I don't know if you're going to go through it but I just wanted to find a factor of what you call just Drupal and what we were calling here now, custom Drupal is that a lot of the modules that come with Drupal you can take them and you can keep them a bit to make them do what you need them to do but there are components to a lot of client's businesses that this has to work exactly like a certification process or what not and all those things it's depending on your dev team they'll build custom modules and they'll build workable all the way around that but with most of it We have a good example of this later that will show you like some real world examples where we made the decision to choose Drupal and then customize it for our needs. 80% of the client requirements were specifically well tailored to Drupal and 20% weren't so we did custom Drupal because 80% was met with Drupal so why start custom at that point? So what are the benefits of going custom Drupal? You get all the benefits of Drupal that we talked about you get a midway starting point Drupal gets you out of the box gets you with lots of features like login, wizzywake, all sorts of things ready to go this lets you focus on that 20% customization so you can get up and running really quickly and then focus your time and energies on that tailored part that needs to be customized and not the whole thing just the bits that need to be customized and you can get a tailored experience we've had great success using Drupal and then tailoring it and the client gets a really unique workflow and things that meet their specific needs and it's powered through Drupal what are some of the drawbacks? well they're again similar to some of the drawbacks of Drupal you do have a possibility of fighting with the code more so when you're trying to do custom solutions in Drupal because you're either using a module that you're trying to force in a different way or you're building your own module that then has to integrate with Drupal for the last 10% which is often the longest so if you have 10% customization that can often take 90% of the time to get done so you'll spend a little bit of time knocking your head up against your computer because that last bit is the toughest bit to customize there is a concern with update compliance so if you've done custom modules or you've changed modules and then you deploy your Drupal updates how do those things match together and how do you make sure they don't break or you should have passed this now but I feel like I need to say that and then of course integrating your custom work with the overall Drupal install can have its challenges if you don't know what you're doing any questions so far? everyone's following along, okay great anyone need more snacks? so there you go we've gone through some of the benefits and use cases of Drupal custom and Drupal custom essentially what we're saying is sometimes a real heart to heart with either your dev team or your client to go through what are your requirements now what are your requirements in the future where are we best served what meets your requirements best what is your time run, what is your budget all these things play a factor and we always talk about having conversations we sit as a team, we get a project in we go through the pros and cons where it's not evident very often we get projects that are very evidently perfect Drupal solution often we go back and forth on what would be the best way to leverage this because what we don't want is for clients to hate Drupal we don't want the developers to be mad at them when they're trying to support and build projects we don't want this kind of frustration around web projects you never want to make the project fit the tool you always want to make sure that based on requirements you choose the right solution and then you will avoid this agro alright any examples for you, does anyone have anything to interject any questions so far security, can you talk to security in those three scenarios sure so with Drupal you've kind of got an apparent security you've got a huge global team working on modules there is a downside to that is that if there is a security flaw there's a whole global network of people that I know about so you see a lot with work-pressed with Drupal the bigger CMS is that in terms of if you're a client the global site doesn't get your updates security is employed immediately then you tend to be a target because you're on these larger CMSs with custom you still have the same security risk you have what's called security by obscurity depending on what you use and how you build it people don't necessarily know how to get into it because you've got a custom module that doesn't mean you're exempt from security at all so I'd say that security standpoint it's easier to manage when you're with Drupal because you've got that community with you if you're going custom you're relying on either your vendor or if you're a client you're a third party person community doing it on your security but that's why you're trusting so the web vendor would have to practice best practices and security if they're doing a custom application if they don't know what those are then you're leaving yourself open and vulnerable to their knowledge really good custom application they have to build a security component with it or with Drupal it comes more inherent did that answer your question anyone else okay so we've got some examples of projects that we've worked on at Phoenix the first example is Nokia Nokia is a perfect Drupal client in that all their requirements meet Drupal CMS they want to manage content they have multi multi languages they have multi sites they have dispersed geography multiple publishers faceted search they're hosted on Aquiat everything they want to do it's a massive site it's huge enterprise yet it really is simple in that it's really a content management solution so we manage and deploy and build on the Nokia platform in Drupal 7 and it's perfectly tailored to content management there are no other unique needs for this website within Drupal there's a lot of unique needs but in terms of the fact that it requires managed content do you want to talk to any of you in Aether? no it's a good fit for Drupal perfect fit for Drupal this is an example of a client where they're an association and 80% of their needs are met through Drupal they want it to manage content they need to have a login Drupal provides that they want members to pay their dues Drupal provides that it has a member database you can give them that it's got news, images, galleries all that kind of stuff that's all Drupal they wanted to be able to allow the members to manage their certification these people have to show that they maintain their certification over time they had to be prompted to say you have logged in and now you need to show us it's time for your certification reminders as you log in to have your certification and you had to then upload proof that you've done your courses and there was this whole nothing in Drupal could satisfy that workflow such a unique workflow had so many unique components around it there was nothing we could leverage so Paul built a custom Drupal so we deployed Drupal built a CMP certification management feature as a custom piece in Drupal this you can't see very well it's supposed to be all fancy back end data stuff this is the NavCanada project I referenced it earlier we built this in cake PHP in 2008 and we launched it in 2009 this basically takes all of NavCanada's hiring for air traffic controllers and flight specialists it automates it online where it was previously a manually based process that was a big deal at the time when we launched this it saved NavCanada 1.1 million dollars in the first six months of launch and two hires this is a tool that NavCanada to this day still uses every single day both the admin use it in terms of the fact that prior to this tool NavCanada never knew how many applicants they had where people were in the process of applying for an air traffic controller if somebody in Gander five people in Gander are going to retire NavCanada didn't know if they had enough people in a database ready to fill those positions they didn't include where anybody was one of the biggest problems they had was that they didn't know they would have 20,000 or 34,000 applicants a year and at the end only 200 were making it through to the training they didn't know where they fell off was it at the psychometric testing was it in the interview second interview first interview medical where were these people they don't know how to process no idea because it wasn't in a database NavCanada uses this as a business tool now in the first year we had 20,000 applicants they know exactly how many people are being deployed to Gander and all their different towers throughout Canada who's in what stage where they're falling off in the process over two years so they can make business decisions about that this is a specific, specific, tailored solution that we couldn't have leveraged any path for on the front end and the candidates get to log in prior to this tool candidates would call two years in where's my application what do I do next what happened with my interview like they didn't have a clue candidates each now have a unique login it's got a tab thing at the top or they can see you're in phase three you've passed oh it's pending interview please respond to an interview date or something it's all automated no more phone calls candidates are well informed NavCanada uses this tool to make business decisions this is a perfect example of a custom application okay this is an upgrade screen this is a project that we built in Drupal and this is a bit of a back end screen built in Drupal perfectly suited to Drupal everything they said we were like ding ding ding ding ding bells and whistles are going off this is Drupal no problem we built it we built it and everything's great a year or two later they make an amendment we decide that the amendment can leverage the web forms module in Drupal no problem this is great this is where the requirements perfect fit a year after that they come back and say actually this web forms module that we're capturing all this data for needs to do this that this that this that this that and that's when we realized we should never have built this in web forms it's not the right tool or module for this had we known their future requirements we would have built this as a custom module to meet all their future needs we didn't know that at the time so what happened the client ended up having to compromise on their needs because they didn't have the budget to rebuild this as a custom piece so they just changed their requirements it happens all the time right if you don't have a budget for custom all of a sudden quickly like you want a new kitchen it's going to cost you 100,000 all of a sudden you think okay I'll just reclaim the covers like all of a sudden you change your requirements to meet your budget right that's what this is yeah it was one of our appropriate examples I'm going to get into a second detail you can just put a comment at the box and put forms on the site that you can fill out right and you can make it multiple choice you can add textiles whatever there's also a part of it that you can fill out your own custom components and you can make your own client a question that you can ask to your form so that's kind of the property level so we kind of went that Drupal ended the box with a slight tweak to the module and as Jeff said that's kind of where we fell short when they decided to change their future because they wanted to do more with it it's like well we could have made that fit into the box for a bunch of time and now no longer fits right whereas we went custom Drupal and filled their own questionnaire application that upgraded enhancing elements easier the issue is more the existing units are there right they have if it was something like 10 or 20,000 patents that log in and use these forms and try to enhance it with my form move that in which it's used as a headache I feel like maybe we have a comment from the seats this is my team here part of my team and I feel like they want to jump in and say style and I think this Drupal could have been avoided we had that conversation in advance of like where do you guys plan on taking this it takes off the way you want and if you had the pie in the style then you could have what you want because if you can have that conversation just have a glimpse of what they want or what you want then you could have a look no heaving we had the exact same issue with public works so we did the system on web forms and then they would not scale that out at the very beginning we had a discussion with the client that was the short term solution but the client was so adamant that no it has to be a web form short term for example do what you can as quickly as you can so when that happens what did you tell the client you know that picture where we had the girl talking you have to be honest and transparent and say this will meet your current needs but we had this conversation with the client but be mindful that we may have to rebuild this entire solution in a year from now if it takes off a lot of people will come to us clients will come and naturally they've got short budgets short budgets and short term frames and we'll say this is not the right solution for you but we've got to get up and run it quickly and then if it takes off we revisit the right structure moving forward and they understand that possibly a rebuild might be required I actually had this conversation with one of my clients and what I was just happy to say is that if you do go to a quick route do know that if you had to do it the right way to the end this is what your differences are and as long as they know about it then when they come back and say okay I'm going to do this okay we have lined up the forms when we talked about it it's the same thing we call it expectation setting with the client we always like to be if you go this route or this route here's what you expect a year from now and then they make a decision based on that did that answer your question this is our final example and after everything I told you about all the requirements that you need to make sure you choose Drupal we built a website, Grapevine if anyone is familiar with the Grapevine.ca right, the for sale by owner type thing we built this in Drupal and it is not a CMS so after I told you I had to meet all these criteria multi-cultural, multi-cultural types all that stuff, they said none of that and we still built it in Drupal and it still manages to serve the client well after 5 or 6 years we have many debates internally the motivation for building it in Drupal was time and cost plus the client didn't currently have a tool where they could see how many listings were posted when they were expiring when the open houses were how to approve new listings and all that kind of stuff they didn't have a facility to do that so this tool at least gave them all that in the back end their back end office was well set up for Drupal but the front end really isn't a content management it's a search, right? it allows you to search for homes and deploying something like solar or elastic search will help greatly with that experience and is required in this instance but that's a situation where Drupal wasn't really a natural fit but because there was time and budget considerations and the client had nothing that they could leverage to manage their business with so Drupal was a good fit and it continued to be for 4 or 5 years so there are exceptions, right? where you can build things in Drupal that aren't naturally a fit as long as you have that conversation with the client and they understand the limitations and opportunities provided by Drupal that is our top I would like to know how many people in the room by show of hands are developers how many of you are specifically Drupal developers? okay, so where do you agree you're a developer? we have a page in the web we're just starting to get into Drupal we're just going to do a part of that so we're we invest in Drupal 8 and we start to build okay, great how many people here are like project managers with business or sale business development or sales? of those people that are here is this presentation you're here to listen to this presentation because understanding when to sell Drupal is an important piece of information for you if that would be why this would be of interest understanding when to serve what technology for anyone who didn't put up your hand what do you do? oh, yeah we got a QA girl everyone else doing QA? yeah if anybody here on the client side that isn't a web developer like it's your client side but your developer like somebody who will be looking for web development companies and trying to figure out what to do with their own organization no, that's it okay, I just want to get a sense of the room you with the beer, what do you do? what's that, sorry? developer is developer developer is developer so does anyone have any questions or want to clarify anything that we've mentioned? the presentation will be made available at this link so you're welcome to I don't know if I can always email it out to anybody that can resist it go ahead this is more of a name you don't believe all I'm doing is how many projects are you building on to you? I think we're trying to go over D8 where the requirements fit in that we have a current project coming in that I want to go D8 but the team is convinced that it's got the right modules available for us to build off of and this should be unfortunate because by the time you start the project and finish it six or seven months goes by they might get there but at this moment in time so we are going D8 and have done a bunch of projects in it but it still depends on the requirements of the client and whether the modules are available, is that fair? yeah, so with this project we chose we have efficient chosen I guess you're the first it's great to do this because of that again it's the client time of the project whereas if you have the option to go to play I think it's a good time because even if it might not have a module in place that something that people say it does if you've got the time you can help build it, yeah so that's right we had that conversation when I was pushing 80s and when we would have to build a bunch of modules which we would love to do but we have to work to a deadline so we're at this situation where it's like if we had the novelty of time we would love to do that in a tribute but we have a very short time did that answer your question? yeah go ahead so our concern was yes, agreed yes like we saw that it's like you're stuck where it's like either we invest in building the modules or we invest in rebuilding the whole thing so I think you know how do you quantify both situations that's a valid concern the architecture of D8 is much more stable and better like you might say, the platform just for if you want to lift it yeah and what I would say to that is as long as you set expectations for a good job as long as you set expectations for budget and time with your bosses or whoever it is that's asking you and you've got that ability then absolutely go D8 because it's the platform you want to build on and it won't be decommissioned and supported anytime soon but we are often under the gun and have to serve client deadlines but if you can get that expectations set, absolutely I would go D8 go ahead have you fixed your projects about upgrading from 7.8? we talked about it yeah, we talked about upgrading from 7.8 I'm not to the opinion still that everyone likes to call it an upgrade but I think a lot of times it ends up being a rebuild and I could be wrong your situation is going to be different but I found a lot of times the client comes up and is like oh, we want to build a new version they don't just want to be on a new version they want to change the way the site looks or they want to add a new feature here a lot of times it ends up just being a rebuild maybe you can leverage some of the content or you can leverage some of the structure and the theme but a lot of times it ends up being a rebuild that's our experience anyways are you a developer? I get asked that a lot too like who just upgraded your plane and like oh that's that sounds a lot simpler than it is we need that easy gun we just sort of we have found that some stuff is made let's say slower yes everyone's focus right now is on eat any new thing and it's built entirely different so it's kind of exciting right so anyone else do you have any questions or comments? well thank you very much for your time today we appreciate it


The Senses. Design Beyond Vision. MTA.me 2011 Colored lines spread across the screen, forming a map of the New York subway. When a line is crossed, it quivers like a string plucked on a musical instrument. The length of the string determines the pitch. Alexander Chen was sound by Tim Kahn.


I'm playing with keyboard mouse. I'm not playing with controller Yes, I am high for spider-man actually I'm over here twirling by myself. I'm trying to stay out of the way so I don't die because I really don't want to ruin this run So if you don't see if you don't see me hitting him, that's on purpose. I need some nerca gante points. So I'm This guy says he's got bombs Think I do too He's about dead.  All right, we're gonna help this way We're spamming flash chat that one more. I missed We're gonna craft another one We're not done yet. Whoo. I thought I died. I thought I died Wow, I thought I died there All right, let's hope we get the parts we need from this car Rip rewards. What do you mean? I guess he wanted to capture No, then get it then get it from the car Is there a gun to an elder though? He's like, I don't know. I don't consider him an elder for some reason, but he is He is I Think he's the easiest of all of them. That's probably why Talon care paste dragon scale None of which I need all regrowth plate. I think I needed one of those right So I gotta learn how to stay alive as a hammer user that gets these elders The other fights are okay, but this guy's man. I barely made it through that fight. I need to wishlist this I thought I did I thought I added this weapon to my wishlist. I did But I didn't see it update. All right, so I just need two tails So we did get one part we needed Just need two tails now Reload. Oh wait, she's got a quest now cleanser booster I For my palico Slay Nurgent a We're doing it live So how's life one I've been a while since I've been in stream any large donations I've missed like the last one almost gave you a heart attack That was in January, man No, not really we've been getting a gift of subs every now and then but there's been nothing substantially huge It's the last big thing I got was around yeah, January So it's been a while Been a little bit I'll throw up an SOS in a second grab these two Grab a meal Put that away SOS fired Lego Do I have an idea what's the store for the elite announcement announcement you mean? What do you mean? I know that the chapter 3 is coming out But as far as an announcement is concerned, I'm not sure what you mean I don't know about announcement. I know about the 28th being at the release date. That's the release date of Chapter 3 that miss That shot right through his head chat. What am I getting hit by he's really hard to keep up with I don't have any more Bugs left that hit me. I'll be a little lay on phase 2 gents when you get the chance of try to farm some Wet fish fin plus second. I need some more God bugs and some blue mushrooms, so I'm tearing through this life powder stuff. It's my first melee class chat Apologize if I'm not optimal, but I'm learning. Do I have any bombs? My bomb did absolutely nothing chat.  I went in my mantle back up Should be soon don't press shift during that have a talent cool my goal was to not die I'm learning to fight though. We need 10s What crappy little chat? Oh, we got a horn plus, but More talons I Picked up like all the things. Oh, well No tail from that Well, it's a time limit of 30 minutes, so I think the health is maybe adjusted the health may be adjusted for that Come on. Give me a tell us the reward. Nice. I need one more tail one more tail chat. I made the board That picked up the most loot. I Need more flies You need to grow faster, sir. I need more flies. I'm using them all up There's only four flies. I'm gonna use some points chat That earplug jewel I get a jewel. I did Wow Stop soapel. I didn't I didn't even know I didn't I know So we don't have any more flash pods, but I have bugs Right so I can Crap those bugs so I think I go back here and Refill the bugs for all the great justice. Okay, I'm down to four bugs. I Need more flash bugs. It needs to work faster chat. All right, do it again We will do it alive again. This is the wrong one investigations slate. Nurgurgante. I got six more left We have to get a tail a tail chat a tail of two cities It has been posted Stand back at the pocha the park now I will throw up an SOS again There's multiplayer fix not really Switching the dual blazing hopes that I could cut the tail. Okay Whoops. I ping for no reason Yeah, I've maxed out the bone alpha Except for one piece Actually, I think cross play between ps4 and PC would add more problems to the already complicated issue that we have now Make one more mine. Oh, okay. We got it. I think combining Sony's mess with steams mess Would be a hot mess The hottest of messes Because people are saying that the ps4 had a similar thing during launch and I don't remember it But then again, I got I got the game after launch so it has been a few weeks So I think it had been fixed by then Why is he do that twice? Come on males. It's my attack.   I just I don't know the openings. I got a little bit of it. I did at that time Do I have to let go to charge when I tap because that's Dragon treasure. Wow So I tapped it there and it just Charged the hour you happen. Okay. I'll look at that later tail That's a tail chat Give me give me Give me give me Good job, mr. Good job, mr.  Wow


In particular we're exploring the idea that it's okay not to be okay and we're going to think about how we can recognise the warning signs that a friend might need support with their mental health and think about how we can go about starting the conversation if we're worried. This lesson is based around a video created by some young people at Cape Cornwall School which is right down at the very, very west of Cornwall. I went to visit them recently and they've put together a fantastic resource and some really great ideas to share with you. I hope you enjoy their video and that you find their ideas helpful and that their ideas help you to create ideas of your own too so you can make this your own. Before we get into the lesson I think it's really important that we establish a few ground rules. Now you might be used to doing this from other lessons within PSHE or your wider curriculum but when we're thinking about things like mental health it's really important that we re-establish those ground rules. So I'll give you a moment to talk with your class teacher about ground rules in your class and whether you might like to add any of your own but ones I would suggest are one we need to listen to one another, two we need to respect each other's opinion, three it's important that we don't assume or judge when listening to others' points of view and four this isn't the time for us to be making disclosures and sharing our own experiences about things that are difficult. Those things really matter and I will encourage your teacher to remind you how and when to seek support if you're worried about yourself or a friend but please don't start sharing those difficult things in the middle of a lesson because it's not the right environment. Okay I'm going to pause the video now for a moment so that you can have a discussion with your teacher and the class about the appropriate ground rules before you get started. It would also be great teachers if you could highlight to your students anything they need to know around how and when to seek support if they're worried. Okay so hopefully you feel ready to get started and you feel a little bit reassured by what's been said so far. The lesson shouldn't get too difficult but it's always good for us to kind of on the side of caution because sometimes when we start thinking about things like mental health issues it can turn up some slightly tricky stuff for us. So what we're going to do now is we're going to watch the video which as I say was put together by young people down in Cornwall at Cape Cornwall School. I want you to watch it and as you watch the video I want you to have a think about why do you think the young people created this video, what do you think it represents, what's the story you think it's trying to tell and how does it make you feel and what does it make you want to do. Now you've had a bit of a chance for a general discussion about the video. I'm just going to share with you a few snippets from the young people who created the video telling you about why they made it and what they hoped it would do. The video is about how people don't always show their emotions because they may not feel comfortable to or they just don't know how to describe the way they feel. We made it so people could realise that they're not alone in their struggles and that there is always someone who'll understand what they're going through. We made the video to describe people's mental health and how they can hide it. There's lots of different forms of how people can hide it and why they do it. We made the video to help people in similar predicaments and so that they could have the courage and the ability to talk to a teacher or parent. The video is about a young girl suffering from mental health issues and we made the video to address these issues and explain to people how they can be dealt with. I think we made it and make it a bit easier for younger people with mental health to talk to someone about it and say, well, they're struggling a bit, but it's about young persons struggling but not wanting anyone to know what's going on. We wanted to make the video to show people that it is OK not to be OK and there are many other people suffering from the issues and you're not alone. Now let's look a little bit deeper into the video. There are a few moments that for me really stood out and I'd really like us to think a bit more about. So let's think first about that moment when the girls take the selfie and in the selfie you suddenly see their faces have masks on. I want you to think about what's happening there. So let's watch the snippet and then I'll give you a chance to discuss in groups or as a class what you think this represents. Well, I think it's a showing that they're trying to show that nothing's wrong with them but deep down they know that something is but they don't want anyone to know about it. It's a covering up. Well, it was meant to show how even people who are close to you might not know that they could be suffering from mental health issues as well and it's not just you. It's a very common problem. It's supposed to represent that there is no set pattern of who's got problems with mental health.  It's just a random thing that happens to certain people. Dr. People are suffering from mental health issues and maybe if everyone came together we could all work it out. This part was to describe how it's not just one individual person who has mental health problems. Lots of people face them for different reasons and even if they don't show them they can still be like different severities and things like that. We put this part in the video because it shows that you don't know who could be suffering from the issues and people who are close to you could be suffering from them as well. Another moment in the video that really stood out for me was when the mask became cracked and there was an attempt to tape it up. I'd love you to watch that bit again and have a think about what's happening here, what do you think this represents? Here's what the young people down in Cornwall thought about that. It shows how people can't continuously hide it for a long period of time. Over a while it will start to break down and wear away and things will get worse. The mask cracked in the video because we wanted to show that it can become very hard to keep your emotions in and the girl in the video is desperately trying to hold it together but it became very hard. It's to show that people sometimes certain things can just chip away at the mask and mean that certain behaviours seem to be recurring and show you up more than others and that the person struggling will desperately try and repatch it and seem even happier and more joyful that it will be completely fake. Finally at the end of the video we see the moment when an adult comes and removes the mask. What do you think this represents? How do you think this might have happened? Here's what the young people down in Cornwall thought about that. When the adult intervenes the teacher takes the mask off which is showing how they reveal the student reveals their true emotions to an adult. This means they can get help so it shows that you can always tell someone you trust what you're really feeling and they will listen to you and give you advice. There's always something better and someone will understand you even if it's a teacher or a friend or parent there's someone out there who will understand and have possibly gone through what you've gone through. Well I think it shows that adults and anyone is there to listen to you once you break that barrier of wanting to talk about it perhaps and say once they start talking it's a lot easier to keep on talking about it so just shows that adult then everyone's there to talk to you about it really. This was important because people need to help in different ways so it wasn't just about the adult talking to them and telling like telling them what to do it was about them listening and then them talking back and also the child listening to to make sure that they got the help they needed in the right way. I'm going to give you a few more questions now to explore in groups or as a class to help you get a bit more from the video and we'll also hear from our young people down in Cornwall about their thoughts on each of these questions once you've had a chance to discuss as well. Now remember there aren't right or wrong answers here but hopefully this will get you thinking and help you feel a bit more able to explore these slightly tricky topics. So the first question is this idea of masks why do people wear masks when they have issues with their mental health when perhaps they need help why do we mask that what's going on there? Here's what the young people down in Cornwall thought about that. We don't need to hide them but we do because we fear that if we don't then we may get bullied or we may get amocked or shamed. We mask our issues because we're afraid of what people might think if they see our true emotions and we feel we might get picked on or bullied showing these emotions and it can be easier to hide them as you won't have to talk to someone that won't feel awkward but really when you're feeling down you need to go and seek help. We mask our issues mainly because of social anxiety of people judging you when you say what you truly feel and maybe losing friends or losing family just because of mental health issues that you can't control. Fear of being judged I think compared to you think people might think less of you if you're struggling a bit. Next I want you to have a think about what warning signs might help you to know if a friend has got struggles with their mental health even if they're working really hard to wear a mask and here's what the pupils down at Cape Corn will thought about that. I swear not wanting to go out so much with your mates and not socialising so much and we're just being generally down. Warning signs you can look out for are people changing how they look so becoming less so taking less care of themselves so not brushing their hair or doing something different that they don't normally do. Also if they become a lot less social and don't want to come to school or meet with certain people. Yeah they might not look after themselves as well or think about what they can do to benefit themselves and their health they might see people less and dress differently and just in general be anti-social and introverted. It's often really difficult to notice if someone is struggling because if they have a mask up that mask can be impeccable and don't have any cracks but it's not always oh they do this so that means this it's not it doesn't have a set pattern everyone's different and will experience things differently. Finally what do you think that we can do to be a good friend if we're worried that someone else is struggling with their mental health what might be the ways in which we can start the conversation and what might be our next steps and here are some suggestions from the peoples at Cape Cornwall. If you're worried about a friend the best thing to do is talk to them or let them talk to you to decide what they need to do. If you're worried about a friend you of course first should talk to them and see that they're okay if you don't believe they are okay then you should go to an adult who you trust or even just another person who you trust and ask some advice. Talk to them a bit and then say maybe suggest people to talk to you and get them to talk to someone perhaps. Let them know that what they're going through is okay and that their struggles are genuine and you won't judge them no matter what they say. Finally I'd like your teacher to remind you about how you can seek support if you're worried about yourself or a friend. Teachers please can you point out what are the sources of support available in school telling your pupils what they need to do if they need help and what will happen if they reach out and ask for that help. You might also find other sources of support helpful if you don't feel ready yet to open up to a trusted adult at school or at home you could think about using Childline or the Samaritans. I hope you found the lesson helpful and interesting and that it gets you started talking about mental health and remember as the Cape Cornwall pupils say it's okay not to be okay.