Hi everyone. Today I'm talking about hearing loss prevention and how we need to approach this challenge from a number of different angles. When I talk about hearing loss prevention I'm talking specifically about noise-induced hearing loss. And we know that that risk of noise-induced hearing loss can come from two sources essentially, from the workplace and also from leisure environments, at least in the pre-COVID era when we were still allowed to go to nightclubs and attend music concerts. Research at NAL and many other labs around the world over the past few years has shown very clearly how sound levels at recreational events can be just as loud as they are in more traditional industrial workplaces. In this graph the pink lines, the pink bars represent recreational sound levels while the green bars are workplace levels. And you can see for example that a nightclub is just as loud as the sound level that you get from a chainsaw. Similarly the sound level that you experience in a fitness class is just as loud as the sound level in a sheet metal workshop. And while there hasn't been an epidemic of hearing loss from recreational sources, the research clearly demonstrates that the more recreational noise that a person is exposed to, the more likely they are to exhibit signs and symptoms of hearing damage. And that's particularly true for tinnitus. In the lower graph you can see that people who report always having tinnitus are very likely to have higher levels of recreational noise doses. And so there's essentially three ways that we can approach a hearing loss prevention. The first approach is to take an upstream view. So this means working at the government level to change policy, to change regulations and legislation. It means working with international organisations to try and make change at a systemic level so that you can create safer environments for a really large group of people, whether that's like a national population or even an international population. At the midstream activities include approaching schools, doing work in the workplace, disseminating information via the media, basically community driven activities where you can still reach large groups of people but not quite as large a group as you would be reaching in the upstream sort of scenario. And then there's also downstream activity that you can do. So downstream refers to reaching individuals on a one-on-one basis and trying to change the behaviour of individuals. And clearly this is a fairly ineffective way to go about trying to change the dial on hearing loss prevention. It's much more effective to try and work at the upstream level where you can make really major changes that affect the health of really large groups of people. However, even though upstream work is effective, it's also really labour-intensive and it involves a lot of stakeholders and reaching agreement from a lot of people who have very diverse views. So it can be really time consuming and it can take many years to reach an outcome. What I'm going to talk about today is some of the lessons that we've learned from the work that we've done at both the upstream, the midstream and the downstream level. So the first lesson I want to talk about is the fact that we've learnt that international cooperation can make a difference. So NAL has been involved in the World Health Organisation's group called Make Listening Safe since it was formed in 2015. And the World Health Organisation estimated that 1.1 billion young people were exposed to unsafe sound levels through their headphones. And so they formed this Make Listening Safe group to try and see if we could come up with some international agreed standards for how we can better protect people's hearing while they're listening through headphones on their personal listening devices. And after four years of work and many meetings and a lot of effort from a lot of people from a wide range of disciplines, the group came up with some international guidelines. So the Safe Listening Guidelines for devices and systems is a joint publication between the World Health Organisation and the International Telecommunications Union. And it sets out some minimum standards that we think should be included for people who are listening through to sound through their headphones. It includes ways for devices to measure sound levels and monitor them and then provide that information to the user. And so this is a really good example of how work at the upstream level can actually lead to tangible differences. One of the really important aspects of this work was that Apple has been involved in the working group discussions. And so if you look at the latest updates in Apple software, you can see that they've actually incorporated these standards into their devices. They allow for monitoring of headphone levels and they provide messages when people are listening at unsafe levels. So this is a great example of how you can really make a difference when you're working upstream. The next agenda on the item for the Make Listening Safe Group is to try and tackle the concept of developing standards for music venues. And we've been heavily involved in this work. We developed a background paper collating all the evidence from the countries which currently have standards for their music venues. So there's quite a few countries in Europe that already impose standards on their music venues. They require them to meet limits on the sound level. They require their sound engineers to monitor the sound levels of their music. They also need to make sure that they're listening to the environment concerts. They require venues to provide earplugs for patrons and they also require rest areas. So that people take a break from loud listening. And so the aim from now on for the Make Listening Safe Group is to try and see if we can emulate what we've done for the personal listening devices and try and create some international standards to create safe listening is it relates to workplace behaviours and how these can translate into leisure environments. So we conducted a survey of 8,000 people and we asked them about their workplace. Did they experience noise at the workplace and did they use hearing protectors in the workplace? And what we found was that those people who'd been exposed to noise at work who'd learned about noise exposure at work or understood the risks of noise exposure and who had used earmuffs or earplugs at work were much more likely to then translate that information, translate that learning, translate that knowledge to their leisure environments. And they're up to five times more likely to use hearing protectors in leisure environments whether that was at concerts or when using tools around the house. So this is a really great example of how activity in the midstream can have an even wider effect than you might think initially because those behaviours can be translated beyond the workplace into other aspects of a person's life. We've also learned that online tools can be a really effective way of reaching a large number of individuals. So while it might be really expensive and time consuming to reach individuals and try and change behaviour on a one-on-one basis, the internet provides a fantastic platform to reach large numbers of individuals for a relatively low cost. So back in 2014 we developed a tool called the Know Your Noise Risk Calculator and we've had many thousands of users log on since that time and what Know Your Noise is is a personalised risk calculator. It's an interactive tool where people enter information about the noise activities that they do, how often they do them and how long they spend doing each one and then the noise risk calculator calculates that individual's personalised risk profile. It presents that information in relation to their peers so it compares where they're sitting on the risk parameter. So in this example this person is at very high risk, they've got a noise risk level of 2.5 and then we demonstrate that when you compare that to the group, the group sitting more around one. So this person's obviously at high risk and most importantly what the noise risk calculator does is it provides information about the source of that risk. So in this example this person's risk is mostly coming from attending concerts and so the person is encouraged to actually go back and change their initial answers and find out what would happen if they changed their behaviour. So for example perhaps this person goes to concerts on a fortnightly basis and so they can go in and say okay well what if I only attended concerts on a monthly basis how would this change in behaviour change my risk profile. And so there's a very real, tangible, personalised demonstration of how that person's behaviour can alter their risk profile. And we know that providing this information to people is useful and then does change people's motivation. So we've conducted a before and after survey and found that before starting the noise risk calculator about 60% of people told us that they either sometimes or always act to protect their hearing and reduce their noise exposure but after doing the noise risk calculator this number jumped from 60% to 88%. So that's a really significant increase in the level of motivation for people doing this tool. We've also learnt that giving access to tools is a more effective strategy than providing information. So we studied a group of clubbers and we invited them to come and meet us and receive a pair of high fidelity earplugs to wear at our clubs and we had two groups. There was Control Group who simply received the earplugs and then another group that received the earplugs plus they were given some information and some training about noise exposure and risks and so on. And what we found was that there was actually no difference between the groups. Both groups were equally likely to change their behaviour to wear earplugs more often and both sustained their intention to protect their hearing 12 weeks after the initial time that we interviewed them. And so what this study has shown us is that giving people the tools that they need to act and to protect their hearing is a more effective strategy and it's really all that you need if people are motivated already to protect their hearing. Giving them information is likely to make a very small difference if at all. Over the years we've done a lot of qualitative work talking to people who protect their hearing and trying to find out exactly why they protect their hearing, what are the insights that we can learn, what are the themes there, what can we find out about what motivates these people and then the idea is that we can then use that information to design tools and campaigns to convince other people to take protective action as well. And what we've found through these qualitative interviews is that tinnitus can be a really salient trigger for people and also people who have a really strong love of music and those who can take a long-term view of their hearing are really likely to be the ones who have been proactive about taking action to protect their hearing. So we often find that if we talk to someone who's a regular earplug user they will relay a story about how they decided to start using earplugs when their tinnitus got too bad or when they spoke to a friend who had really bad tinnitus and they realised that they didn't want to end up in the same situation. So tinnitus can be a really strong emotional motivator to get people to take real action. And we also found that people who are regular earplug users often identify very strongly as music lovers. They see it as part of their identity and it's something that they want to maintain for the long term. And so these people who can see themselves in 10, 20, 30 years time and they realise that they want to maintain their hearing so that they continue their love of music, these are the people that are more likely to be the regular protectors of hearing. And so these things are really important for us because they're sort of emotional triggers that help us to design tools and activities and interventions to help other people also take action. We've also found throughout the years that the media is a really important partner for promoting hearing health and it's a really good way of reaching a large number of people. So these examples come from World Hearing Day from 2018. The ABC published a number of studies looking at music exposure and the risks that come with that. And what we found was that reading the comments was really useful for us. And in particular we found that there were a bunch of comments where people were indicating that they were taking action as a result of reading these media stories. So there were people who were talking to their friends, tagging their friends, talking about getting earplugs for a concert they were about to go to, reminding their friends to get earplugs, offering to buy earplugs for their friends. And so this was a really encouraging sign that promoting your work through the media can actually have downstream effects and affect behaviour in individuals and really you can see sort of the effect of what you're trying to promote. And even more encouraging was one comment in particular which pointed out that this was the first feed on this person had ever read where other people are saying they wear earplugs at concerts. And this gives us a really great sense of encouragement because it suggests that there might be a time when wearing earplugs and protecting hearing and being aware of noise levels will actually become the norm. And we know that people are much more likely to listen to their friends, listen to their peers and take notice of the example of their friends rather than listening to scientists or academics telling them what to do. And so the fact that promoting your work in the media can have this effect and can suggest that the norms can be changed is a really positive thing for us to be able to see. And so I guess if you take all of our work and look at it as a whole, what's very clear to us is that it aligns really well with the COMB model. So the COMB model is a popular health behaviour change model. It's used in lots of different areas of health, not just hearing. And what it says is that in order to change behaviour, what we need to do is enhance and improve and change a person's capability, opportunity and motivation. And it's these three things which will drive behaviour change. What we need to do is to resist the urge to educate and instruct and inform. And instead, what we need to do is look for opportunities to try and help people be capable of protecting their hearing, knowing the risks, understanding the relationship between noise level and duration, giving that capability and the know-how to insert earplugs. These things are all about enhancing capability and they are the type of things that are going to lead to real behaviour change. Equally, providing opportunities for people to change their behaviour. So if we take the example of earplugs at a music venue, it means having the earplugs visible. It means having them available on the counter, not hidden in the back room. It means making them available at a reasonable price, so that people can purchase them easily. And of course, motivation is essential. We've seen in our qualitative work that motivating people, appealing to their love of music, appealing to their desire to be able to listen to music for a really long period of time. Those are the types of things that are really strong and salient and emotional and are much more likely to create behaviour change than giving people handouts and information and scientific material. So this leads me to the final piece of work I want to talk about. And this is some recent work that we've been asked to do by the Department of Health and they asked us to look at how we can change hearing health behaviours across the entire population. So not just young people in a music setting, but across the whole population. How can we motivate people to change their hearing health behaviours? And so we've done a big analysis, a big deep dive, if you like, looking at the needs and gaps of the Australian population in terms of their capability, their opportunity and their motivation to engage in hearing health behaviours. And yeah, if this is something that you're interested in, please reach out to me after this talk and I'll be happy to tell you more about it. And so finally, to conclude, if we're going to prevent noise induced hearing loss and make a difference, what we need to do is a whole lot of different activities. We need to think about what we can do at the upstream level. We need to keep active in the midstream, engage with the media and also think about what we can do in the downstream and try and reach individuals on their level. To do that, personalised online tools are a really good way for reaching young adults and motivating them to change their behaviour. At the midstream, we know that the workplace is a really good place to talk to people about noise exposure because it has more widespread effects than just the workplace. It goes beyond that into leisure and recreational settings as well. We know that giving people tools to act is much more important than giving them knowledge and we know that we need to keep engaging with the media because it's a really good way to generate peer-to-peer advice, motivate action and perhaps even create some new norms. Finally, my main message, prevention campaigns, interventions and activities need to be based on trying to enhance a person's capability, opportunity and motivation. By changing these three things, we'll be able to make effective changes in terms of behaviour. Finally, I'd like to finish by thanking my colleague, Megan Gilbert, who has been an instrumental partner in all of the work that I've talked about here today. Of course, I'd like to acknowledge our funders for all of this work. That includes the Hearing CRC and also the Department of Health, which funds much of the work that is done at now.


