Hello. Perfect. Wonderful. So to do this talk, I conducted a survey. So I want to do a quick straw poll among us right here. I'm wondering, testing one, two, three. Y'all hear me now? As little too far from out there. All right. So I'm wondering, little quick straw poll, how many of us have made a comment to themselves as they were working within their code base? That's amazing. Okay, me too. Not alone. Thank goodness. And there are lots of reasons to want to do this. So maybe you have a variable that you're scared to change. Someone else's code. Do I know exactly what that variable is doing? I'm not sure. Maybe you just copy pasted a section of code from online. And you want to make a quick note? Yeah, I heard a yeah. We've all been there. And it's even easier to forget what the code does when you didn't write it as it turns out.  So, since we're all on the same page, and we've all worked on these comments, we've come to the right place, we're going to dive into code comments. So with all these reasons to add comments and all these hands going up in the room, we might wonder why we aren't making these in line code comments all over the place. Please. Thank you. All right. So we're going to do a quick critique of two comments. I am shamefully sharing with you today. So what happens when someone who is using learning to use comments and commenting to hold their place and relieve some of this cognitive load that they're going through in their learning as they change direction, look up terms, find code samples. So in this first example, what do we think? The tutorial that I used to start the project is cited at the top. Anybody find that reasonable? It's okay to do that? Do a show of hands? Okay, a couple people think that's okay. We've got some skeptics in the room. Oh, yep, I hear you. Okay, well, I'll tell you what's going on up there. What's going on up there is there is some code and then there's a line at the top that says, I took this code from this lovely tutorial and it is turning into this project. This is what I contributed and what came from the tutorial because I'm an academic and I love citing things. So that's what would be on that screen if my color were a little less off. So for most of us, that comment might survive in a code base and eventually be added to documentation as the project goes. And in this second, hopefully with even better color, we see this person was trying to use beautiful soup to scrape a website and send an alert when her favorite on-campus climbing wall was open. And you see there's this little, oh boy, badly colored green square that would say open if we could see it. But our hero has not used beautiful soup before and the notes that she made to herself list not only what she should be doing, her own little to-do list, it also has code that is commented out. It probably doesn't work. And notes expressing her confusion, including my favorite comment to date. Oh, it's a list. Thank God. So would you want to contribute to a code base that had similar pileups of comments throughout? Honestly, when I was pulling out this example, even more experienced me felt confused just looking at this. If this was file after file, I think I'd run in the other direction. Y'all with me on this one? So before we dive in and we talk more about comments, what makes a good programmer? We need to know languages, methods, there's some amount of knowledge that we need to have. We need to have the ability to apply or problem solving and creative thinking skills. And last but definitely not least, we need to be able to communicate and let's face it, right? Usable code. So we spend a lot of time in our industry talking about that first point, knowing a language and methods. But I want to talk about the journey that I took through the other two, that creative thinking and communicating since they're an important part of the mastery we all desire. So, relatable. So documentation is what allows the code to be used, expanded, adapted, and for a community to be formed. Avoid causing other programmers pain. So as I was approaching my own comments as docs strategy, I tried to see what other people were using comments for. And I found a couple of different uses. You can have comments at the top of a file as a summary. Not all of us use GitHub any other academics in the room. A few? Okay, cool. That's where I come from too. We have these nice little things at the top and it tells you the email address of who you should message if it's all messed up. And yeah, everybody loves having corresponding authors. So, they have comments to describe functions. And then you want to be able to maybe clarify any tricky situations you had to go through when you were writing the code. So this will allow you to later be able to create your own standalone docs, in part using these comments. For folks like me who are very visual and enjoy and benefit from having all of their work in front of them, it also could serve as a notepad, so to speak. And as many blogs helpfully or unhelpfully point out, it's important to tell why you're making a certain decision, but your code hopefully tells you how. So there's some confusion about comments. A lot of people think that no comment is bad code. But maybe this is also true. Maybe you're worried about the bail list. I'm sorry, I think this will be hard to see. You want helpful comments but not distracting ones. And it's possible, like this comment claims, that the kind of hazing around figuring out when a comment is helpful documentation and when a comment is fluff and should be avoided is a bit of hazing that we all have to go through as we learn what the proper balance is. That doesn't sound like very much fun. So we debate. So we hear about comment rot. But it's easy to forget that learners, our people or comments might be helping and that you're not going to be able to decide how many comments or what kind of comments are helpful until you've worked within code bases that use them and been able to see them yourself. So remember, we're trying to create the most usable code we can. If you're always having to go to source, it's going to be a very long day. So I started looking and saying, well, are there some things in all this debate that we can agree on? And there are some best practices that we can get behind. We generally agree. Doc strings should have inputs, outputs, explain the transformation that's taking place.  We don't like those. They're terrible. And finally, my favorite advice from the internet, too much. How many comments are too many comments? Well, too much is too much. Thank you. Thank you, internet folks. So sometimes we can agree that the code tells us how while the comments should tell us why. Some folks say, keep things instead of dry, wet, don't waste everyone's time. And that, you know, we put the further critique a line by line commenting may indicate a lack of understanding. So the difficulty for many of us is that there's lots of variation in what is considered best practices for comments as we've discussed. And the explanation is clearly enough. There's variation, different languages, different needs, different industries, and different styles of learning. So companies create their style guides and, you know, decide whether or not we should include doc strings, comments, etc. But we can all agree, no matter what we think about these guidelines, that comments, if used properly, if we can ever figure out what that means, are an invaluable part of a code base. The thing to remember here is that to a beginner programmer, comments can be magic. If you can go back and you can remember the first time you realize, wow, if I put this nifty little hashtag, the interpreter is going to ignore it. And I can put whatever I need there. Nobody just me remembers that. Okay, okay, I see a few hands. All right, well, I was excited. I felt just like this. I was like, oh boy, I'm going to use this all day. So people use this power differently, but many of the new programmers, as I started talking to folks and mentoring, they'll start throwing comments everywhere. I've seen comments for variables, comments that hold questions to ask a mentor later. Comments made during pairing to record some new related bit of knowledge that people are still putting their heads around. Comments used as an outline for code yet to be written. And for the code orders among us, comments holding code that we don't use anymore, but we aren't quite ready to get rid of yet. Even one person added comments that record the URL of the website where they had found some insight, they had stacked overflowed and done that copy pasta thing. It wasn't theirs, so they wanted to show what they had done and not. Okay, so there is a lot of different ways that these folks found to use comments. Really ingenious. And there's one thing as we are pushing folks to do, to be dry and to do things the right way at a time when as newer programmers they're taking on probably more than they can. There's one thing that we forget. I don't really know. WTF. I've done tonight. I committed a lot of stuff to get. Something, something JavaScript. Do you all know this? I don't know.  You'll see this person come out. You may think that you aren't this person, but you've definitely been this person. And we tend to forget that this person needs aids and resources and the ability maybe to use comments however they need to use comments. So as I was progressing through this stage, and I spent a while being this person because I jumped around a lot, I became active in several programming communities and I started to see a trend. Good code is dry. So if you go online and you say, okay, so I've started learning how to comment and I want, I'm a new programmer and I want to be the best programmer I can. So I'm going to find out the best practices and do it the best way all the time and I'll put that on top of everything else I'm learning. If you're going to hear, if your code has too many comments you need to refactor, you're going to hear the very helpful, you should just code better. No, no, this is real. I went and I searched and this was advice that I got. You should code better. You should not use comments. Why are they there in the first place? You should only use the correct comments and you should know the difference. And only your code matters. Now if you're me or you're someone else who is diving deep and trying to find the best way to do something, what you're actually going to hear is, so the way you're learning is an anti-canon. I don't know how that feels, but okay, it doesn't feel very good. Y'all are less emotional about this than I am. All right, so I went to Stack Overflow and there were too many things. I could have made a montage, but instead I'm just going to show you, and it's hard to read, this person has written a very thoughtful, hey, I'm just learning how to do this and I want to be able to document my code properly. And you know, on and on and they're like, I hear this and I hear that. Can someone give me guidance? Can someone tell me what to do? And you know what the person says? This has been beaten to death. Why are you here? And they got a lot of upvotes.  So I don't want to pick on this one jerk because there's a lot of them. But this was continuous as I looked and it was also continuous in the forums that I was in. So I started to ask myself, what's what's going on here? Or is this like, you know, kind of a, there's a beginner, beginner and then a slightly more advanced beginner, like looks down on the beginner, beginner and says, like, you shouldn't do it that way. Like, or is there something more we need to address as a community? So I'm a scientist. There are a few things in the world I love as much as data. And so I asked Twitter a question. And I got a whole nine respondents. Do you know how not statistically significant nine respondents is? But I asked, hey, Twitter, have you always been dry or is that something you came up with as you progressed as a programmer? And Twitter, well, I got nine respondents. And they were split almost right down the middle. If I'd gotten a 10th, it probably would have been right down the middle. And I was a little irked that so many people said they were dry from day one because who is. And that really surprised me. And I said, wow, I need to look at this more. And so I went to places that were not Twitter. And I thank you, thank you. I needed that. And definitely when I started this project, I definitely needed that. So I read a little bit about survey design. And I set out into the world of how do humans think? And I made myself a survey. So I asked a lot of questions. I said, when do you use comments? What causes you to use them? When do you add them? Are we all secretly taking out our shameful comments before we add them to GitHub? Okay, I needed to get down to the bottom of this. I saw a couple of knots. It's not just me. Okay. So so I asked, and then I asked a little bit more about people's attitudes towards commenting in general. Tell me how you feel about comments, I said. And what was wonderful in addition to the multiple choice and scale responses that I got is people, you know, I gave them a space to write about how their commenting had changed over time, or to write after each question. And they wrote, I'm going to talk through and summarize as we go on, because I made the mistake later in putting too many words on slides, as one does. And so I'll share those results with you. So what best describes your current or recent use of comments? Do you comment when you're not certain? Do you comment each function as a matter of practice? Do you use single line comments? Or do you comment out unused code? Shamefully. And I expected because I had so many dry folks on Twitter, I expected I did not expect so many people to say, yes, I using blind comments 90. Let's see. What percentage is that? It got cut off 50 something percent. I didn't expect that. And people said some words. My favorite comment was someone said, as a child. And one really neat thing about this survey, and I want to dive into this data more. So there will be more chatter about this data, and at some point it's going to be on GitHub and we'll all get to play with it. But I had survey respondents who had been coding as little as one month and as long as 35. And it's a really nice spread. And I'm really glad that I put in the effort to cast such a wide net. And that people responded and really had strong feelings about comments that went on for paragraphs and talked about their childhood commenting and how they've grown up since then. And in my heart, I really want to know if this person was truly a child when they learned to program or if they're talking about their childhood program or self, which is how I talk about myself from four years ago. So some folks said, I comment unused code, comments clutter code. So we've got a non comment person in the room. And it goes on. So I asked, when do you add comments? Because remember, I had that long list of reasons for comments earlier that my newbie buddies were using. So I said, how about scoping? Do you have a to do list in your comments? Does it help you experiment? Do you add them as you're completing a program? And a surprising number of people said, yes, it does help me experiment. I'll start writing a piece of code. And, you know, I'm not sure if it's what I'm going to keep. And I commented heavily. I see what works and what doesn't. And I know right back where to go to. So more folks are using that, you know, cognitive load, you know, comments as their little cognitive storage bins. Then I expected. And there are more words. I didn't write comments as much as when I started off, because I wasn't confident that what I would say would be useful. Some folks are literally scared of the prose element of commenting. It's comfortable to write code. Writing code is what we value. But the act of commenting is almost more vulnerable. You are writing documentation. You are explaining yourself. It is difficult. You have to if you have pulled something offline that you don't quite understand, it's sometimes hard to say so. And so I had asked a series of questions that said how positively do we feel about comments? And one is disagree and 10 is strong agree. So a whole lot of folks say comments help me remember what my code does. We see a similar distribution for comments help me clarify my thinking, a little more spread out, a little wider tail. And then we get to comments help me learn. And I'm interested to see here what the distribution is for, you know, how many of these folks have just been programming so long that that's not the A that they use anymore. And it's possible that there are a whole lot fewer new B programmers who are using comments in the way I and some of the people I've mentored have been. So that'll be an interesting thing to look at in the future. We almost all agree comments, you know, the good ones will save current and future developers time. We disagree that comments are helpful to you, but should be removed from GitHub. So all those folks who earlier said that they take out their comments before going to GitHub. You're good. Go ahead and add those in. You can show the world. It's fine. But interestingly, when I started talking about clutter and what was acceptable and not, my distribution wasn't quite so clear anymore. That's a pretty wide tail considering what we were seeing before. And when I get to clear code is self documenting and doesn't need comments, we're a lot flatter. So it's clear that despite all this positivity towards comments among my respondents, we're actually still we've really internalized this idea that good code is going to be so clear that you don't need the words. So let's think about what makes a good comment. And I'm so sorry about what you're seeing right there. So what this person did is they're describing the state of their program in a comment. Like they have a diagram and they say you are here at this point. And I thought that was genius. Because guess what? Sometimes it's really hard to visualize what your code is doing at that moment. Some folks will create a whole man page to describe section of their codes. And it's possible that right now, those obvious comments aren't so obvious to you. And as you get better at naming conventions, you won't want to put Post-its on all of your cats. And in the spirit of this quote, the best comments are a huge help, but the perfect comments are not going to come without trial and error. So what can we do? A lot of us are really experienced. We're probably mentoring. We're probably talking to folks who are figuring things out. So our end goal is to support learners where they're at. You want to praise the accomplishments. And instead of saying, hey, it has to be dry. You might say, you know, I see what you're doing there. It's ingenious that you're using ASCII to show the state of your game engine. But you know, some someday you're going to get to the point where you don't need that anymore. So you got to remember your overwhelmed learner, advise them where they're at. And you might want to suggest a deep dive or reading other folks code. If we rethink comments, the thing I kept coming back to is if we were to think about what comments we're getting. And we said, what if comments are docs? Would we be having another conversation? So I want to thank each of you for coming. You've been lovely. I appreciate your participation, especially. So thanks to Pi Texas. And thanks for all the folks who told me their comment stories. I would appreciate if everyone in this room do not take this survey because we talked about some results and you know what that does, right? So don't do that. But if you want a social media, that thing, my handle is there and whatnot. And I'd love to be able to hear from, you know, more folks about their common experiences. So thank you very much.


