Today, we're going to be looking at a handful of sneakers that I think are great for styling year round. And to make things even better, I'm actually going to show you guys 11 different sneakers that are all under $100. First up, we have the Adidas Continental 80. I think this shoe can be dressed up, dressed down, worn with shorts, worn with pants, and honestly worn any time around the year. And normally the sneaker retails at around $100, but sometimes you can find it on sale even at prices low as $50 and $60. Now as we know, when it comes to sneaker heads in the shoe game, there is going to be a high demand when it comes to a lot of sneakers these days. So some of these sneakers on this list may be a little bit harder to get than others, but for the most part, you should be able to get your hands on all of these for the retail price point or even able to find them for a discounted price. Next up, we have a classic right here and that is the Vanskate High and Skate Low. Retail on the high top is going to be somewhere around $80 and retail on the low top is going to be somewhere around $70. Now these we know are very universal sneakers, again when it comes to dressing up, dressing down, wearing them year round, all those same things. Now honestly, all these sneakers on this list are meant for those reasons, that's why I wanted to put this list together for you, but basically I think the Vans are another great sneaker. If you get the all white version, you can easily throw them in the wash, clean them up, bring them back to life and be able to rock them again. Some people even kind of like when it has that kind of little dirty vintage kind of look to it as well. That's always some type of aesthetic depending on the outfit. Obviously, if you have a cleaner outfit on, you don't want to look like you have some completely dirty shoes, so you do want to clean up your shoes at the same time, but when it comes to these all white sneakers, I think these are definitely a must have on the list and easily affordable sneaker that you should be able to get at your local malls or online from the Vans website for again somewhere around $70 to $80 depending on the shoe, and you might be able to actually find these on sale even at other discount places like Ross or Marshalls. Next up, we have another Adidas sneaker right here, and this one is an all time classic. Whenever I think of all white sneakers, this is definitely a shoe that comes to my mind, and that is the Adidas Stan Smith. These right here also come in a bunch of different colors and variations, but typically when you think of the all white Stan Smiths, you think of the pair with the green on the back, and then they have other versions with a little bit of color on the back end, or you can find an all white version as well with no color at all on the sneaker, but I know a lot of people are happy with the green or that navy kind of look or the black on the back end when it comes to this shoe in particular. These are a leather material on the standard white pair, so this is a lot easier to clean as well. They do have different versions with suede and stuff like that, but for the most part, when it comes to an all white Stan Smith, you can never go wrong with these, they're never going to go out of style, they're always going to be a classic, they're always going to be a banger, and you're always going to be a happy camper. Also when it comes to this sneaker, the retail is going to be just under a hundred dollars, so around 95 to 100 bucks depending on taxes and shipping or where city you're located and stuff like that, but at the end of the day, again, another a hundred dollar sneaker that is very affordable and very universal for a lot of different things. Oh yeah, and by the way, if you didn't know by now, my name is DJ and this is the DNA show. On this channel, I love talking about sneakers and especially giving you guys tips and tricks and hacks like this on ways to budget and be able to get affordable sneakers for your lifestyle and what you like to rock. So if you haven't already, consider subscribing and joining the fam. We're on the road to a million subscribers and you could be the next one to get us there. Now let's take it to sneaker number four. And that is the New Republic Kurt. Now these right here, again, another all white sneaker that is very simple, very clean, has a leather on the upper similar to the Stan Smith, but a different brand and slightly different when it comes to the shaping, but essentially, you're going to see a very similar vibe when it comes to this shoe. And these are going to be very affordable anywhere from that 60 to $80 depending on where you're purchasing them that and what there's a sale or anything like that. But either way, another very affordable sneaker. I personally don't have them, but I do see a lot of people rocking them and I know that they look good on feet and I do appreciate that sneaker as well. That's why I put it on this list. Now let's take it to sneaker number five. And that is the all white Nike Air Force one low. Now when it comes to this shoe right here, we all know, I don't think I need to say much, but this is a very classic, very iconic staple sneaker that will never lose its energy and will always be considered as one of the best all white sneakers to ever be made. And I don't know if that's a biased statement because obviously I love Nikes, but I do love all brands and at the end of the day, I personally feel the Air Force one is one of the greatest out there. Let me know what you guys think down below in the comments section. Now the retail price on these, which is crazy, used to be like 80 bucks low key, probably like 70 bucks back in the day. And they've been just slowly, slowly creeping up over the years. We'll see a $5 price, then a $10 price hike, another $5 price hike, $10. Next thing you know, the shoe is now around $100, which is okay because I still think at the grand scheme of things, all white Air Force one goes with a lot of things. Very affordable shoe. So if you want to add these to your collection, might be a little bit harder because there is a high demand, but at the end of the day, you shouldn't have too much trouble. They've been restocking them a lot. So good luck to you if you need a pair. I know typically in the winter time, they do sell out a little bit more often when it comes to the numbers and gifts and things like that. So whenever you have chances to stock up on one, two, three extra pairs, trust me, it's worth it because then you don't have to worry about going through the struggle or even potentially paying resale for a sneaker like this, even though it's a $100 price point on the retail shoe. Next up, we have the Reebok Club C85. Again, another iconic sneaker similar to the Adidas that we saw at the beginning of the video, but they do have their own twists and their own style to them as well. Very simple, a little bit when it comes to the materials and the different switches up with the patches and everything, not super minimal like a Stan Smith or anything like that. But at the end of the day, again, very clean shoe. I love these. They look great on people's feet. They look good, clean and dirty. I think this shoe looks really good. I know some people are saying, well, this shoe looks good, dirty. Trust me, there's some sneakers out there. They just kind of look better when it's got that vintage kind of look to it. Some people might be able to test that down below in the comment section. Let me know how you guys feel about that when you got that more vintage worn vibe on your white sneakers. Also, I'll make sure I have a full list for you guys down below in the description, giving you guys all the information you need for all the shoes that we went over and links to be able to go and purchase the shoes if you ever want to. Next up right here, again, another iconic shoe.  They're going to be on that similar vibe as the Stan Smiths or something like that. You are going to find versions that do have a little bit of color on the upper. So if you're looking for a complete white version that is going to be out there, but typically you see the classic white with the black stripe or the different color stripes on the sides, like kind of like what we talked about with the Stan Smiths, you get the white with the green on the back or something like that. So always something to consider, definitely a very classic iconic model. They do really well when it comes to the switching up with the materials and the collaborations and stuff like that. So not only just good for a white sneaker, but overall just dope sneakers for your collection. You're going to like these. And again, these are the type of sneakers that you can get for a very affordable price and actually be able to find some of these pairs at places like Marshalls, Ross, TJ Maxx, stuff like that as well. Next up on the list, we have the Nike Killshot 2. And honestly, I have not really been a huge fan of rocking this sneaker, but I know I do see this a lot on people's feet. So I figured it was only right that I put these out there to the world to let you guys know about them if you didn't know about them when it comes to an affordable sneaker under $100. Let me know what you guys think about these down below in the comment section. I don't have any personal problems with the shoe at all. I just, for some reason, it's just never fully gravitated to me. And I think that's completely fine as well.  It's all up to you, right? I'm just trying to help you guys figure out the shoes that you may want to consider to adding to your rotation in the future. Next up right here, just at $100 as well, we have the Nike Blazer High and the Nike Blazer Low. Now I, again, same thing. I'm not that big of a fan of Blazers. I'm a size 13, so maybe that's the reason with the white sneaker, the Blazer looks pretty huge. In my opinion, it just doesn't look that well on my feet. And I know some people like lacing them up tight and that's definitely like one of the top TikTok sneakers. We see a lot of TikTokers rocking dirty, crusty Blazers on their profiles. Again, that's up to them what they want to do. If that's a part of styling and some people like them with that more vintage old school look.   But again, that's a whole other topic. Either way, the Nike Blazer High and Low are definitely very good sneakers, classic iconic models that have been around for over 30 years and it completely makes sense why people will want to rock these. And honestly, they do look good on some people. So I cannot be mad at that at all. When I see sneakers, I can still appreciate them. Don't get me wrong, I may not have to purchase them, but I can still appreciate a shoe. So yes, I like the Blazers. Let's take it to the next one. And that is the Converse Chuck Taylor Low and the High Top. Now I know some people are only fans of the Low's and some people are only fans of the High's. Similar to the Blazers, I know a lot of people do like the High version, but I feel like there's definitely a heavy mix when it comes to these two on the Converse Chuck Taylor's as well. These are gonna be very, very affordable. You're gonna be able to get pairs. Sometimes you can find, again, Ross, Marshalls, TJ Maxx, different places like that. You might be able to find a pair for 15 or 20 bucks and get a really good deal on a pair. So good luck to you if you are able to, but if not, it's still fine, cause typically you're in a pair, you know, anywhere from like 50 to 70 bucks, depending on where you're going and if you get a special version or not, but besides that for an all-white sneaker, again, classic, iconic, all that stuff. Some people say they're comfortable. I have pairs. I kind of rock them sometimes. I wouldn't say they're that comfortable. I don't know. That's another pinion-based thing. Let me know what you think down below. If you have a pair of Converse in your collection or you rock them in your rotation, how comfortable are they out of 10? For me, if I were to say anything, I feel everything when I walk on the ground. So I would say there are probably a solid four out of 10 when it comes to how comfortable they are, but when it comes to styling and the look, I love them, they look great. So those were 10 different sneakers right there and I promised you guys I would give you 11. So this last one right here, another classic iconic banger, looks kind of weird on my foot, but I do own a pair and that is the Nike Cortez. I think right here when it comes to all-white sneakers, again, you cannot go wrong with these, depending on your foot size and your style and your aesthetic and everything, this shoe could look really fire with an outfit. You could wear them any time of the year. You could dress them up, dress them down. It looks super dope, super fly. So I feel like that's just a shoe that had to be on the list. And if you guys have any other recommendations for other affordable white sneakers under a hundred bucks that are not on this list, please drop comments down below so we can help each other out. And if you wanna see anything in the future and you have questions or any other top 10 or top five videos or anything like that, make sure you guys let me know down below in the comment section. I appreciate you guys as always. Peace. Yo, if you enjoyed this video and wanna grow your collection or make extra money on the side, I built a VIP mastermind that will teach you everything that I've learned about growing my sneaker collection over the past 15 years. This will also give you access to the DNA fam in my VIP community where we talk about investing outside of sneakers. And don't worry, if you don't plan on joining the VIP community, it's okay. I also set up a private DNA fam community that gives you access to all the behind the scenes looks from the studio and multiple chances to win free sneakers and gear from weekly and monthly challenges. So all you need to do is click on the link down below in the description or the first link pinned in the comment section. That will get you set up and into the community. I'm excited to see you guys on the inside. Yo, if you made it to the end of this video, drop a comment down below and let me know what city are you from.