Live, from the Mandalay Bay Convention Center in Las Vegas, it's theCUBE, covering VMworld 2016. Brought to you by VMware and its ecosystem sponsors. Now, here's your host, Stu Miniman. Welcome back to theCUBE here at VMworld 2016. I'm Stu Miniman, joined with my guest host, Keith Townsend. Happy to dig into this session to some of the happenings in cloud. And for that segment, welcoming back to the program, Peter Cutts, who's the Vice President of Global Solutions inside the EMC Converged Platform and Solutions Division, or it's EMC-CPSD now. EMC always changing around the acronyms, moving things around. We talked to Chad this morning, but thanks, Peter, for joining us. Thank you for having me. And of course, if we can't put an acronym on it and square it, then, you know, we don't have something. All right, speaking of acronyms, your group, the main two things you have, it's EHC and NHC. Give us the update on kind of what those are, the announcements you had this week and what you're talking to customers about. Great, so exciting stuff. I mean, Enterprise Hybrid Cloud, EHC, we always had to throw the acronym out, but from a standpoint of updates, what's been really exciting is, look, it's a turnkey IS platform. It's helped customers accelerate the VRealize suite, converged complete turnkey IS with life cycle for apps, all that stuff. It's been great, phenomenal. Customer adoption, as Chad mentions, it's growing like crazy in the announcement. We kind of said 178% growth, you know, really just screaming. The key is the updates are really focusing on our customer's needs. So we've been interviewing and doing a lot of agile fashion development with the developers and line of business owners in our customers and just having them help us refine that feature. So it's been really great and, you know, so we're really focused on a couple things. More sites, simpler and literally allowing, you know, compliance across the board, encryption on demand, cross cloud encryption, those type of things all kind of been the fundamentals of it. So adding more to it while continuing to make sure it's rock solid and delivering what our customers need. Okay, so the EHC being infrastructure as a service, it might be tough, I would think, to find, you know, what is that killer use case? What's the thing that's bringing customers to EMC, deploying that solution? What's the case, some of the key drivers there? It's really a couple things. So turnkey, right, so I need this, you know, to be life-cycled, managed, supported from a single organization, a single kind of entity. Because again, you know, the piece parts and kind of assembling it is a way to do it, but a lot of our customers are saying, I want to focus on, you know, my value, which is building banking applications or manufacturing or other pieces. So killer use cases, true IT transformation and automation. So being able to deliver a complex application with micro segmentation, firewall rules, all without having to have human beings touch all of those pieces, it's all automation, it's all self-service. So self-service is the key. How are the business units developers in line of business owners? Yeah, so Peter, it's interesting, you know, cloud was one of the major focuses that Pat talked about in the keynote on Monday. He even looked out and said, you know, public cloud, you know, five years from now is kind of that transition point. You know, is that scary for some infrastructure players or, you know, because, you know, I said, if you think of EMC as a storage company, it's like, if I say, gosh, that could be a third or half of my available market would be gone if I'm not a player. How are you making sure the DMC stays relevant and important in that space? So I think a couple of different ways. You know, when you look at it from a standpoint of public and private cloud and the comments that Pat made is very salient, which is like, hey, it's not going to happen overnight, but there's a lot of things that are well placed there. And I think when you see some of the stuff that we do with Virtustream and other things that are coming up, you'll see that we'll also have a play there. But again, public cloud is absolutely part of the enterprise hybrid cloud. That's why we call it hybrid. Chad says, you know, we get about a B plus right now. I think by the end of the year we'll be approaching our A minus. And I think next year we'll really hammer it into, you know, A plus territory because the use cases, the monitoring and the capabilities that we provide are differentiated, especially across the, especially this multi-site addition, compliance, things that are important. There's still important way of managing that and having IT policy around it. So making that easy is really part of our job. So whether it's public, private, we got to help. So talking about EAC, is this an on claim within the data center or is this a integrated solution in an existing VMware vSphere environment? If I'm a customer, do I have to manage this separately for my existing environment or are there hooks into my existing data center? Well, so there's a couple of different ways. A lot of times the way customers are approaching it is they're starting a net new project because it's totally transformational. Like nobody ever touches a storage array again, except for during the first initial setup to create pools. Nobody touches the IP networks anymore. They don't log on to switches to a provision. So it's a little bit different. And so a lot of customers start in like a new project, but what's powerful are some of the tools that we brought to bear that says we can take a virtualized, complex, multi-tiered application and import it into the new, you know, kind of EHCV realized power infrastructure and apply all of the cloud semantics we've built so that you can just do that in a very easy fashion. So I would say that, you know, a lot of customers are managing it separately because it's a different way of doing business and doing IT. Right, if you're going to provide complete self-service, you've really got to make sure that you have everything set up to make sure you allow that. So if I bring in the EHC, or, you know, tell me from customer experience, are customers bringing in EHC and then finding that they're migrating processes and workloads from their traditional infrastructure into EHC? Absolutely, absolutely. So the key piece of what we built of being able to ingest workloads and apply all these semantics, because actually moving a virtualized workload out of the box into cloud is not like something that just happens. And to apply all these different new policies and provisioning policies and encryption on demand and all these different features self-service, you've got to have an ingest capability that allows you to apply all that in a simple way. And so that's what we've helped customers do is really onboard workloads and pull them in fast and easy.  My understanding is you've got NSX in there in the EHC piece, not something I'd heard too much about before this week. Maybe you can unpack that a little for us. Well, so I think there's a couple of different reasons people are using NSX. One of them is the obvious kind of micro segmentation you saw where like why is internet traffic hitting the database, right, directly? That was a cool demo from CrossCon, but even in the data center, that's something where, you know, intrusion can now happen inside the data center. So micro segmentation, being able to isolate, you know, what talks to what is really important, that's built in, right? So part of the Enterprise Hybrid Cloud, you know, kind of build structure says we support that. Then you pull in some of our partners like Palo Alto and Infoblox, we've actually built kind of modules that allow you to ingest those and put those into your environment seamlessly and easily. And so things like firewall rules and being able to, you know, provision on demand, all again, self-service by policy, that's all included in the automation. Because if you don't really add that, if it still takes two weeks to get a firewall rule, you're not really moving things faster, you're not creating that agility that you need to with the self-service approach. So EHC has been a strong onboard ramp to services like Amazon, Hybrid Cloud. Exciting announcements from Pat yesterday or CrossCloud. How does CrossCloud fit into the EHC roadmap? Well, I think, you know, from the standpoint again of helping our customers on the journey of making sure that if they do have multiple clouds, you know, they have the freedom to move to protect. So building in that automation, I mean, part of our work is to actually make sure that the provisioning processes for EHC are seamless to the public cloud, you know, other public clouds that are out there. And so in this case with CrossCloud, I would expect us to be able to leverage that and we're partnering with obviously VMware to make sure that we have the capability to either take a workload off, back on premise, if that's a customer wants to do. I've talked to a lot who want to do that. They start out in the public cloud and they're like, yeah, you know what, I'd really like to bring it in. These are things that will help make that easier, I think, and also, you know, make things more secure and manageable. So speaking of secure and manageable, so I have an EHC, I have CrossCloud. Let's tell you another part of my data center. Is there an integration path between the NSX that exists in EHC and the NSX that exists in the other part of my data center? Yes, absolutely. I think that the beauty of NSX and the software defined networking is it really does allow you to bridge across the data center and provide that. So absolutely, no, and again, that goes out to public clouds, anywhere you use it, it allows for that. So absolutely. All right, Peter, let's talk a little bit about NHC then. Can you kind of compare and contrast kind of the customer set, you know, the business drivers, you know, what's differentiating that and, you know, are there paths between those two? There are, and one of the things you see, especially when you look at kind of the solutions, you know, EHC is really all about, you know, the complete automation and self-service nature of stack-based application development, as well as traditional applications like Oracle SQL, you know, branded apps that need complete automation, life-cycling automated, you don't want to have people patching things anymore, you know, all of that stuff gets kind of worked into it. From a standpoint of the value it provides, it's really returning back, you know, what I would call, you know, savings. You know, some of our customers that you guys have obviously interviewed and talked to, you know, 25% of savings and cost, right? That's a huge deal, right, out of EHC. But then there's this other piece of the business, which is, you know, I need to have agility that is completely focused on, you know, what we call the green field, however you want to look at it, it's really all about cloud native. And when you get into cloud native, one of the things that's powerful about native hybrid cloud, we've basically taken a similar but different approach to the enterprise hybrid cloud and we've taken basically the package of turnkey paths and really built it so that customers can realize an actual platform that allows you to deliver that paths experience and that developer experience literally turnkey and lifecycle it. Because again, just because you're in, you know, mode two or platform three or in cloud native, you're in a situation where you still have infrastructure that's underneath as Gil just mentioned, right? You got to lifecycle that. Pivotal cloud foundry releases once a quarter. You got to make sure that you continue to update that and then you've got to have an operations panel that allows people to actually talk from the applications team to the operations team. So, and we've built all that and given that kind of power to the customer. So, when customers look at it, it's really a two pronged approach where I can actually automate, take cost out and invest in basically cloud native apps. And by the way, the cloud native apps still need to talk to the systems of record. So you got to have both. And it's a really powerful, you know, kind of combination for customers. All right, so Peter, want to give you the final word, you know, talking to lots of customers at the show. Any kind of, you know, really fun or interesting or, you know, surprising stories that you've heard that you can share with the audience? I think the stories that were interesting to me, other than of course, when Chad and I did the analyst thing and I got the mic twice, I think it was out of that. No, it's funny, that's a story. He wrestled it from them. I wrestled it from them, but it was, you know. No, from a standpoint of customers, I've just been walking around, I was able to talk to some of our customers here and the excitement that they're hearing about kind of that transformation and you can hear it across the board with now the new Dell announcement out today as well as, you know, people are shifting to cloud, people are getting this, people are starting to see this cloud-native development, people are getting NHC and EHC more and they're seeing that they can really start to provide services with better agility and they can do it all with a self-service nature but still keep the compliance and control of what they need to do and again, that's what we're trying to do and deliver to them every day. All right. Peter Cutts really appreciate the updates on everything happening in the Converge platform and Solution Division inside EMC. We'll be back with lots more coverage here from BM World 2016. You're watching theCUBE.