The Cube at EMC World 2014 is brought to you by EMC. Redefine VCE, innovating the world's first converged infrastructure solution for private cloud computing. Brocade, say goodbye to the status quo and hello to Brocade. Okay, welcome back everyone live here in Las Vegas for EMC World 2014. I'm John Furrier, the founder of SiliconANGLE. Today, I might go as Dave Vellante. This is the Cube, our flagship program. We go out to the events, extract the signal from the noise and we're proud to have Jeremy Burton here, president of products and marketing of EMC. Cube alumni and when we started the Cube, it was our first event was EMC World in Boston. Jeremy, you just started at EMC. You were on the Cube as a guest and it was a great time. And since then, lots of change. Welcome back to the Cube and congratulations on all your success. Thanks, my, it's great to still be invited back.   And the great thing about the Cube is because it's open source, we're documenting all the conversations. You were on the Cube and you told us, I want to be global. I want to control the narrative.  So tell us, are you happy where you are right now? I mean, cloud meets big data. I mean, it was, you know, during the private cloud was, I think you kind of inherited that, but you then quickly moved to cloud meets big data. And since then really the EMC narrative has been spectacular, you know, great conversations around that. Are you pleased with it? And what's your, what's your take on what's changed in the past four years? Yeah, so I mean, I think first things, you want to be part of the conversation. I think in this business, you know, if you're at a company that customers don't believe you're relevant to the future, you might as well not exist. And so I think, you know, although there's a lot of great technology within EMC, I think the first, you know, kind of objective is to establish relevancy in these new areas like cloud and like big data. But, you know, right now, what you see is that the customers that they're a little bit past the top level headline of cloud and big data, they really want a little bit more, well, okay, how do I do that? And what are the products and services that I should use to move in that direction? And the reality is a lot of these new applications that people are going to build are going to be different. And the infrastructure is going to be different. And so when you see the theme around here today around redefine, that's not just kind of redefining the perception of how people think about EMC. It's really challenging the attendees at the conference. They've got to redefine how they look at their infrastructure, if they're IT guys, they've got to redefine that relationship with the business. And, you know, underneath all of that, you know, I think probably closest to their hearts, they've got to think about redefining the storage infrastructure, which is what most of the people at the conference do on a day-to-day basis. In following your career, CMO, now president of the product, you quickly moved into the product space as the market was very dynamic. What's different now than a few years ago? In terms of the product mix, obviously Flash is heavily at the center of it, software, what key knobs of the EMC product portfolio do you have your hands on the most right now? Yeah, well, I mean, my entire career, I've always kind of dabbled a move back and forward between, you know, be it marketing or product management and running development teams or product teams, so.  Yeah, well, yeah, back in the day, yeah. It was, you know, C++, that seems a long time ago. It's because it was a long time ago, I'm getting old. But now, I mean, what are you, in the portfolio, I'm in clearly Flash, right? Whenever the media changes, you know, tape to disk, disk to Flash, that's a big deal. You want to be on the front foot there, which I think we are. I think we've got a great portfolio, not just the traditional products, but ExtremeIO and now DSSD, but the thing you can't ignore and as much as I think we're well equipped for that transition to Flash, the reality is, is that in the next four years, you're going to see 3% of the world's data on Flash, which means that still 97% of the world's data in the enterprise is going to be on hard drives and we're moving much more to this architecture around having a hot edge, which is the performance here based on Flash and then a cold core, which is the capacity to, you know, predominantly based on hard drive technology and those two things, you know, really need to operate and orchestrate together. So at the conference this week, when you've seen things like DSSD and ExtremeIO, and then you see things like Nile turning to the elastic cloud storage appliance, capacity optimized workloads, you can start to see where the hot edge and the cold core is coming from. What's a quick update on some of the stats here at the show in terms of just the data, in terms of some of the customer activity that you're involved in. Now, as President Frost, not just overseeing the marketing, there's a lot more customer engagement here. We've had, so a lot more engaged customers talking. What's some of the stats and what are some of the customer conversations you're hearing? I mean, the customer conversations are pretty wild. I have to say, and actually interestingly enough, a lot of the customer conversations then they're not just strictly taking place at like the EMC office, Pivotal and VMware offices as well. And I think the Pivotal guys in particular, they have business people coming to them and saying, look, we want to become a software company. So these are retail clothing companies. These are pharmaceutical companies. These are banks saying that we need to be a software company. And a lot of those new applications and that new software that's written is going to drag a different set of infrastructure. So we've found ourselves at the table now, not just with the IT teams, but actually with a lot of business executives and a lot of the time, they actually don't bring the IT team with them. But obviously what they're working on is going to have a profound impact on IT. Jim, I'm going to ask you some product questions if I may. Viper, obviously big announcement last year, focus this year Viper 2.0. Is Viper the future of storage? Is it the future of software-defined storage? Or is it a way for EMC customers to consolidate sort of the different platforms that they have or both? Yeah, it's a little bit of both. I mean, this is, I think, probably one of the magical but also confusing things about Viper. It is our software-defined storage platform is the way I describe it. The control plane is the thing that is really the cloaking layer that's going to allow the storage administrator to treat all different kinds of storage in a very, very similar way. So you can automate provisioning and a lot of storage operations in a very consistent way. But the data plane of Viper is really what's given rise to the advent of truly software-defined data services that can run against existing arrays or they can also run against commodity storage hardware as well, so it's a weird beast, which is what makes it unique. And I think more to the point from a product strategy standpoint, you got to think of it as almost the architectural backplane that all of our portfolio will hang off. So I have to ask you another question. So I was in the session this morning, the analyst session, and Bill Richter was talking about how a dupe is just smoking on Isilon. And I had texted our big data guy who happens to be somewhere else. And he said, that's interesting, he's not a hardware guy, he really doesn't understand that business. He said, I'm surprised, dupe is all about scale out, low cost, commodity infrastructure. And I said, yeah, that's what Isilon actually is, relative to everything else that was out there. So my question is, does Viper change that game even further? Is it going to be just a dupe machine or is it more going to be towards service providers, a combination, help us understand where it's going to go? Yeah, like everything. We think the world of Hadoop, it's going to take place at different scales and there's going to be different performance requirements. And in the same way as the traditional storage world, we've never believed in one size fits all. I don't think that's going to be the case in the world of Hadoop and data analytics. I think at the hundreds of petabytes in exascale, I mean that's really what Viper was architected for. If you look at the cost, it's going to be the cheapest. But the reason why Isilon's doing well is in the data center, if you've got data sitting in Isilon today, it could be hundreds of terabytes and you want to access that data through Hadoop, it's easy, it's right there, you don't have to move it. And so, Isilon's going to be one of these very interesting kind of general purpose big data machines. If you look at what say the VNX does on the transactional side of things, you got to look at Isilon being that kind of Swiss army knife on the big data side of things. At massive exascale, it is absolutely going to be more expensive. You are going to go to this very distributed kind of shared nothing architecture. But then I'd also say, I mean we saw DSSD yesterday. Hadoop over time, there are going to be use cases where it's not an offline batch thing, it's going to be a real time thing. And so you're also going to see DSSD, surface things like HDFS out of their infrastructure to do these super high performance, but also more expensive Hadoop kind of workloads. We've got a number of customers in the Wikibon community of actually bringing transactional data and analytical data together. Ad serving is a good example obviously, but there's other use cases. I want to ask you about Nile. You announced Nile I think in the fall, right? July last year, yeah. It was a July last year, I think somebody's going to hit the launch. It was a mega launch, okay. Imprinted on my brain. Yeah, okay, good. Okay, Nile, the biggest river, bigger than the Amazon, okay, great. So now you're really starting to bring that to market. It's called the Elastic Cloud Storage. Talking about 28% lower TCO than public cloud services. Talk a little bit about that and sort of what customers are telling you. Yeah, if you do the math on that, I mean a lot of people don't realize that your storage is relatively cheap, right? I mean you do the math on the Elastic Cloud Storage. It's a couple of cents a gigabyte a month, which is not a whole lot. And now for a certain class of workloads, that's what's required because the data volumes are massive. And we see not just kind of enterprises building out, starting to build out these massive, capacity optimized storage tiers, but also the service providers as well. And we think the Elastic Cloud Storage appliance, it's going to go in both places. It's going to go into the enterprise. It's also going to go into service providers as well. So Jerry, we had two questions. One, redefine, words like redefine, Elastic, sound familiar to me. Amazon has reinvent, you guys have redefine, they have Elastic in there, Elastic Cloud, Elastic Beanstalk, you guys have Elastic Storage. Was that by design or is that just coincidence that sounds familiar? I mean, why reinvent when you can redefine? You know, don't fight fashion, right? I mean, there's one of my old bosses, actually a funny story, I spent a lot of time at Oracle over the years, right? And Larry Ellison, I was fortunate enough as a kid to kind of watch that guy at close quarters. One of his great lines was, I spent enough time in Italy to know that fashion matters. And it's the same in the tech business, right? If the term that people understand for storage pools to grow and shrink is Elastic, use Elastic, I've never been the person that thought, we've got to go reinvent or recreate our own segment in order to be relevant, right? There are relevant things out there that we want to be a part of. So, speaking the language that customers understand. Yeah, exactly, don't create a new term, no one understands it. Well, great, I knew this Jeremy's, but fingerprints were all over that. Very clever, it's awesome, by the way, totally agree. Second question is about developers, right? So, right now we're living in a modern C change, Joe Tucci, cause it's software-defined enterprise. Clearly, DevOps and Cloud have shown that way. The Federation's all set up with VMware, certainly, with Pivotal. Yeah. A lot of chess pumping on, we're going to win the developers, it's hard, right? So, how are you guys looking at that at a federation level? Obviously, it's not that easy. You can't just throw a Barney deal together. You know, I see, you know, some are saying that the Cloud Foundry deals are very much Barney deals. You know, we love each other, but where's the meat on the bone? And certainly it's a good strategic direction, but where, how are you guys going to win the developers in this new and modern era? Yeah, so I think, you know, you're banging on the right door with Cloud Foundry. I mean, I actually happen to think it's one of the most strategic assets we've got in the entire federation. It's probably an asset that we've not played as much as some of the others, right? I mean, certainly, you know, NSX and Viper and the certain other things in the federation have gotten more play over the last year or so, but Cloud Foundry, I think, is one of the most strategic. We look at it as, you know, as we produce the, you know, the HDFS interfaces, for example, that are going to, you know, plug into Hadoop and so on. We've got to surface those things up through Cloud Foundry. So, you know, EMC ourselves, we're probably not going to go direct to developers. We're going to use Cloud Foundry as the vehicle to go to the development community. And what I think a lot of people are starting to realize is that there is room for an independent, truly community-owned platform as a service layer. And the way the pivotal guys are setting this up is your influence in the community is going to be based on how much code you contribute. So look, anybody can sign up and whether they're Barney deals or not is, to my view, is neither here nor there. He who commits has influence. If you don't contribute anything to the community, your name will be on a logo, but you'll have no influence. If you commit a lot to it and you move the ball down the field, you'll have a lot of influence. Well, one of the guys involved is from Piston Cloud and he also was involved in setting up OpenStack. So, and that's a lot different than OpenStack in terms of a community-led infrastructure. Do you see our community-led software environment? Is OpenStack in conflict with that? And how do you guys view OpenStack? Is that a complimentary? Yeah, to me, it's a level lower. It's only, I don't think OpenStack is trying to be any kind of pass layer. I think really what they're trying to do is create a framework for which folks can deploy infrastructure to make it easier to manage and provision. The cloud foundry push to me is really a pass layer to developers and then an automation layer to simplify the deployment to any cloud which could be OpenStack or not. So what kind of contribution do you guys make? Well, so the main contribution to Cloud Foundry right now is through the PivotalGuys and actually the secret sauce in all of this is Bosch is the name of it and that is the magic that does all of the deployment of applications to third-party clouds and so on. But over time, I mean, look, we've got IP within the EMC community. I mean, the APIs that we've surfaced northbound, the HDFS layers there, potentially as well. I mean, it is a source of huge debate internally whether we should go for it and open source the ViperController, right? I mean, there's a whole bunch of northbound APIs there which would be useful from an automation standpoint. We've not pulled the trigger on that yet, but as I said, it's a source of vigorous data internally. Yeah, it would be a big move. I got to ask the marketing question because we've always been big fans of what you've done as a CMO now as president, especially in the social media area, which you've been a big supporter of theCUBE, which is what I never know that you've done that, been great champion of our effort of open source social media. But you've made some good calls around how you've invested your dollars in terms of social media, paid media, earned media. What is your take on the current trend right now out there in terms of marketing? You've got obviously the paid media, owned media, this whole earned media, you guys have invested heavily in a lot of that. It's still early. What are some of the things that you see that are working that need development around this new social fabric? I just, I'm kind of a broken record in this stuff is, I still feel like 80% or 70% of what marketers do, I wouldn't say it's a waste of time, but it needs to change, right? There's a big move back to quality content. Content is king. If you've got something interesting to say, people will listen and they'll listen in the thousands. If you're BS in people, you've got nothing interesting to say, you're spamming people. You've got no voice. And that is the harsh reality of the world that we're living in. It's very noisy, but high quality content will win out. And so one of the things that we're looking at, and this is now Jonathan's Martin's job, as well as playing the guitar, he's actually got a great mind for the online and the digital. And I think a lot of this is retooling the organization so that we can, within the marketing team, generate the quality content and then have that content and appear where the people are. Because what we really want is inbound. We want people coming to emc.com having known a bunch about our products, maybe even downloaded our product for free. And that eliminates friction in the sales cycle. It makes it easier for our sales guys. And I think it actually puts the customer in a position where they want to be, which is a position of knowledge and therefore a position of power, right? Who's your team in the Premier League? My team actually isn't in the Premier League, right? So unlike the U.S. where these football teams can kind of give up on their hometown and move somewhere else, in the U.K., if that happened, that would be a civil war. So my hometown team is Middlesbrough. So they were a Premier League team six to seven years ago. They're now a championship team, but my dad's a Newcastle fan, so that's as close as it gets. Okay, Jeremy Burton, Cube alumni. Great to have you on the Cube as always and congratulations on continued success. I'll give you the final word. Put the bumper sticker on EMC World this year as the truck leaves Vegas. What's the bumper sticker say that summarizes the magic of EMC World this year? I mean, it's really about a bridge to the third platform. We realize everybody coming here has made a career out of running the second platform applications. There's a new dawn emerging and if they stick with EMC, we'll take them there. Jeremy Burton here, this is the Cube. Be right back with our next guest live in Las Vegas. Be right back.