Do Asians love EDM as much as white people love country Latinos love reggaeton and black people love rap Welcome everybody to the hotpot boys David We just got back from Las Vegas from our very first EDC event. We bought in we took a plane We went there to join the rest of the Asian world What do we see there? Oh the skydeck VIP zone is about 70% Asian General admission is about 25% Asian considering America is 6% Asian It's like 40% Asian. I mean, it's really over represented I thought I was in like an engineering or computer science or medical program for years on the internet people have asked the question Why do Asians love EDM festival so much? Why why why will pop up all these little questions that people have asked? Well, David, we have 10 reasons why Asians love EDM now You may think that we're complete outsiders. We've been keeping up with the scene for a while I've actually met Elenium and Marlon from the base Jackers. So you know I told him I talked to them about some of this stuff because they got a lot of Asian fans by the way So here are 10 reasons why Asians love EDM? Let us know in the comments down below which reasons apply to you and if you think we left any out Do you agree disagree guys? We're not the first people to talk about it point number one There is a historical context for Asians to like EDM because there has always been a decently large Asian rave scene someone told me Andrew that we are in AZN Raver 3.0 Wow 1.0 was in the 1990s with the pet shop boys mystic boys AZN Raver number 2.0. This was like exchange LA days Ken Lloyd And we are right now in AZN Raver 3.0 Which is Steve Aoki, but the favorite DJs like you said our Griffin, Elenium and Porta Robinson guys this is back when it was more referred to as like techno trance like the term EDM Wasn't really even used and then also it was highly highly and tightly knit with the Asian racer scene and this is when you know you had the light gloves and all these hand movements is where it came from This is there was an Asian rave scene before EDC was even an event okay before insomniac Started throwing stuff in Orlando or LA. This is this is the Asian rave I mean basically long story short I would say since the 1980s which is when like Asian Americans really started popping up like from our generation They've only been Favorited favorite of two types of music and one is EDM and one is hip-hop But I would say out of like three decades probably hip-hop got like one decade and the other two decades went to EDM And right now we are in the EDM decade. All right point number two EDM is culturally open as in you don't really have to buy into any specific culture to enjoy it And this is different than other genres of music. It does feel like sometimes other genres of music belonging I guess to other ethnic groups in America sometimes. I'm not saying for sure. It could feel a little bit like Self-glamorizing you know like when you're at a country show, it's like if you ain't a country boy Then what are you doing at the show or like at a hip-hop show? It might be like man if you're not like us Then really what are you or that at the reggaeton? They're like, hey You have to be Spanish to understand the rhythms of the like the romantic urn Yeah, I mean there's oftentimes no words to songs or our songs with words But they're usually about very relatable topics like love and being free and being positive, you know I mean, that's a good song by the way But you know, it's a very relatable topic and there's no like specific stories and slang that you have to know Right, even though a lot of EDM music is produced in like Sweden on a computer It's never like if you are Swedish on a computer you can't be here Yeah, no, it's very wide open in a way. I'd almost say it's like a blank canvas The only culture is to have peace love unity and respect plur and I do think that's been changing though Someone told me that as EDM has become hyper mainstream, especially in the AZ and raver 3.0 stage Which is right now that like everybody else has started to come in It's sort of like when the tech bros started coming in a tech and the pure like technologists are feeling like hey, man I don't know this guy from like Alpha SIG keeps like trying to like beat me up This kind of moves on to point number three Asians feel accepted here guys. We know being minorities in America There's not that many big mainstream parties that Asians feel completely accepted But I will tell you this EDC, you know, it's built into the culture to be accepting of Accepting of all types of people wearing all types of clothing. So when you're Asian there, you don't really feel like you're standing out Yeah, I think there's two types of acceptance There is consumer acceptance, which is you going to the show How do you feel and then on the back end how many Asians are getting money like points either producing the music or throwing the Events and EDM Andrew Asians are getting money Well Asians are spending money obviously as consumers, but a lot of Asians are making money as DJs whether that's like like we said You know, there's been Asian DJs DJ shadow going all the way back to Ken Lloyd to now Steve Aoki zoo The names are like sort of endless. Yeah, I mean, I would even say comparing it to an event like Coachella Coachella is much more about being cool putting on your best fit You want to go viral for your outfit, but EDC is like even if you don't have a good outfit No one's like bugging out. No one's gonna like look at you be like, oh, yeah, you're scrub You know, it's just not a judgmental space to be honest and also one last criticism that some people have said Some people ask the question that do Asians like EDC because they feel accepted there, but accepted by white people I don't know because it's mostly still a white event actually at the majority of it Oh, no for sure. I mean, um Like has gone through a lot of phases and people perceive EDM to be a upper middle-class white music genre Yeah, but particularly for progressive like open-minded middle-class, right number four all types of Asians go to EDM festivals Now I'm talking about everything from Asian thugs to Asians frats and sororities You're talking about Asian medical students Asian engineers to Asian CEO tech founders, right? You talking about geek money to street money They got everything in between I think of the different groups that you see at EDM festivals, but mostly that's to be honest just mostly white and Asian from what I've seen Uh, I would say the Asians have like every single archetype of Asian Whereas when I see the whites at EDM shows they tend to be more like one or two different types But if I examine the Asians, it's like they got all like 20 days. David. We're at EDC You know, we did happen to have access to the skydeck VIP area and let me tell you this There was like shirtless Asian thugs like tatted up from head to toe and they were just like just loving the music So and there was the table across was like some CEO tech founders some crypto kids and just all All different types of backgrounds guys Maybe it's an event not just to bring all people together, but all Asians And I think that once that in AZ and Raver 3.0 like we're talking about the three different segments Once it got super mainstream at some point the snowball just keeps on rolling No, and and other Asians who are not really the EDM like us We just end up going because we're just like all Asians are going Yeah, also, I do think that to the point of Asians either loving hip-hop, which was mostly from 2002 to 2012 But a lot of those people that were hip-hop producers or rappers if they wanted to stay in the music industry Andrew They actually switched over to EDM to get money whether they're like producing the shows or making the beats The reason that that's relevant Andrew is because me and you loving hip-hop hip-hop and EDM are not Oppositionally to each other. They're sort of like cousins There's artists and or like a Yuletron or Waka flaka who made the jump from the hip-hop world to the EDM world point number five It is an escape from what is often otherwise a stressful and compressed Asian life I mean listen if you talk to anybody who discovered EDM festivals and felt accepted there They almost are like it was just so freeing like I just I kind of dropped everything I didn't have to think about my Overbearing parents and I didn't have to think about this and that and it was just an escape people like escapes And let me tell you this it is a different world when you go to these festivals Especially EDC the way they build it up and the music and the looks and everything It's just like you're almost in a dreamland. Yeah, and I don't think it's like for everybody. Some people They're just like, you know, it's just another reason to party. I've been partying my whole life But you're right There is a segment of people specifically probably East Asian with like very high expectation Tiger parents who's going as like almost this Like party 101, you know in addition to their like school syllabus and they're trying to get an A Point number six for some Asians and some people in general It feels like a spiritual moment and especially for those who are maybe not very religious now I mean, I think if you've ever met anybody that has really discovered EDM And maybe they were on the substances as well, but they were like, oh my gosh I felt free. I just opened up to the music and it was just like a spiritual moment for myself And maybe I feel better about myself. Maybe it helped with depression or whatever it was But like it definitely sounded like they had they found God at EDC. No for sure I mean, I think it's like scientifically proven whether it's like the BPM rate or the heart syncopation with your heartbeat Different things. It's like Andrew I saw this quote in this article where somebody said, you know, this EDM stage brought me closer to God Than any book ever has. Whoa. Yeah, I mean, it's possible guys again, you know music I do think it depends on your prior like religious upbringing or exposure Yeah, I do think like for example, like perhaps if you grew up at a you know, African-American Baptist Church where every Sunday You're already up singing and you're moving along with the choir and stuff like that, you know And you have that as part of your life. Maybe you don't need EDM music as much to get up off your feet No, you probably would prefer to be at Kanye Sunday service, right? Right? I mean, maybe you know, I mean, I'm just making generalizations But guys point number seven EDM DJs have very relatable images that I think is very appealing to Asians Right spent a lot of time in front of the computer usually like prep school backgrounds.  No rap sheets for the most part not like, uh, you know It's not like other genres could could potentially get kind of crazy I think that that's why people like them too, but you know rock stars wrecking hotel rooms or rappers getting shot Yeah, overall EDM DJs are often guys who even used to work like as engineers or doing something with the computer And then they got into producing music and then, you know, some of them even have like a anime background for example So guys, Porta Robinson and a Lenny and big anime fans. Yeah I've heard Asian guys time after time be like, hey, man, I think I could be an EDM DJ. That looks lit I might have to see how many ABG's are there. I wish I was it. I'm just kidding. David What if instead of being in a rap, we were just in the EDM this whole time. We don't pick the wrong genre Hey, headlining, you know, kinetic field fun, bro. Hey, and we bought the wrong stock Point number eight you can dress Very revealing and sexy without being judged. Also, you could partake in a number of different Substances and not be judged.  Well, this is a great time Just take off your shirt and no one's even gonna judge you it makes perfect sense even with women as well Obviously, you want to dress very sexy without the connotation that you're gonna be harassed not saying none of that stuff happens But it probably doesn't happen as often as you know, considering how many people are there But like yes, the whole idea is that you can walk around and you have space to vibe out and people aren't gonna like No, it is a safe space I mean, I think that that's what their general rule is It's like we want to provide a safe space for you to have a fantastic galactic experience But remove the downside risk of you know, potentially what could happen in high-risk exposure environments point number nine It is one of those few events in the world that Asians feel comfortable Mobbing to in large groups. We're talking about what's aptex groups of like 20 30 people who are going to EDC, right? And whether you can meet up with each other because it's a logistical nightmare, but like they just it's it's an easy buy-in Asians are like Hey, we're all going let's go and other Asians are like, all right, I'm in You know what's funny and I was doing research for this article in 2015 There was kind of a controversy in the EDM world at least in America where people were complaining about Asian trains Which is so almost like a frat stroll But with just a group of friends that doesn't want to lose each other So some people were saying like they were getting really mad at that but Andrea 2022 now it doesn't seem like it's a big issue anymore. These articles were from 2015 I know what you're talking to do because Asians, you know, especially for all the reasons listed They're gonna go there as a group and feel comfortable each other They want to link together so they kind of make these long snakes that kind of cut through the crowd And basically if you're a person in the crowd, you have to like move. Let me tell you this I know that it's it's big because Andrew There is a subtle Asian ravers group on Facebook with like 120,000 members and that's pretty much just America and Canada Yeah, I think it really comes down to Asians really seeking safe spaces and and EDC is one of the more wild Still safe. No, it's lit and it's safe and the how often you find those two things juxtaposed and layered together Yeah, if I'm it's lit and it's safe Asians are gonna be there and point number 10 Asians have embraced EDM because they don't necessarily have their own form of music like we said earlier And it seems like a lot of us especially obviously southern white people. They tend to gravitate towards Country music northern white people. They tend to gravitate towards rock music African-Americans gravitate towards hip-hop Latinos gravitate towards reggaeton. I'm obviously these are like They're not really there. This is just like the main group that consumes it or desi people You can ask any desi American Indian American and they're like, oh, I listen to some bongra At least I'm familiar with it. Which is funny enough Jay Sean was at EDC I'm not saying Jay Sean is bongra, but he did have some bongra influences in his earlier albums But I think you know and shout out to K-pop we have K-pop, but it doesn't use a lot of necessarily like traditional Asian Elements, right? So I think when it comes to music that is specifically infused with Asian elements There's not really a pop one right now. Now. There are some songs here They're from J-Chile Wangli home that had the goot on the Artists from Japan and Korea and Vietnam But for the most part the vast majority of music consumed even in language in those countries Doesn't have a lot of Asian instruments because the West has sort of determined what is modern music by using their drum kids and their Guitars and things like that. Yeah. Yeah, and I do feel like Indians were the one like Asian group that has deeply infused their traditional music and I'd actually just heard like a like EDM dance song that was mixed with traditional Indian music would play like five seconds of it right now You know what I'd like to see I think that we generally think that Asian culture doesn't have a lot of like rhythm and drums in it But we have taiko drums and we have the drums that you use for for Chinese New Year the You know for the lion dance, so I don't know if people could somehow incorporate those those would still count as Asian elements In my opinion and Lenny M and Porter could always one I'd like to see how they would flip it as outsiders. I have a bonus point I'm not gonna spend a lot of time on this but EDM trance house techno are really big in Asia as well And it's partially because Asia has probably interface more with Europe or interface with Europe earlier on then it did with American culture and but also if you go to any club in Asia like any club in any big city in Asia For the most part they're gonna play mostly EDM techno house stuff like dude It is super common and I remember growing up at church There was like somebody else our church that was really into the JDM scene They were listening to techno and trance to pock remixes in the year like 2005 Like literally this is oh five pock died in 95 and they were playing techno to pock. Let me pop up some videos of Shuffling in China because people love shuffling in China I do think it also goes down to the electronic music or the midi music of even games like chrono trigger final fantasy Kingdom Hearts, etc. I do think there's some tie-in with anime RPGs as well as even the blade soundtrack and or that was the first time I got Exposed to that like deep house trance, you know from Europe that Actually and for me my biggest takeaway is that it's just something that fits with Asians even though it's not inherently Asian There's nothing inherently Asian about computer science. There's nothing inherently Asian about medicine That's been like a worldwide thing, right? It's just like numbers and stuff like that But for whatever reason Asians really gravitate towards it in like disproportionate numbers. Yeah, yeah I mean, I think the question is like does the EDM help Asians find a release and find their voice or does it just help Asians feel? Like they fit in like everybody else. I don't know guys. These are just bigger questions I'll leave it at that and let us know what you thought about our list in the comments down below. There's more ABG AZNs at EDM's than their ABGs at KTVs. Oh Yeah, also be another factor. I forgot to mention. All right, everybody. Thank you so much for watching We are the hot pop boys and until next time we out peace