Hello friends. I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. In this video, I'm going to demonstrate how you can call Autolunch Flow through process using process builder. So in this video, I'm going to tell you how you can create Autolunch Flow. Then we will call that Autolunch Flow using process with help of process builder. Before starting, if you want to watch Salesforce training videos, you can search my name Sanjay Gupta on YouTube and you can follow my YouTube channel. So now let me first create Autolunch Flow. Before creating Autolunch Flow, let's take a look on email alert and email template. So I'm going to use this email alert, email alert to contact. So we are going to send an email whenever we create a contact record. So whenever a contact record is created, we need to send an email alert. So this is the email alert recipient will be the email field that is available on the contact record. This is the email template for contact email alerts. So here it is, it is, it's text, so it will throw this message like high contact name, then congratulations. You are registered with our company. Thanks for registration. So this is the email template, then this is email alert. Now we have to use this email alert in flow so that this email can be triggered and then that flow will be called through process builder and that process will be executing when record on contact will be created. Right. So now I'm going to create a flow first. So here I need to select Autolunch Flow. So remember that there are two types of flow, screen flow and auto launch flow. So you can select only auto launch flow if you want to execute it with help of process builder. So I selected create then in elements you can click action and drag and drop it from here you need to select type and from here you can select email alert. Now we need to select or search this email alert to contacts in this flow. So here it is. Now we need to provide its label. So email alert. Then here we need to put the record ID. So this record ID will be off that record that we are going to create. So this flow requires this record ID so that email field can be identified. So we need to create a variable named as record ID. It's type is text and it is available for input. So its input will be provided by the process that we are going to create in process builder. So this way you can see I created email alert. So this email alert will be working for contact because it is created for contact field. And now we need to link this flow with process. So I'm going to save this email alert flow, its name. I'm saving this, activating this. Moving to process builder. So here this process is on contact object. It will execute when a record is created. Now we need to enter criteria. So I wanted to run always. So no condition. So whenever a count record will be created, it will execute. Now I need to add action. So from here I need to search flow. So here you can see it is showing the name as send email flow. No, we need to refresh this page. So whenever you are creating new flow and you are going to use this in any feature, so you need to refresh that so that it will be available there. Now I'm going to add action. So our flow name is email alert flow, right? So now here it is available email alert flow and action name is call flow. Now here you can see it is showing set flow variables. So from here you can pass values to flow. Click on add variables. So in flow we have a variable record ID. Now we need to set it with the contact record ID so that you can search here. Contact ID choose so contact record that is going to be created. It's ID will be passed to record ID variable that is available in flow and I'm clicking on save. So this way this process is also ready. So I'm activating it. So now understand the process again. So first I'm going to create a contact record. Then this process will be executed. This process is calling a flow. Then flow is calling an email alert and email alert is associated with the email template. So this way four entities are working here. Process builder, auto launch flow, email alert and email templates, right? So now flow is activated and process is also active. Now I'm going to create new contact record. So its name is flow. First name is auto launch and last name is flow and then I need to put email. So this is important because I use this email field and email alert. So if it is filled then only email will be sent. So now I'm clicking on save. So here you can see auto launch flow record is created. Right now I'm moving to my mailbox. So here you can see an email is available. So hi. This is auto launch is first name, flow is last name and rest of the message is available here. So this I showed you it is available in my email template. This email template is used by this email alert. This email alert we are using in this email alert that is in flow, right? Then this record ID is receiving value from here from process. So it is receiving contact ID. So record ID is having contact ID and this process is executing whenever we are creating contact record. So this way you can call auto launch flow through process using process builder. So I hope you understood whatever I demonstrated. If you want to watch more Salesforce training videos, you can search my name Sanjay Gupta on YouTube and you can follow my YouTube channel. So on my channel biggest playlists are available related to Salesforce so you can watch them and learn Salesforce. Thank you for watching this video.