A working group developed a new tool for assessing methodological quality of studies reporting prevalence data in systematic reviews, which was piloted among healthcare researchers and found to be valid and easy to use. The tool is now recommended for use by authors conducting prevalent systematic reviews. This article was authored by Zachary Munn, Sundit Mula, Dagmar Ratano, and others.


Welcome to the Addiction Recovery Channel. I'm Ed Baker. Today, we're very lucky and pleased to have Sarah George, Chittenden County State's Attorney as our guest. Welcome, Sarah. Thank you for having me in. Yeah. Sarah has been our State's Attorney in Chittenden County since 2017 and has really been an outspoken advocate for people at risk for drug overdose and death. And that will be our topic today. Sarah, just in general, in your own words, can you please describe what you see happening in our beloved Chittenden County today? So I think what I've been seeing lately is what I've sort of seen historically, but given COVID has seemed to become worse and worse with time, and that is that as our social service resources have dwindled, our risk of drug use and drug overdose has gotten worse. And people are struggling in a way that I haven't personally seen before in our community. And that, again, I think is from, well, when COVID hit, a lot of our social services closed. A lot of individuals were kicked out of their housing or lost their housing due to the housing market. Our voucher program had all of the issues it did. We had encampments getting taken down. And all of those things have made our social service issues and our social issues in general have gotten worse. I mean, I know that part of your role is to respond to overdose death. So what are you seeing as the trend in our county and in Burlington in particular? What is the death toll currently? And has it been increasing over the past years? And how do you see it as like moving into the future also? Any predictions? Yeah, so because our office is called for every overdose fatality, I have been keeping track for the last four or five years now, at least for how many people are dying. And what I've seen so far this year is that we're at around 50 of our community members, and that's in Chittenden County, who have died from fatal overdoses. That's about on track with last year, if not a little bit higher. But certainly last year was significantly higher than the two or three years prior to that. So we are seeing overall an upward trend. And we're also seeing that the places in which individuals are dying are more and more sort of brutal and sad in that people are dying in cars and in the parks or in public spaces and public restrooms. I think, again, going back to how many more people we have without homes in our community means that those deaths are occurring in really scary places. So approximately 50 deaths to date, and this is getting toward the end of November. If I'm not mistaken, I do believe last year the total for the year was 51 or 52. So it looks like we're losing more than one Vermont per week in Chittenden County. Is that correct? Yes, that would be my estimation. We haven't had any fatalities in November, so certainly there are weeks where we don't, but overall there are some weeks we have multiple. And certain times of the year seem to be a little bit worse, but overall I would say once a week is accurate. And in the state, I know last year the Centers for Disease Control estimate was a little above 260 Vermonters lost. The state estimate was a little bit lower, but Chittenden County, I do believe, has the highest number of deaths per year. That may be. I really only focus on Chittenden County typically because that's my world, but that would make sense, certainly given our populace. We have over a third of the state's population, so I would be quite surprised if we didn't have more than the rest of the state. Let's just take a look at this slide that we have here. This is a Burlington Police Department overdose response slide. And as you can see, obviously, it's so clear the concentration of overdose responses and also overdose deaths is in Burlington, downtown, Burlington. I think that's a very poignant visual. Do you have any comments on that? Yeah, I think that what we see everywhere in the country is that these overdoses tend to happen in places that are concentrated with services or bus stations or shelters and all of these other things that might bring these individuals to those areas. Certainly, Burlington is always at a higher risk of having higher numbers. Those blue and purple dots are really terrifying to think about how many people are overdosing in our downtown center. Given this, the kind of language that I use to describe this is catastrophic. What do you see as going forward? Do you see any... Given the structure that we have in place to deal with people with severe drug use disorder, people who are overdosing and dying, can you predict the future? Do you see it as improving or staying the same or worsening, giving you a vantage point and your knowledge and your experience? What are we in store for here? I would say that based on what I see in my office and the individuals that are coming through my office, if we continue to treat this as a criminal issue and a police and prosecutor issue versus a public health issue, and we focus more on putting these individuals in jail versus giving them housing and providing them with housing and employment and services, this is only going to get worse. But if we really take the time to spend those same resources or the settlement money and other things that the state has access to, to actually giving these individuals support, and that's not just through drug treatment, but a lot of these individuals are suffering from really significant trauma. They need mental health services as well. They need child care as much as a lot of us are dealing with, and they need, again, safe and secure and affordable housing and employment. If we don't focus on those particular things and spend the resources there, it's only going to get worse. And I would also say that as long as, again, we see this behavior as criminal, we're going to be responding to this issue instead of doing anything to prevent or help. Well, thank you. Thank you for your perspective. Sarah will be joining us as a member of a panel at the end of the show, a panel that will be focused on solutions. For now, Sarah, is there anything that you would like to personally say directly to people out there in Chittenden County who are at high risk for drug overdose and drug overdose death? Yeah, I mean, I really just want those individuals to know that I care about them, that I want them to survive, that we can't help them if they are no longer with us and that I don't want to be responding to the scene of their death. And if they are feeling like they are ready to not be in this situation anymore and want help, then I would suggest that they go to the Monash for Criminal Justice Reform and talk to those folks or go to the hospital or go to the methadone clinic, go to anybody that they think will help them and start that conversation and we will do what we can to help them get into some type of treatment. Yeah, thank you. Thank you so much. I appreciate the work you've done and I look forward to supporting the work that you will do in the future, Sarah. Thank you, Ed. I really appreciate that.