Hello well hello folks I'm Philip Magnus and this is rather a short video since I did my permafrost review which was for the record not the review permafrost uh novella by alistair reynolds the much beloved all truth sci-fi since it did so beautifully badly I thought why not hope that lightning strikes twice and I get another 17 views so naturally I had to do another review of a novella by alistair reynolds again very short video because I only had so much to say so let's get to the reviewing shall we another fast-paced novella courtesy of alistair reynolds slow bullets makes for one of those reads you can't put down after reading the first scene in the library where I picked this title up I sat down in the evening and didn't stop reading until there was no more slow bullets left to read whereas permafrost the first of the alistair reynolds novellas I read was driven by the force of its science-fictional idea the impetus for me here for my interest in this one was absolutely 100% the characters in particular main characters cur is a soldier fighting in a war she doesn't believe in it's a war she wasn't even supposed to be in and when an incident within a transport vessel sees her sent far away from home she's not too thrilled about it the cherry on top the war criminal who captured her in the final days of the war after a ceasefire in fact is also on board hint hint here's a war criminal at least in part over the kind of fucked up horrors he did to her he's not even her biggest worry however by the end of circumstance it is up to scur to make sure the nearly thousand people on the ship civilians as well as soldiers war criminals and what have you from the two sides of this massive bygone war don't kill each other so yeah she's got a lot to deal with and all of that before they have so much as figured out what has gone wrong with the ship where everyone's ended up and what terrible tragedy the lack of any man-made cosmic noise bodes for interstellar human civilization the greatest strength that reynolds shows in slow bullets itob is his doubt wielding of elements of uncertainty he injects lines of dialogue with subtle double meaning that some readers might very well miss only to recall them after a number of conjectures are presented in such a way as to make you doubt everything you've believed for a character or a set of characters what makes this novel so special and probably one of the reasons it won the locus of war in 2016 when you tear it down to its bare bones is that you have a human story whose resolution speaks to the best of who we can be something that inspires in something to aspire to i love my time with slow bullets and i i'm absolutely enthralled by alistair annals writing i'm currently making my way through revelation space which is the first in his most celebrated sci-fi series and there are definitely elements that i recognized from slow bullets in that book as well i will keep talking about him even if no one ever watches another one of my alistair annals sent to the reviews ever in the world if ever because they have fun they're amazing books and i think that if you enjoy something like mass effect revelation space for example is such a perfect book for you but hey i'll tell you about it some other time if you enjoy this video please share it with your friends like it and press that subscribe button i'll see you next time bye