This study investigates the potential benefits of incorporating remote sensing near-surface soil moisture observations into an operational hydrologic model. The study found that the model's dry bias and precipitation was reduced by nearly half when the remote sensing data were assimilated. However, the model's surface moisture state was quickly lost due to increased surface fluxes caused by the wetter soil moisture states. Therefore, it may be more effective to address the precipitation bias directly rather than correcting it through data assimilation. This article was authored by C. Draper, J. F. Moffoof, J. C. Calvitt, and others.


So the next stock is Python Traceback for humans and the speaker for today is Anand Reddy Pandy Kuntah So about the speaker The speaker is a well-known Python developer and today's talk is focused for on Python Traceback for humans I request Anand to kindly Initiate that session Okay, it might take for him two minutes. So anyone wants to you know Tell a joke or something you are very much welcomed on the dice Any joker in here joker. I mean joker. Yeah, I'm coming Okay Hello Is it audible at the end? Yeah, font size is visible Yeah, good so This session is mostly about trace back and debugging code and stuff like that So, how many of you seen Python trace back or errors? Oh, very good. So everybody has seen so whenever your code has some errors So python will throw some exception and it shows some trace back So what we can do is actually we can take out whatever trace back python is giving and we can bring our own trace back And we can plug it in there. So how many of you know that we can actually do that Oh, okay, that is quite good number. So, how many of you actually tried that? Oh Oh, that's cool. So in this session, we will try to do that Okay So we'll mostly see what is a trace back and then we try to take away the default trace back and replace it with the Color trace back and then we can see what are some useful things we can do with a custom trace back And then we can see how we can customize the trace back To debug our code and lastly we will see how we can write better code to get better trace back Sounds good Yeah, let's get started So I'm just going to write a simple function called you Which attacks two arguments x and y and then returns x by y so And i'm going to write one more function called foo which attacks two arguments and just calls d of x comma y Now i'm just going to call foo with arguments one comma one So is it visible at the end? Okay, just a second Yeah, yeah Yeah, so can somebody tell me if I execute what will be the output? One are you sure? Nothing. Yeah, exactly. So somebody is not sleeping. I think So actually I need to put a print statement. Otherwise it will not Show that value So now can somebody tell me what will be the output? Yeah, let's execute and see that So Ah I'll just increase the font size So it's actually one So now what i'm going to do? I'll just call the same function But I will just call You pass arguments as one and zero Now can somebody tell me what will be the output? Huh Zero division error. Are you sure? Okay Ah, okay, it is actually throwing zero division error So as you can see here, this is this entire thing is trace back And this is the error type and this is the error message So this trace back has three frames. This is the first frame. This is second and this is the third So first we are calling print foo of one by zero Which is calling this written div of x comma y And in that it is executing written x by y where the actual error is occurring So Okay, so this line of code. This is what triggered the actual error But the actual error has occurred at this line Which is written x by y Okay, but this is the default trace back which is printed by python So now We will try to remove that error So for that what so can somebody tell me how I can remove that error Okay Try catch okay two more any more solutions. I just need to get rid of that error. That's it That we are already doing that right before that I need to have that foo of one comma zero, but still I need to get rid of that error Keep why no, I need one by zero. That's what I'm saying So what I'm going to do is I'm going to take away python exception. So I'm going to define a custom function called custom trace back Which it takes error exception type exception value and trace back And does nothing And then I'm going to Hook that function To system dot accept hook Let me import that Cis yep Now if I go back and execute see The error has just disappeared But if you see my code That One by zero is still there So what is happening here? Anybody any wild guess? Yeah, exactly. So whenever some error happens python calls system dot accept hook Which will have some custom function which prints that trace back So what I'm doing here.  So You will always get expected results with this kind of code Okay But the thing is We can't Debug the code like this, right? So what I'm going to do now is I'm going to print the actual trace back what python is printing So I'm using a function called format exception From trace back module and I will just pass the same arguments And then I'm just going to print that trace back Oh, you need to import trace back module If you see We are getting the division error again But the thing is that trace back whatever it is printing it is not being printed by python But we are writing a custom function to print that So I can print whatever I want here and I can even customize it So for example, I can just go here and I can say This is custom trace back And if I go and execute you can see Here there is a that line is printed here So right now python is not controlling the trace back, but we are controlling and we are modifying As per our needs So we have done this we are trying to mimic the python trace back Now we'll do something cool So there is a Package called pigments. So which does the syntax highlighting for a given piece of code So I'm just going to call that function So it has a function called highlight which takes Code and some formators and just highlights the given code So previously I was directly printing the trace back But now I am passing the trace back to a function called highlight Which takes the trace back and then it needs a lecture to format the code Since I'm printing a trace back. I'm giving python trace back lecture And since I'm running the program in terminal. I am giving a terminal formator so If I go ahead and run this Can you spot the difference between previous thing and this Yeah, what is the difference? Color trace back. So we are actually trying to customize the trace back So To make it better and to debug our code quickly So this is one thing we can do So can somebody tell Are there any users of customizing a trace back? Why do we need to actually customize this trace back, right? We can just use the python trace back Why do we need all this customization? Okay, like color trace back. Yeah, okay. That is one use case any others With the normal trace back also you can get right Yeah, we can make it more human readable And Yeah, exactly And any others? Yeah, yeah Yeah, yeah, yeah, so we can do lots of cool stuff by customizing the trace back So this is a color trace back So hyperlinks in ids. So for example If I have some error here And if I try to execute this code If you see here this trace back it has a hyperlink So the guy who has designed this thing he has actually taking the python trace back And wherever there is a frame and a path he is actually hyperlinking that particular path to exact file and location If I actually click this So see it actually takes me to the position where the error has occurred So this is one use case of this gwabs so Anybody have you done g y programming with python? so Yeah So whenever you are running some g y apps you just run one main loop which runs forever And that will run entire app. So when you are running an app and some exception occurs You don't want your app to crash So what they will do they will run one main loop and whenever some exception occurs Instead of throwing the trace back they will silently lock that error somewhere else and they will continue execution of main loop So by that way even though some error occurs the whatever g y that is there it won't crash It will be it will keep running on So that is one more use case and Ah work zig so how many of you do web development? How many of you used work zig? So so what will be the use of this? So what we can do is here we can go to each and every frame and we can debug actually So if you see here, I have some trace back here But the thing is it provides interactive debugging for example here one frame is there I can go to this frame and then I can just say inspect locals So it prints all the locals which are present in that frame And I can go to some other frame where I think error might be happening and I can debug there also But you can't do the this in the terminal here since the state of each and every frame is saved We can inspect each and every frame wherever we want. So for interactive debugging This will be very useful So debugging tool so I have Simple notebook here So we need to We'll do we'll take the trace back and we'll inspect and see what are all the items that are present in the trace back So i'm just importing the function foo which we have defined earlier Okay, the function is imported Now i'm Can you see the font? Is it visible at the end? Yeah now Not visible Now i'm trying to run the same function with the same arguments, but i'm trying to run that in try accept block So i'm trying to execute foo of 1 comma 0 and if some error exception occurs i'm storing the exception values in at In three variables. So there is one function called assist dot accept info So whenever an exception occurs that function has all the exception information So whatever it is written i'm just storing in three variables And if i try to format and see what is present there So the same thing it is present So the exact error it is showing that it has called foo and then It has called a written div of x by y and it is returning x by y which is throwing zero division error So now we have three variables, which is nothing but exception type and then exception value and trace back So this exception type is nothing but zero division error and the exception value is division by zero error And we have this interesting object, which is nothing but a trace back object So now we will try to see what is present inside that So there is one function called a get inner frames, which is present in inspect module When you pass a trace back object to that function it returns all the inner frames that are present in the trace back So it is returning all the three frames and if i see what is present in first in the second frame It has actually a frame object And then it is showing the complete path and then it is showing the line number which is present And it is showing the function where it the error has occurred and it is showing the line where it has occurred So i'm just going to unpack that frame record And now i have all the frame frame name line number everything And now i'm going to pass this frame to A function called a get arc values What this function does is it takes a frame object and gives all the values that are present in that frame so You see it is actually printing what are all the arguments that are passed to the function We have passed two arguments, right? So it is giving x and y And where are we have not passed any optional arguments? So it is returning none and we have not passed any keyword arguments So it is also none and it is even showing local variables. This is this will be very useful actually So the local variables it is showing x and y x is one and y is zero So we can actually pass the frame and local variables to a function called scan wires Which actually takes a piece of code and tokenizes the Code and finds the variable in it and actually returns the value of that variables So So In the line where the error has occurred it is a return div of x by y The frame we have taken so if we look at the object it has returned It has returned a div which is nothing but a global variable and it is a function And it has returned the x which is the local value and its value is one and y which is the local value which is zero So What we have done so far now is we have taken the trace back object whenever an exception occurred And we are going to inner frames and we are inspecting what are all the variables that are present in that frame In addition to that Whenever some error occurs we are trying to find the variables in that line and we are trying to get the values Back here Now i'm going to show one function So I have A small Code here So i'm just importing a module called num and i'm getting three numbers from that Module and i'm trying to sum the three numbers i'm trying to print the total So if i execute that it should print a total right? So i'm just going To run that function So it is throwing some error So it is throwing type error unsupported operand types for int and stir So can somebody tell me how to debug this? So replace No, we need to get the total right how to Hmm Check the type of that three numbers and then do typecasting. Okay, so Remember the procedure we are doing we are trying to Okay, we are trying to check the type of all this and So it is showing the first is int second is string and the third is int So I need to go back to my script and then I need to typecast these two Int and I need to remove this print statement Now if I go back and execute it is running successfully, right? So this is one way of debugging that code No, actually that is a module it is returning It is some third party module So it is like whenever When you are writing some real life code, you won't have like everything up and running You will be calling some other functions and somewhere you are retaining some data and somewhere you might be doing something else So there is a good chance of you getting that type error So where you might have to do typecasting, but you can't change the upstream where that error is coming So in such situations so What you can do is We can actually print So whatever we have seen in the notebook. I have already packaged that into a simple package called ptb And if I just import that module and I enable that And if I execute that module So now also we are getting the same error But if we look at that trace back So it is showing that the error has occurred in this particular line Where total equal to num1 plus num2 plus num3 But the interesting thing is just below that line it is automatically printing all the values of the numbers So it is printing that num1 is 1, num2 is string 2, num3 is 3 So we don't need to actually go back to our script and then put one print statement and then again Come back and execute and all this So just by looking at that trace back we know the value of the objects So we can just go back and do typecasting So which will be a bit easier It will be useful only when you are dealing with some kind of errors, but yeah, it will be useful So filtering frames So How many of you use Django here? Okay, so have you seen Django trace back? So one of the interesting thing with Django trace back is so here I have some If you look at the frames here, this frame is actually dimmed This is dimmed, this is dimmed, this is dimmed, but this frame and this frame are actually highlighted So the reason why Django does that is This whatever frames that are present here, they are part of core Django So most likely the error will not be present there So Django tries to dim that frames to make it easy for the user to find the bugs So actually the error is somewhere here So just by looking at that trace back, we can Get an idea that the error will be present only in that these frames So When we were actually getting the frame information If we see the frame record, we actually have the frame path here So what we can do is whenever we are printing a trace back We can actually take the frame path and we can check with the standard library path And if it is present in that we can dim the frame if it is not present We can actually highlight or do something else with that frame So it helps to distinguish between multiple frames More context So how many of you use ipython? Yeah, so if you have used ipython When you run some program which has some error Let me run some function So see Let me run the same thing in So when I run function using Normal python Whenever an error occurs it actually shows the line where the error has occurred or For each and every frame the function or the line which has caused the error It shows only that line But if you look in ipython, it actually shows Two lines before where the error has occurred and two lines after also So it does the same thing for each and every frame When you are doing some kind of numerical or scientific computation you might be getting errors Because of previous lines also you might be doing some subtraction It might be giving some zero or something else So when you have some more context where the error is occurring It might be easy for you to identify the error So this is one of the use case So we have been doing all these things like magical print whenever some error occurs Print some variables and then we are doing filtering frames and then We are looking at the context and we are doing lots of other things So do you think is it really worth spending time on doing all of this stuff? Yes So to decide whether it is worth or not, we'll let's have a simple exercise I'm just going to show you a picture Which has number five and number two You just need to count number of number twos in that picture Get it? Just count number of twos I'm just going to give you 10 seconds Okay, let's start Time up time up Six five four Four five six. I'm hearing only these three answers Ah, okay. Okay. I got it. I got it. But you took around more than five seconds So all most of you took more than five seconds to figure that out So I'm going to show you one more slide. Just tell me how many of them are there I have actually highlighted all the twos for you And again you are counting So actually in the previous slide it is quite difficult, right? You can't make out where the twos are But when you differentiate you can actually easily see That is the thing we are doing with the filtering frames So actually whenever we are trying to make the things like that it will be quite useful and We do spend a Good amount of time on debugging our code So it will be and the thing is it is only like one time investment We just customize the trace back like whatever you need and it will be there forever. So It will be quite useful So Now let's see So one or two tips on writing Some code which will give us some better trace back So what you can do is actually whenever you are writing code you can use some custom conditionals and custom exceptions To catch the errors. For example, when you are opening a file You can just actually the the file path might not be correct or there might be some typos like that So there is good chance of that file might not be found there So what you can do is when you are trying to do some task like that you can actually catch the exceptions which might occur in that case and Even when you are trying to Build some apps which will be used by users and some exception occurs You don't want to show the trace back to Users, right? So you need to give them some meaningful message so that they can understand better. So Here I have a small script which reads an integer So if I execute that So it is just asking For enter an integer instead of entering an integer if I just type some string or something like that It just throws some weird trace back If you are actually shipping this code to some user who is not a developer This might actually confuse them a lot, right? So what you can do is you can just catch that error and you can display them a good message So now if I enter some String or something like that it just says please enter integer only So and if I enter integer it shows congratulations. You have successfully entered an integer so The thing is you you need you don't need to show that trace back and everything to end users Chaining exceptions. So how many of you use python 3? python 3 Okay, only a few hands. Okay Have a small code I'm just using python 2 here So What I'm trying to do here is I just defined a function called compute Which it tries to divide a number with another number And when an exception occurs I am trying to log that exception in a file called log file.txt I'm just taking the exception and I'm trying to write the exception to a file And what I'm trying to do I'm just calling the compute of 1 by 0 So what will happen when I call compute of 1 by 0 it goes here and it tries to execute this And whenever this happens so it will throw 0 division error. So it tries to log that error So when it tries to log the error as mentioned here that log file is actually not present So it will throw one more exception If I run this It just gives me some error called IO error file not found What I'm actually trying to do here is trying to divide 1 by 0 I'm getting an error called IO error file not found This is happening because when I am trying to divide 1 by 0 I'm getting 0 division error And I'm trying to handle the 0 division error by logging it into a file And when I'm logging that into a file I'm getting an exception here So this exception is getting lost and this exception is getting printed So it will be difficult for developers to figure it what is actually happening But if I execute the same code in python 3 See it actually shows 0 division error here 0 division error 0 division by error And then it displays message during handling of above exception another exception occurred And then it is showing that file not found error So python 3 actually does exception chaining implicitly So whenever one error occurs and you are trying to handle error and some other error occurs python 3 actually tries to chain the exceptions and print it If you want you can actually try to manually also you can rise the exceptions Rise some error from other error like that So you can do lots of stuff with python 3 So try to read that pep 3 1 3 4 So it teaches about python exception handling and how it does implicit exception chaining So if you are very lazy to do that error, please start using python 3 So the thing is you don't need to stick to whatever trace back python is giving You can actually customize the trace back according to your needs And whenever you are getting a trace back you can remove all unnecessary information And you can take out whatever information that is required for you So that's it if we have time for questions I will take otherwise I will take out So he is asking like when i python is showing a lot of context right Where error has occurred two lines before and two lines after So let me just So you can see here here we have only one line where the error is occurring in the frame record If I go back here here when we are calling get in our frames in addition to trace back We can also pass context if I give context equal to 5 and then execute And then look at the frame record now you can see you are getting actually five lines Previously you are actually getting one line so whenever you are calling that get inner frames You can actually pass the context which you use the amount of context whatever you want Local variables so when you are when you have a frame record You are so you are calling that inspect dot get arg values So it is returning all local variables that are present in that particular frame Does that answer your question Whatever I have told I have written that into a package called ptb and I have published on pipi I think there are many other packages Any more questions two three four six guys are sleeping right now So wake them up and ask them if they have any questions Okay, thank you