So welcome back to the Friday Vogue series where today That's right. I've done it again. I bought myself another bike. You are out of control, mate And yes, I can appreciate what some of you may be thinking as we've recently just built the Chinese carbon bike I purchased at the back end of last year being the windspace the factor O2VAM is being built next week And now I have a brand new BMC team machine SLR-13 but I have a very good explanation for you if you can bear with me And I promise this will be the last bike that I purchased for at least a few months So let's break this video as per normal into my favorite number of parts being two part number one I'm going to share with you why I've purchased a brand new Lamborghini orange BMC team machine SLR-13 With SRAM Force 12 speed and some lovely DT Swiss carbon hoops And this purchase kind of happened through an unusual Sequence of events which I'll explain to you shortly and part number two of this video What's been going on behind the scenes including what my wife thinks of all these bikes and also wishing her a happy birthday today So part number one what on earth am I doing with this bike right here and in this section of video I'm going to share with you a conversation I had with the head mechanic at Trilogy Cycles Aaron is his name about building the new BMC's front end So in 2020 an opportunity that I wasn't really seeking just started to present itself to me It was creating a Masters A or old bloke cycling team for the Road Cycling Academy or the RCA Which is a coaching business. I started through this channel in 2019 links below if you want to check it out but in order to create a team I wanted to have for me anyway all the gear and absolutely no idea the other riders have an idea They're way better than I am, but we needed the gear So in order to present or pitch to the riders about the team dynamic the racing and the equipment We were going to have I reached out to my friends at advanced traders here in Brisbane Queensland Australia mate and advanced traders for all those of you who don't know advanced traders are the Aussie distributor for BMC and Merida And if you have been supporting this channel for a while, and if you're not yet supporting and you're thinking about Subscribing because you're getting value out of these videos. I'd really appreciate your support below subscribing to the channel Because I'm getting a little bit twitchy as we head towards that hundred thousand marks I please just tap it in below much appreciated But back to the story I have loaned and reviewed through advanced traders the Merida sculpturer The Merida reactor and the BMC time machine and in between all of that I have also purchased a BMC team machine for my own use directly from Keith at trilogy cycles here on the Sunshine Coast Who by the way has one of these in store for all my local friends that want to go in and check it out So I rang the BMC brand manager at advanced traders His name is Rob and pitched the RCA team to him and he said we've got some of these Lamborghini orange BMC SLRO ones coming in and we could provide them to the team at a local amateur Sponsorship rate, so we'd be paying for them still a fair chunk of money, but we get a discount on the bike However after organizing all this not only the bike the helmets the shoes and everything The RCA team became too hardbasket and so long story. I'm not going to bore you with all the details No one cares mate. Stop waffling. Yep, you said it So I ripped the Band-Aid off before we even really got started, but the whole process Got me very excited about owning this bike here Which is an updated geometry and design from the previous version that I had and for your information I owned a BMC team machine in 2014 and absolutely loved it The only reason why a part of ways with it was because of the formation of the original Inform amateur cycling team which had us all on specialised Tarmac's, but the BMC team machine has always stuck with me And that's why I purchased it again in 2019 but selling it again recently to Makeway for new bikes in 2021 that was a sad day So I've come to the realization that my cycling life is better with a BMC team machine in it I really do like this bike and no one is paying me to say that despite What some of the skeptics out there think it's perfectly normal human behavior to like things and just because the channel has gotten to a Certain size. I don't feel I should have to refrain from saying I like this bike here a lot Now know what some of you may be thinking though. Ah, so we got the bike for free Didn't you mate? So I paid the same rate as what the team was going to pay So it's still a fair chunk of money And if you follow me on the Facebook marketplace groups in the cycling groups You'll know that I'm selling lots of stuff at the moment to be able to fund this and all the other bits and pieces That are going on and a continuation of that thought I know will be. Ah, here he comes captain biased Yes, I got a deal on the bike and I know some of you will be saying I hear this often in the comments that His review is going to be tarnished now We can only trust the review if he's paid full price on the bike But just hear me out here when you become a cycling YouTuber as I did in my late 30s after 15 years in corporate your salary goes from up here To down here and even with a channel of a hundred thousand almost Subscribers some of you may find the surprising I earn less from this channel than I did from my first corporate job in 2003 in my early 20s. I'm almost 40 now So I don't do this for money and I do it purely for a passion for making videos and a love for cycling So please Give me a break for getting a deal on a bike a bike. I want to ride and a bike I will review in the same fashion I have been reviewing bikes on this channel for almost three years now and if I don't my credibility It goes right out the window. You're smart. You will know So please have some faith because I've kind of had a bit of a gut full of this new grief That I've started to get below in the comment section. So now we have that out of the way Sorry, I just had to get that off my chest. You now know why I purchased the bike What is the content going to look like for this project over the next few months number one? We're going to do a front-end build video with Aaron at trilogy cycles number two a first impressions video and number three a Formal comprehensive sit-down review. So before we get into part two I did film Aaron at trilogy cycles putting on the front-end, which we're going to do a separate video on but it's quite a tricky process I've never watched somebody do it So I thought I would share with you some of the things he shared with me after putting the front-end on Before we get into part two of this video. It is yes So we've predominantly for the front-end so with cockpits or the new style of bicycles It was starting to see come on to the market with the integrated cockpit assemblies and with internal cable routing obviously if it's a Narrow bar wide bar stem lengths and so forth is important as well, but it's more about trying to find out You know length of cables length of hydraulic lines with Shimano systems obviously you have all the DII charging ports and so forth so We can tailor fit those items and change obviously cockpits like with BMC you can choose a different cockpit So what we want to do is make sure that we can cut the assembly to your height requirements again. That is Imperative when it comes to hydraulic lengths And yes, so with this bike today for your bike what we've done is we've chopped out 40 mil of steerer tube length We've lowered obviously the front-end cockpit to get your fit requirements So that's something that's we would obviously talk to the client about and guide them as well If anything you're probably better off with a bike that's running taller, you know, and we can progressively Make you lower to suit your riding dynamics. So so what's been going on behind the scenes? Rossi Rossi hasn't been in the vlog recently apparently I forgot about that come on come say hello up here No, no around here mate this way. No Rossi Rossi. Oh, no, he's eating your popcorn Rossi Rossi right here up here. That's it. That's it. See it. So hello to everyone.  Say hi to everyone Oh My gosh So an update the factor O2 is caught on the couch here. It's super light This is being built by Jay Taylor at Taylor cycles in Brisbane on Monday. So in a couple of days time That's assuming the SRAM red 22 that I've got for it because now I've got SRAM force access 12-speed on that bike. I've decided to go with the light weight SRAM red 22 for this bill that's stuck in a depot in Brisbane. So hopefully it arrives on time Depot depot depot Did they say depot in some other countries? Correction a lot of people are asking me about the wind space. What's it like to ride? So over the last I'd say week and a half to two weeks. We've had torrential rain non-stop. There's been flooding In New South Wales in parts of Queensland where South East Queensland Fortunately, we haven't been stuck in any flooding, but it's been constantly raining So I haven't really been getting out and riding at all. I've ridden the wind space once for 30 kilometers at like 32 kilometers an hour So it's not enough for me to be able to share any experiences with you and next week after the bike build I'm going to Melbourne for a week. I'm not taking any bikes with me Yeah, it's gonna have a week off the bike So I'm not gonna have any really solid feedback for probably two to three weeks on the wind space Sorry about that and outside of that Alice. Can you tell us just quickly? Your birthday tomorrow. I'm just wait a second I'm gonna have to give you the audio thing so you can talk and also what are your thoughts on all these bikes I've got lying around the place. Give me a second So, how old are you turning tomorrow? 30? We don't have to tell us. You don't have to tell us. 39. Well, what are we doing for your birthday?  We're going to the spirit house for lunch And what do you think about all these bikes lying around the place? What do you think about all these surfboards laying around the place? It's a contra arrangement