So Guillaume is a developer at the SOS Media Lab in Paris and the ideation, the web-based firm. Also, I developed the first version of SigmaJS and just to correct you, you can see it right here. Guillaume is actually the main maintainer of Sigma today and our strategy is kind of, if we have no $10 rep library kind of a huge problem because we have more and more use cases that other people wanted to build through the web graph analysis. We use cases like with session network analysis, the reasons, page runs, et cetera, and even sometimes we'd like to have like in Node.js, which is more and more used, a tool like network is called Python or boosts, but there's nothing today. All we have today is some graph rendering and giants which have their own profiles and algorithm implementations, like in my NCA stage. There is two ports of network in Node.js. Graph are actually both squatted and NPM. So we cannot create anything that's called graph with lower case or a ver case G. So the problem is that in the state of the art, and I know, yes, we have like some, both are really layout, so things like this implemented in Sigma, but it's absolutely not usable in anything else than in the web page. And it's a problem for data page, I guess. And when it's too much time to render it, it's only for the web, but it cannot be used as standard SNA library. And yeah, for the SNA algorithm, I do more in the state. I take the quite standard JP workflow. When I have a social network, what do I want to do to create a network map? First stage, we're going to be able to compute some metrics like Python, or Geats, or any centrality score for my nodes, and map to map the results to that site. Then we search for communities, and we map the explorers to the communities.  And we have Sigma kind of covered the part of this, only if you run it with or under it. It's not possible to use this in the JS. There are some local solutions, like, I know there's a page wrong, but not because I run models in NPN, but none of them are bound to a new app model, the same bar hits in NPN. About the communities, there's like two kind of loophole applications on NPN, but none of them are quite, and some graph rendering have their own. So if you go to the site, you have the links. And for the project, it's quite worse, because it's really only tied to graph rendering, and we have Sigma has closed at last two, which is also developed for some other rendering library, I guess. There's a lot of string implementations for D3, Cyclocay, Petra, and I have seen some string modules, again, really different. So if I want to use some of these implementations that proven, I have to switch with the original CTIs all the time, and it's quite painful. So basically, it's all SNA algorithm, it's all SNA process is really painful to do for any industrialization, are you doing it? So are we doing it? Okay, so I hope it's fine. So we certainly hope not, and so what we propose here to you today is actually with something which we called Graphology, because we had to find a name, because NPM is a wild place, and when someone takes a name, you can't take it back. So we just used a lame pun, and this is it, Graphology. So Graphology, what is it? It is a specification for a robust and multipurpose graph object in JavaScript. So what does it mean, really? So yeah, this is it. So this is a specification, not a library, but you have a reference library, which is the reference implementation of this specification, which you can download and use. And you have also a standard library, which comes attached to it, which contains a lot of classical algorithms. So you've got layouts, you've got generations, you've got its, et cetera, et cetera. So this specification is meant to be multipurpose. So we are not targeting one specific kind of graph. We are targeting a lot of graphs, so the graph can be directed, can be undirected, it can be mixed, which is probably some pervert thing when you want to have directed and undirected edges. And the graph can be simple, so A to B is only one, or you can have a multiple graph, which is A to B plus A to B plus A to B, we don't care. And the graph will or will not accept self-loops. We don't have an opinion on this, we let the user decide. So we have a lot of use cases for this kind of library. We have graph analysis, if you want to compute metrics or a whole indices about your graph. If you want to perform graph on linked as, like you want to build specific graphs like bipartite graph from data or modify something which already exists, et cetera, et cetera, or maybe interface with some databases like Neo4j or Titan or so on. And like you have also a data model for rendering, which means that graphology is actually suitable for rendering libraries as a graph model, because it has like a lot of events and you can listen to mutations on the graph and so on. We will see that later. So what we won't do is handle graph data that does not fit in RAM. We are doing like the weakman thing. So we just like take graphs, hold them in RAM and that's all. If your graph is like 14 gigabytes, it's not all work. And so I want to stress that this is a specification. Here we are building, it's not a library. So this means actually the following things is that, I'm sure you will agree here that there is not a perfect way to implement graphs data. So you can't really do it. So there are implementations that will cover more use cases than others. And you can aggressively optimize an implementation to work on some really specific use cases. So with a specification, what we have is that anybody can implement the specification, however it fits, and it will use its, or their implementation, but they will still like have the benefit of the standard library and be able to use like all the ecosystem of libraries which use this specification without having to record them and again and again and again. So for instance here, you've got an example. You've got a graph, which is actually an implementation of graphology, which is my custom graphology implementation, which is why not build upon say plus plus for not JS. And here you've got something which is a library from graphology, which is the function which is able to extract the connected components. And so these functions will still work on your particular implementation of the graph because yeah, it's the same API, so no biggie here. So that's why we have a specification and not a library. So what are the main concepts of this specification? It's really simple, you've got nodes and nodes are represented by keys and those nodes may be described by several attributes which are like key value, key value and so on and so on. And an edge is represented by a key that may be provided or not because the graph is able to generate the IDs and you'll see why later. But can also be represented by attributes. So you've got nodes, key attributes, edges, key, source, target attributes. So that's a graph, I guess. And that's all. So for instance here, you've got like an example of the code if you like load the reference implementation of the specification. So you are going to like build the graph and you add nodes to it and then you add one really interesting edge and then you add a really interesting attribute to the Susie node. And you've got a miscellaneous information like the order of the graph, so two obviously. And you can like iterate on the nodes, you can iterate on the one nodes neighbor and so on and so on. It's pretty boring actually, it's just a great API basically. And so this is the current state of the standard library for instance. So this will grow. You've got like assertion, centrality metrics, components, detection, generators, like if you want to generate a random graph or an L-dose-reney graph. You've got hits, you've got layouts, you've got four, eight less two layouts, you've got operators and new utilities and so on and so on and so on. So you see the thing. So what we want to speak about here is more about like API design. So because when we intended to implement a specification, we were like a bit like a bit befuddled by the whole diversity of graph library that exists and how we were going to like implement it, what would be the semantics of the library, how are we going to like add a node, add an edge, et cetera, et cetera. And there are a lot of ways to do so. So we want to show with you what the choice, what were the choice we made and how we came upon the API we've got today. And what kind of issues we had also and how we solved them or I hope we solved them. So first of all, we're in JavaScript and so JavaScript is not Java.  So obviously we don't have classes for nodes and edges. So this means that there is only the graph which is actually an instance of a class. And so you don't have things like this like your const node is gl equals new node. No, you don't like get node instances from the graph by adding a node or something. So basically this means that the node is just a key and some attributes and that's it. So if you want to ask questions about the graph or about the structure, you will use keys, both for nodes and both for edges, that's all. So the other issues we had were concerning like the default graph type. So because a graph can be a lot of things, can be mixed, can be directed, simple, multi, we had to make a choice and tell you like what is the default graph? And so we made a choice and we decided like the graph is mixed by default because most of the developers actually don't want to make the choice because this question doesn't interest them at all. So by default, the graph is mixed. So you can add directed edges and directed edges also and that's not a problem. But by default, the graph is simple. So you can't add multi edges. So you would just like create a graph and this is actually the same thing as saying that my graph is mixed and my graph is not multiple. Okay, so this means some things. Like this means that usually when you build a graph implementation, it's kind of useful to know whether the graph is directed or not because you can optimize the implementation because you won't implement an underrated graph the same way you would with a multiple directed and directed graph and so on. So if you don't want to choose, yeah, don't choose the implementation will work. But if you want to choose because you know it, you can use like type constructors to do so and the implementation will be able to optimize itself because it has information now basically. So if you don't want to choose, you don't choose, but if you know, just state and the optimization will be possible to be around. So here for instance, we are going to instantiate a multi-directed graph which has exactly the same API as any other graph of the library. So there are no like difference in the semantics of the API. For instance, in network X, if you build a directed graph, you won't have the exact same API as you would be with the undirected graph. So here you have the exact same methods everywhere. So this means that we have to rely on some useful error messages and hints.  So here you have it. So we add some nodes, we add an edge, we add the same edge. The graph will tell you that you can't really do that. You know, it's a simple graph. So if you want to have a multi-graph, maybe you should like use a multi-graph. So this way we both have the benefits of having like a standardized API for all types and like being able to explain really gently to the user that is making some mistakes. Okay, so the other problem we had was concerning like the edge keys. So it might not seem a problem because usually you don't use keys because the keys is just like the source to the target. But when you have multi-edges or multi-graphs, you have the problem of being able to target a really specific edge and you can't do it if you just have the source in the target because you have to be able to like loop on the edges to find the one you want and this is a bit silly. So here we told ourselves we are going to use keys for edges because this is quite useful and you can target really specific edges. But the thing is, and we learned this the hard way on Sigma is that it's really boring as shit to ask your user to like invent keys for things which don't have a key specifically. Like in a simple graph, you don't want to tell your user, okay, like take your counter and increment it each time you add an edge. So you will have a unique ID. This is really a pain. So at the beginning, we told, okay, we are going to like have a method which is add edge, a key, a source and a target and some attributes. And we are going to have like a method which would be graph.aid, add edge without a key and we have thrust and target and attribute but this was like really boring. So we went the other way and tell ourselves, so if you had an edge, the graph will generate the ID for you and the key for you. And if you want to explicitly provide a key for the edge, just do it with this one, which is add edge with key. So like the really common case is eased and the hard case is like swept away. But this means that you have to generate a key and actually it's not a really easy task because like incremental ideas are really shitty because if you merge two graphs, you will have like some issues like, I already have the one edges and you have also the one edge but they are not the same, how do you do? So you have to find a clever way to do so. So we went with the easy way, which is UID. And in the current implementation, actually the edges are processed, the edge keys are generated likewise. So we generate a UID V4 and then we compressed it in base 62 to reduce the amount of RAM used. And the really neat trick with base 62 is that you can double click on the thing and copy it really easily. Whereas in base 64, you have like iPhones and underscores and shitty things like that. Yeah, you can double click and it's a pain. So this is the most crucial point of the implementation. So what about adding and merging nodes for instance? It could be edges also but I'm going to speak about nodes in this example. So what does it mean exactly? So when you add a node, which is John and you add the same node again, what should happen? Like for instance, in NetworkX, if you do so, it works like a set.  But here we've got a little bit of a problem which is we also have attributes.  So NetworkX actually applies some magic on there and you will say, okay, I'm going to not add the node but I'm going to merge the attributes. So this was a bit magical too, magical for us. So we decided upon something which is a bit different which is you're going to add the node. If you add the node twice, we're going to yell at you by saying you that you do something which is really silly and this is actually quite useful because for instance, when you serialize data and you process this data and you like notice that you have twice the same nodes whereas you should not have it. It's quite useful to have an error rather than just silently do nothing. And so if you want to explicitly merge something, you are going to use merging methods like the merge node methods which actually will not add a node, will not yell if the node is already existing and will merge the attributes as you would expect the method to do. So instead of like doing some magic we chose to yell at the user and tell him to do some things explicitly rather than implicitly. So what is a key in the graph? So this one was a bit long to solve but I'm going to do like a bit faster because we're running out of time. So what should be a key? Like for in the Turkish for instance, you can have anything as a key. So a key can be a reference, a key can be a string, et cetera, et cetera. So here we chose like to be more like the JavaScript way for multiple reasons. So only a string can be a key. So if you pass like an integer, it will be coarsed and cast into a key like an object would do. Why do we do that? Because it's more JavaScripting. It's really easy to serialize because serializing an object is like a pain. And that's mostly it. And so to, yeah, that's it. So the other problem we had was that we needed events because we might use this library in a rendering context and we might be interested by some really focused informations about for instance, this node was updated and the color of this node was updated. This is important for two reasons, rendering and like keeping indices synchronized. So we have events. And so because we have events, we obviously need to have like some setters and getters because otherwise we are not able to know something was mutated. So it's not Java, but it's a little bit Java anyway. So you want to attribute, get node attributes. You pass the node key, the name of the attribute, you got it. You want the attributes, just do that. You want to set an attribute, the same thing, et cetera, et cetera.   It's silly. So we went with an OOFP approach, object-oriented functional programming, which is update the node attribute and just pass some functions to apply the change. And this means actually as a cool side effects, simpler iteration semantics because at the beginning we were cushioning ourselves about like if you iterate on the node, what should we provide to your users? The node key plus the attributes plus some other informations. But it was a bit strange and hard to grasp. So we just said, okay, you'll just have the keys and then you'll ask the graph for other information if you need it. So you save up some memory, you save up some semantics and that's a bit better, I guess. And so the last point we tackled during the design of the API was another information, which is what should we do with labels, weights and so on because the graph theory is full of those kind of special attributes. And so because the graph theory fosters an environment where you have really variation about a common typology, like you would say a node or a vertex or something, we just told okay, there are attributes like any other and that's all you have. And so all the library is made while thinking about this and if you want to call your weights with a shitty name, you can just provide a configuration and you should be okay. So this leads us to like how did we implement the reference library? So how did we implement the specifications so in JavaScript for anyone to use the reference implementation that you can download and use by doing NPM installed graphology. And so the main issues we had was concerning like constant time versus memory because we don't really know what the users are going to do with the graph. We can't really aggressively optimize for some use case. So we decided we are going to like support everything in constant time. So this means if you had a node, constant time. Delete a node, constant time. You want to like find if an edge exists, constant time. So this means we have like some memory overhead to be able to provide this kind of fast operations. And so the actual data structure is likewise. We have two maps which we're introducing in ES6 which are going to store like a node index key value and an edge key value index. And we have a lazy indexation of neighbors which means that we won't build like the information of the neighbors if we don't need it. So the node maps will store this kind of things like degrees, attribute data and a lazy neighborhood indexation. So this means that if you have to check like this is my neighbors, it will compute the index and then you'll have it but not on the first time. And so this, the index of neighbors look like this. So it's actually sparse matrix. It's a really simple sparse matrix. So you've got like the node A has got like out neighbors which are B and C and so on. And you've got a set of the edges which are related to the path A to B, et cetera. And the only optimization we run is that like this set is actually the same reference as this set. So it means that A out B is actually the same as B in A. And so the edge map is quite similar. You've got like the source, the target, the directedness and some attribute data. And so I'm sure that someone can find something better. So please bash me and help me, you'll find something a bit like interesting. And so the last issue we will tackle is like the cases of undirected edges. How do you store them? So in memory, we just like to keep an implicit direction. So if you say at edge A, B, we will store like undirected in A undirected out B. And if you say like B, A, it will change the internal representation in memory of the edges. So with two equivalent graphs may have different memory representation. And for some people, it seems to be an issue. So I want to have feedback on that. And so should we sort the source and target keys? Should we ask them? I don't know. I really don't know. So please bash me again. And if you want to have some precision on the implementation, please do read the code. Everything is open source and everything is accessible and you can contribute. Yeah, so the future roadmap now really quickly. Yeah, Sigma, we will really develop a fully Sigma without a graph model, which is kind of good news for us. And with a really smaller, specific functional scope, which is just doing rendering management and interaction management, which is really nicer for me. So no more, yeah, I need to implement the page rank to render graphs, which is kind of nonsense for, we will have graphology to end all that. And some just quick note community notes. Since Guillaume is actually more maintaining it than I do, we'll try to adopt a more community workflow with an actual roadmap, put this on a GitHub organization and try to have more frequent updates, actually. And so for like future ideas, should we try to support iPod graphs? Does someone need it? Does someone need an imageable immutable version? Like it's easy to write using immutable JS or Mori. We would like to have like type script definitions and so on because it's all the rage right now because like static types, yeah. And thank you. So this is all a work in progress. So please bash us and help us like achieve a more useful tool. Yeah, thank you. Yeah. What was the biggest graph you tried to build? Sorry, I can't hear you. What was the biggest graph that you were used to test it? Yeah, last time I checked I had a graph with like one billion note, but not really representative because it did not have a lot of attributes data. So, but it will like store a lot of data, but not more than you can store in a map in node JS, for instance. So it will like run a memory quite easily because of node and things. Actually it could be like the object of a customer implementation because it could be like quite easy to do, but not for the reference implementation. But if like you can't implement the specification without being able to like implement your own compression then we failed. And so maybe we failed, but I think you can do it. What? Yeah. Can you speak louder? What's about the layouts of the graphs? If I want to render with the force of it, the output of the SQL layout. Yeah, so there is a stub of library which does those kind of layouts. So the rendering is like a different question which will be under like with other libraries like Sigma JS and so on, but for the layout like for now the implement into what I like to run.