full grain, corrected grain, suede, rough out. Are you confused about the different types of leathers on boots? Or more to the point, are you confused about the terms used in describing the leathers on boots? Well keep watching friend, here is the Leather Deep Dive. Hi you guys, welcome to my channel Bootlossophy and my name is Tech. I acknowledge the traditional custodians of the lands that I'm recording on the widget people. In this video I'm going to talk about leather, the different types of leather and especially try to untangle the different terms people use to describe different leathers. But I'm warning you my voice is going to be a little nasally in this video and I might even sniff. I'm just coming out of COVID. Still we soldier on. Before we start let's get this straight though. I am not a leather expert. I trained in numbers as an accountant and I run a management consulting company. So hardly the man to have grown up in tannery's knee deep in the tanning vat. But I do have an interest in the different leathers used by boot brands and intrigued by the different things that they call these leathers. And so when I started my boot journey I was super confused when people talked about a leather being full grain and it obviously did not look like another leather on another video that someone else called full grain. And then the comments on the videos and on Reddit which I think shows that people really either cannot agree on terms or just did not realize what those terms really meant. So I investigated and this video puts together the consensus understanding not the universal understanding the consensus understanding of these leather terms. Second caveat this video is not about different tannages. That's a video that could take 30 or 40 hours going through the different tannages made by different leather tannery's around the world. No this video is about the different types of leather used for boots.  To explain the different types of leather we need to start with the whole hide. So here's this brilliantly drawn characterization of the cross-section of a typical hide. At the top of course is hair growing out of the layer that we call the grain layer. The grain layer has skin cells that make up really tightly packed fibers. Essentially a protective first layer for the animal. Just under that is the junction between the grain and the next layer down the corium. The junction between the grain and the corium has skin cells that make up fibers that are starting to open up, starting to allow the animal to flex and bend. Beneath that is the corium layer with much looser fibers as it starts to become less skin and more flesh. And then of course below that is the actual flesh of the animal itself. Now when a hide is first tanned to preserve it and stop it rotting it has all of these layers present. Even a little bit of flesh that's still attached when the animal is skinned. Ya, yuck, gross but that's life folks. So the first thing that happens after the hide is preserved is that it's cleaned up and the hairs as well as any flesh are removed. You like that? I told you this was like play school. Only a bloodier gross adult version. Stick with me. A lot of people make the mistake that what's left is referred to as full grain. In fact someone actually once commented on one of my videos about a boot that I'd reviewed which was a full grain leather boot that he liked it but he wouldn't buy it because it wasn't thick enough to be full grain. Well if you made a boot from the leather that's left here you'd be making a moon boot. This leather is too thick. They do use the full piece but usually to make saddles and other things that don't flex a lot. The fact that the top layer is called the grain layer should give you a clue because full grain leather simply means leather where the top is not treated or corrected by buffing or sanding in any way. This is Parkhurst's Allen Boot and it uses Horween's full grain Dublin leather. Check out the review showing in the top corner. You can tell that it's full grain leather because if you look closely you can see all the crisscross texture of the fibers, the hair holes, the pores, often scratches from barbed wire, tick bite marks and so on. So full grain refers to how this top layer is treated. But as I said this is too thick to make practical boots so in fact most leathers are split. The cleaned up hide is run through a roller with a horizontal blade that splits the hide into two pieces either just above or around the junction of the Corrieman grain or it can be just below as well. The top of the split is sent to make certain types of leathers primarily the smooth surface leathers and the bottom of the split is used to make primarily suede. Now before I go on let me briefly point out how genuine leather is not. Well it is but it's not. What the industry calls genuine leather is usually the bottom split which they then sand the rough nappy fibers at the top smooth and then print. Yes print a grain pattern on it. Genuine leather smells funny that's how you can tell. It's the ink and dye smells overpowering and your remaining leather smells. Stay away from it.  As I said full grain means you haven't stuffed around with the surface of the grain but for some designs this isn't really dressy enough and you do need to either really polish it with a lot of waxes to make it look dressy like some calfskin leathers for example in dress shoes or dressier boots. Think of something like RM Williams calfskin or you correct it. Correcting the grain means you lightly buff it to remove the tick bites and other marks but you leave most of the pores and grain. This is the Ellen Edmonds Higgins mill in brown chrome excel. It surprised you to hear that technically while described as full grain chrome excel is actually corrected. It is slightly smoothed out so as to give it this kind of smooth luster. So the debate is can you mean full grain with this kind of light correction? Many would say yes because again full grain is the treatment of the surface and something as light as this doesn't really stuff it up. There are other corrected leathers where it's treated a lot heavier than this and common understanding is that those are no longer full grain. Who recognizes this icon? Of course Timberlands classic six inch waterproof yellow boot. Many of you will know that this is new buck but many might think that new buck is a kind of suede but it's not. New buck is actually corrected grain leather. So new buck starts with a piece of full grain leather. The grain is then heavily corrected that means the whole top surface is sanded and then buffed until these tight fibres in the grain layer start to feel a velvety smooth feel. It's almost too short to be called a nap but it's the feeling of the fibres starting to stand up. Why do this? Because new buck is incredibly resilient. While it still has the tight fibre structure to protect it against cuts the abrasion that removes the smooth grain has made the surface resilient to scratches which would show on a smooth grain surface. That's why it's so popular as a work boot leather and the tanning of it can vary. Apart from a straight dry new buck you can also apply some oil in the tanning and create a distressed look like on this Chippewa original service boot. Now this is a leather called crazy horse. It's not horse it's just a name and it's made as an oiled new buck. You can see other variations that the P&W brands often called distressed. Again is new buck full grain? I mean some brands call their new buck distressed leather full grain. It still has most of the grain layer lots of tight fibres but in my mind it's probably only a subset of full grain. Okay now so let's talk about suede. Yes it is different from new buck. Suede as a term can be controversial because it can be some things to some people. Let me explain. Once the hide is split you can make suede from both splits. The more traditional split is the bottom split. The top surface of the split is sanded so finely as to make semi-loose fibres into a soft nappy surface. The best proponent of suede is of course Charles F. Stead. This is Weiberg's Hulk at boot. It's instead Janus Carth suede probably the softest most velvety suede yet. See the review that's linked in the corner right now. When treated well its surface of the suede is soft and it just plays with the light. It's also incredibly supple on your feet. But don't get me wrong not all suede is as soft as this. Some other tanneries can make good suede but they're often rougher with a little bit more net than the velvet touch. But one of the controversial things about the suede is that it can be made from both splits. Apart from the bottom split suede can also be made from the top split. In this case the top layer is turned upside down and the bottom of the top split is sanded to make the suede. This often results in not as fine a nap. Now this is predominantly used in British shoe making that's why if you look at the British brands on their websites you'll often see a reference to rough out suede which brings us to rough out. From the name you should be able to guess that rough out is literally the rough side out. So rough out boots have this smooth grain side on the inside and the looser fibre structure on the outside. This is the Cordobus capto boot review coming soon. It's a Mexican tan rough out and you can see the nappiness in it. So clearly not a suede because it's not been finely sanded and not intended for finer looks. They are great workbook leathers though because like newbuck they are resilient to cuts, knots and scratches. And for the other guy who commented that my Indonesian rough out boots were not full grain look again. The full grain is on the inside. Now I said earlier that I wasn't going into different tannages and only sticking with different types of leather but I will talk about wax suede and wax rough outs. Now technically they are how you tan and treat those leathers but I will speak about them to clear some confusion. Wax flash is rough out with a heavy coat of wax stuck on the napp smoothing it down. Here's Truman's Java wax flesh boot. The wax flesh from Horween is a mid brown rough out leather that has a thick coating of wax. When new it looks almost smooth grain. Check out the pull loop here. But once it's worn and kicked around the wax layer starts to flake off and reveals the mid brown napp of the rough out underneath and it gets quite beautiful. This one is Caswell's Lisbon boot in suede tobacco waxy commander. You can watch the review of this one on the link at the corner. Again they make this by coating suede with a layer of wax but the difference is that it's not a thick layer so even when new it never looks glossy smooth and it wears off quickly almost with your first steps as you start to crease the boot. In fact I sold another pair of these on eBay just the wrong size after only wearing it for a video shoot and one guy who knew it was me selling wrote to me and said now you're telling fibs no way it looks like that worn after a video shoot. Well he was wrong or probably he thought that wax suede was like wax flesh.  It takes a while to get it to this stage. Wax suede on the other hand was designed as a casual leather designed to start showing the suede napp very quickly especially with the ginger undertones of this tobacco suede. I hope all my viewers live and learn. So there you go even more confused. I hope not. Let me just re-emphasize some people use these terms and affix slightly different meanings to these terms. Those differences are caused by the fact that unlike any other science there is no agreed dictionary of terms that the whole leather industry uses. The differences are often caused by nationality, Europe calling things a different thing from America, tradition and dare I say some internet extract that someone once latched on to and then repeat it and like all things internet to some sector it became the gospel truth. Anyway I hope you enjoyed that rather strange segue from boot reviews. If you did enjoy it you know what to do click on like to help my channel out and tell me if you like more of this content and I want to really emphasize the majority of viewers who keep coming back to watch the videos are not subscribed to my channel. Go figure. If all of you regular viewers actually did subscribe my subscriber numbers would go wild so really please subscribe. I'll even bring you boot reviews. Until the next time when you subscribe do take care and I'll see you again soon.