Hello, this is Laptop Media, and today, we will show you how to open the Asus ROG Strix SCAR 17G732 and what's inside of it. 11 Philips head screws are holding the bottom panel in place. Ultimately, the one at the bottom right corner remains attached to the plate and lifts it slightly, so you can start prying from there. Then, before you completely remove the panel, lift it gently and unplug the LED ribbon cables from the motherboard. Please remember, it would be of great help to us if you just hit the like button and subscribe to our channel. That would motivate us to make even more and better videos for you. In terms of cooling, we have 7 heat pipes, and they cool, the CPU, the GPU, all VRMs, and the graphics memory. Not bad, whatsoever. Upgradability wise, there are 2 RAM Sodom slots, that should be able to fit up to 64GB of DDR4 memory. Also, there are as many as 3 M.2 PCI-EX4 slots with RAID 0 support. And here, the battery is a relatively small 66Wh unit. If you'd like to see more disassembly videos of the latest notebooks we would highly appreciate if you hit the like button and subscribe to the channel.


Live from Las Vegas, it's theCUBE, covering NetApp Insight 2017, brought to you by NetApps. Hello everyone, welcome back to our live coverage, exclusive coverage at NetApp Insight 2017. It's theCUBE's coverage. I'm John Furrier, co-founder of SiliconANGLE Media with my co-host Keith Townsend at CTO Advisor. Our next two guests is Gabe Chapman, senior manager NetApp HCI and Sydney Sonia, who's the IT Consulate at 4th and Bailey, also a member of the A team, a highly regarded top credentialed expert. Welcome to theCUBE guys, see you. Thank you. Thanks for having us. Pleasure to be here. So I love the shirt by the way, great logo, good font, good comes up great on camera. Thank you. We're talking about the rise of the cloud and everything in between, kind of the segment. As a NetApp, A team member and customer. It's here, cloud's here. Yes. But it's not yet baked in the minds of the enterprises because they got to, there's a path to get there. So there's public cloud going on, hybrid clouds, everyone gets that. There's a lot of work to do at home inside the data center. Yes there is, there's an extreme amount of work. And like you said, these are very exciting times because we have a blend of all of the technologies and being at an event like this allows us to look at those technologies, look at that fabric, look at that platform and how we can merge all of those things into an arena that can allow any customer to dynamically move on-prem, off-prem, public cloud, private cloud, but still be able to manage and securely keep all their data in one specific place. Gabe, I want to get your thoughts because he brings up a good point. Architecture's king, this is the cloud architect. DevOps has gone mainstream. Pretty much we all kind of can look at that and say, okay, QED done, everyone else put their plans together. But the enterprises and the folks doing cloud, cloud service providers and everyone else, they have issues and their plates are full. They have an application development mandate, get more developers, new kinds of developers, retraining, replatforming, new onboarding, open sources booming, they have security departments that are unbundling from IT in a way, getting fully staffed, reporting to the board of directors, top security challenges, data coverings, and then over the top is IoT, industrial IoT, man, their plates full. So architecture is huge and there's a lot of unknown things going on that need to be automated, so it's a real challenge for architects. What's your thoughts? My thoughts about that is I like to make this joke that there's no book called the joy of menial tasks and there are so many of those menial tasks that we do on a day in and day out basis in terms of the enterprise, whether it's storage, whether it's virtualization, whether it's whatever it is, right? And I think we've seen this massive shift towards automation and orchestration and fundamentally the technologies that we're provisioning today, APIs are king and they're going to be kind of the focal point as we move forward. Everything has to have some form of API in it. We have to be making a shift in transition towards infrastructure as code. At the end of the day, the hardware has relevance, it still does, it always will, but the reality is to extract away the need for that relevance and make it as simple as possible. That's where we have things like hyper-converged infrastructure being so at the forefront for so many organizations, NetApp making a foray into this space as well, is to push to simplify as much as possible the day-to-day minutia and the infrastructure provisioning and then transition those resources over towards getting those next generation data center applications up running and functional. Old adage that's been in the industry around making things simple as our company's like an aircraft carrier, but when you go below the water lines, everyone in little canoes paddling, bumping into each other, these silos, if you will. And this is really the dynamic around cloud architecture is where the operating model's changing, right? So you got to be prepared to handle things differently. And the storage in the old days is almost as easy, but you guys made it easy, a lot of great customers, NetApp has a long history of it, but it's not the storage anymore, it's the data fabric as you guys are talking about, it's the developer enablement. It's getting these customers to drive for themselves and it's not about the engine anymore, although you got to have a good engine, call it tech, hardware, software together, but the ultimate outcomes of people driving the solutions are app guys. They're just the lines of businesses are under huge pressure and huge need. I think you look at it this way, it's like, you know, we're kind of data-driven and you'll see Gene talk about that as part of our messaging. We can no longer be just a storage company, we need to be a data company and a data management organization as we start to have those conversations. Yes, you're still going to go in there and talk to the storage administrations and storage teams, but there are 95% of the other people inside the enterprise, inside information technology, with different lines of business, they're the ones that we have the most relevant discussions with. That's where our message probably resonates more strongly in the data-driven aspect of the management or analytics and all those other spaces. And I think that's the white space and growth area potential for NetApp is the fact that we can go in there and have very authoritative discussions with customers around their data needs and understanding governance. You have things like GPRD and Amia. That's a giant open ecosystem for it has so many requirements and restrictions around it and everybody's just now starting to wrap their head around it. So building a programmer on something like that as well. So there's challenges for everybody and there's even challenges for vendors like ourselves because we were mode one, now we're mode two. So it's kind of like making that transition. And the old speeds and feeds, we're always diligent. Hey, how fast can you go? What's this files look like? A verification, blah, blah, blah. Now you've got solid state storage, you've got solid fire. Now people want outcomes as a service, not outcomes anymore like a cliche. Things are happening very dynamically and last week at Big Data NYCR event around the big data world, you couldn't get any more clear that there's no more room for hype. They want real solutions now, real time is critical. And watching the keynotes here at NetApp, it's not speeds and feeds, although there's a lot of work going on on the under the hood. It's really about competitive advantage. You're hearing words like data as a competitive advantage. Yeah, Sydney, you're in the field, you're in the front lines. Makes sense of this. The sense that we have to make is made up some great points. Getting the business engaged is one thing because you still, with the cloud and the cloud architecture, you still have a lot of individuals who are not necessarily sold on it all the way. So even from a technical perspective, so those guys that are down in the bottom of the boat as so to speak, you still have to kind of convince them because they feel somewhat uncomfortable about it. They have not all the way accepted it, the business has kind of accepted it in pockets. So having been on the customer side and then going to more of a consulting side of things, you understand those pain points. So by getting those businesses engaged and then also engaging those guys to say, listen, it's freeing the relevance of cloud architecture is not to eliminate a position, it's more to move the mundane task that you were more accustomed to using and move you closer to the business so that you can be more effective and feel more of a participant and have more value in that business. So that's- So it's creating a value role for the non-differentiated tasks that were being mundane tasks as you call them. You can then put that person now on whether analytics or- Are those IOT things like you were mentioning on those advanced projects and use and leverage the dynamic capability of the cloud being able to go off-prem or on-prem. So what's the guiding principle for a cloud architect? Love to get your thoughts on this because we talked about in a segment earlier with Josh around, a good dev-ass person sees automation opportunities and they jump on it, like a grenade. There it is, take care of that business and automate it. How do you know what to automate? How do you architect around the notion of we might be continually automating things to shift the people and the process to the value? I think it boils down to is the good cloud architect looks and sees where there are redundancies, things that can be eliminated, things that can be minimized and sees where complexity is and focuses to simplify it as much of it as possible. So my goal has always been to abstract away the complexity, understand that it's there and have the requirements and the teams that can functionally build those things but then make it look to you as if it was your iPhone, right? I don't know how the app store works. I just download the apps and use it. A good cloud architect does the same thing for their customers internally and externally as well. So where does NetApp fit in there from a product perspective? As a cloud architect, you're always wondering what should I build versus what should I buy? When I look at the open source projects out there, I see a ton of them. Should I go out and dive head deep into one of these projects? Should I look towards a vendor like NetApp to bring to bear that simplified version? Where is the delineation for those? So the way we see it is traditionally is there's kind of four consumption models that exist. There's an as a service model or just in time model. There are, we see converge and hyperconverge as a consumption continuum that people leverage and utilize. There are best of breed solutions because if I want an object store, I want an object store and I want it to do exactly what it does, that's an engineered solution. But then there's the as a service, I'm sorry, there's a software defined component as well. And those are kind of the four areas. If you look at the NetApp product lines, we have an on tap set of products and we have an element OS set of products and we have solutions that fit into each one of those consumption continuums based on what the customer's characteristics are like. You may have a customer that likes configurability so they would look at a traditional flex pod with a FAS and say that that's a great idea for me for in terms of provisioning infrastructure. You may get other customers that are looking at I want the next generation data center, I want to provide block storage as a service so they would look at something like solid fire. Or you have the generalist team that looks at simplicity as a key running factor and time to value and they look at hyperconverge infrastructure. So there's a whole bosses. For me, when I have a conversation with a customer around build versus buy, I want to understand why they would like to build it versus buy it. Because I think that a lot of times people think, oh, I just download the software and I put it on a box. I'm like, well, right, that's awesome. Now you're in the supply chain management business. Is that your core competency? Because I don't think it is, right? And so there's a whole bunch of things like firmware management and all these things that we abstract away all of that complexity. And that's the reason we charge up for our product is the fact that we do all that heavy lifting for the customer, we provide them with an engineered solution. I saw a lot of that when we really focused significantly on the open stack space where we would come up and compete against SEF. And I'm like, well, how many engineers do you want to dedicate to keeping SEF up and running? I could give you a turnkey solution for a price premium, but you will never have to dedicate any engineers to it. So that's the trade off. So on that point, I want to just follow up on a follow up to that is you mentioned open stack, which big fans of, as you know, we love open stack in the beginning. The challenge with Hadoop and open stack early on, although they've kind of solved them, industries evolve, is that the early stages was a total cost of ownership problem, which means that you had the early tire kickers, early pioneers doing the work and they iterated through it. So the question around modernization, which came up as a theme here, what are some modernization practices that I could take as a potential customer or customer of NetApp, whether I'm an existing customer or a future customer? I want to modernize, but I want to manage cost of ownership, and I want to have an architect that's going to allow me to manage my data for that competitive advantage. So I want the headroom of knowing that, it's not just about putting a data lake out there. I got to make data real-time and I don't know when and where it's going to be available so I need kind of like a fabric or a layer, but I got to have a modern infrastructure. What do I do? What's the playbook? So that's where that data fabric again comes in. Just like one of the key notes we heard earlier in the general recession yesterday, we have customers now who are interested in buying infrastructure like we buy electricity or like we buy internet service at home. So by us having this fabric and it being associated with a brand like NetApp, it's opening up to the point where what do you really want to do? That's the question we come to you and ask. And if you're into the modernization, we can provide you all the modernization tools right within this fabric and seamlessly transition from one provider to the next or plug into another platform or the next or even put it on-prem or whatever you want to do, but this will allow the effective management of the entire platform in one location where you don't have to worry about a big team. You can take your existing team and that's where that internal support will come in and allow people to kind of concentrate and say, oh, this is some really interesting stuff. Coming from the engineering side of things, being and on that customer side and when you go into customers, you can connect with those guys and help them to leverage this knowledge that they already have because they're familiar with the products. They know the brand. So that makes it more palatable for them to accept. So from the cloud architects perspective, they're, you know, as you look at it, you look at the data driven fabric or data fabric and you're like, wow, this is a great idea. Practically, where's the starting point? You know, is this a set of products? Is it an architecture? Where do I start to bite into this effort? So ultimately, I think you look at it and I approach it the same way I would say, like I can't go just buy DevOps, right? But data fabric is still, it's a concept, but it's enabled by a suite of technology products. And we look at NetApp across our portfolio and see all the different products that we have, they all have a data fabric element to them, right? Whether it's a FAS and Snap Mirror and I'm snapping to an ONTAP cloud instance running in AWS, whether it's how we're going to integrate with Azure now with our NFS service that we're providing in there, whether it's hyper-converged infrastructure and the ability to move data off there. You know, our friend, David McCrory, talked about data having gravity, right? He coined that term and it does, it does have gravity and you need to be able to understand where it sits. We have analytics in place that help us craft that. We have a product called OCI that customers use and what it does, it gives them actionable intelligence about where their data sits, where things may be inefficient. We have to start making that transition to not just providing storage, but understanding what's in the storage, the value that it has and using it more like currency. I mean, we've heard George talk about data as currency. It really is kind of the currency and information is power, right? Yeah, Gabe, I mean, Gabe, this is right on the money. And crypto currency and blockchain is a tell sign of what's coming around the corner, a decentralized and distributed environment that's coming. That wave is way out there, but it's coming fast. So I want you to take a minute and talk about the cloud component because you mentioned cloud. Talk about your relationship to the clouds because multi-cloud is coming too, but it's not yet there yet, but just because you have a cloud, every cloud doesn't mean it's multi-cloud in the sense of moving stuff around. And then talk about the customer perspective because if I'm a customer, I'm saying to myself, okay, I have NetApp, I've had filers everywhere, I got on tab, they got understanding the management game, they got to manage data on-prem. But now I've got this cloud thing going on and I've got the shiny new toy startup over there that's promised me the moon. But I got to make a decision, you're laughing, I know what you're thinking about it. This is the dilemma, do I stay with what I know and what I know is that relevant for where I'm going? A lot of times stars will have that pitch. So address the cloud and then talk about the impact of the customer around the choice. Ultimately it boils down to me in many respects. When I have a conversation with a customer, if I'm going to go for the bright and shiny, there has to be a very compelling business interest to do so. If I've built a set of tools and processes around data governance, management, implementation, movement, et cetera, around a bunch of on-premises technologies and I want that same effect or that same look and feel in the public cloud, then that's how we transition there, right? I want to make it look like, I'm using it here locally but it's not on my side, it's somewhere else, it's being managed by somebody else from a physical standpoint. I'm just consuming that information. But I also want to have to go back and retool everything I've spent the last 15 and 20 years building because something new and neat comes along. If that new and neat thing comes along and abstracts away or it makes a significant cost reduction or something like that, then obviously you're going to validate that and look at and vet that technology out. But reality is, is that we kind of have these- Well, they don't want to re-code, they don't want to retool, they don't want to rewrite code but if you look at the clouds, AWS, Azure, and Google, top three in my mind, they all implement everything differently. They got S3 over there, they got over here and so I could run something on-prem but then I got to hire a DevOps team that's trained for Azure, Sydney, it's the reality. I mean, evolution might take care of this but right now, customers have to know that. We're at a point right now where customers, businesses we go to, real time is very important. Software as a service is the thing now. So if you have a customer who's just clicking on a button and if they can't see that website or whatever your business is, that's a problem.  So what you have to do is as a business, discover what you have internally and once you discover that and really understand it as a business, not just the tech team but the business actually understands that. Move that forward and then blend some cloud technology in that with a data fabric because you're leveraging what you already have. If most of the time they usually have some sort of net appliance of some sort and then some of the new appliances that we do have, you can either say have a small spin, put it next to an old appliance or use some of the OCI or something of that nature to help you migrate to a more dynamic. And the thing about it is, is to just make it more a fluent transition. That's what you're looking to do. Up time is everything. Yeah, totally. This fabric will allow you to have that up time so that you can propel your business and sustain your business because you want to be able to still use what you have and still get that ROI out of that technology. But at the same token, you want to be more dynamic than the competition so that you can increase that business and still grow the business but not lose any business. Sidney, you bring up a great point. In fact, we should do a follow up segment on this because what I'm hearing you say, and I've heard this many times in the queue but it's happening and certainly we're doing our part in the queue to help the tech guys, whether they're ops or devs, they're becoming more business savvy. They got to get closer to the business. You have to. But they don't want to get an MBA for sake but they have to become street MBA. They got to get that business degree through scar tissue. Yes. You can't just be the tech anymore. You have to understand why your business is making this effort, why it's investing this technology, why they would look to go to the public cloud if you can't deliver a service and try to emulate that. And we've seen that time and time again the concept of shadow IT and the shift away from resources. And if you want to be relevant long term and not just a guy that sits in the closet and plugs in the wires, start learning about your business, learn about how the business is run and how it generates revenue and see what you can do to affect that. Yeah, and the jobs aren't going away though.  No, it's not. And they use the main freemasoning example. Not really relevant but kind of, but there are other jobs. I mean, look at cyber security, huge data aspect that impacts storage. That paradigm is changing in real time. So good stuff, a lot of good business consciousness we should do a follow up on. I'll give you guys a final word in this segment that each could weigh in on what cloud architects should be doing right now. I mean, besides watching the queue and watching you guys here. I think they got to have the 20 mile stair. They got to understand the systems that are in place. It's almost like an operating system model. They got to see the big picture. Architecting on paper seems easy, but right now it's hard. What's your advice for cloud architects? I mean, I say continue to follow the trends. Continue to expose yourself to new technologies. I mean, I'm really interested in things like serverless and those types of technologies and how we integrate our platforms into those types of solutions because that's kind of the next wave of things that are coming along as we become more of an API driven ecosystem, right? So if the structure is code, if everything is just in time instances, spin up, how do I have the communications between those technologies? You just got to stay well ahead of the curve. And you know, Sidney, your thoughts? My thoughts are along those lines not only from a technical perspective, but also like you were talking about that business perspective. Understand your business needs because even though, and be able to provide a portfolio or a suite of tools that will help that business take the next step, and that's where that values. So it's kind of like a blend. You're more of a hybrid. Where you're coming in not only as a technical person, but you're coming in to assist the business and develop it and help it take its next steps. And IT is not a department anymore. It's everywhere. No, it's not. It is the business. It is the business, yes. Guys, great conversation here on the future of the cloud architect here inside theCUBE at NetApp Insight 2017. Here at the Mandalay Bay in Las Vegas, theCUBE's coverage. We'll be right back with more after this short break.