>>live from Atlanta, Georgia. It's the Q covering answerable best 2019. Brought to you by Red hat. >>Welcome back, everyone to the Cube. Live coverage in Atlanta, Georgia for answerable fest. This is Red Hats Event where all the practices come together. The community to talk about automation anywhere. John Kerry with my coast to Minutemen, our next two guests arrive. And Bergeron, principal community architect for answerable now Red Hat and Greg Dankers Berg, senior director, Community Ansel's. Well, thanks for coming on. Appreciate it. >>Thank you. >>Okay, So we were talking before camera that you guys had. This is a two day event. We're covering the Cube. You guys have an awful fast, but you got your community day yesterday. The day before the people came in early. The core community heard great things about it. Love to get an update. Could you share just what happened yesterday? And then we'll get in some of the community. Sure. >>We s o uh, for all of our answer professed for a while now we've started them with ah, community contributor conference. And the goal of that conference is to get together. Ah, lot of the people we work with online right people we see is IRC nicks or get hub handles rights to get them together in the same room. Ah, have them interact with, uh, with core members of our team. Uh, and that's where we really do, uh, make a lot of decisions about how we're gonna be going forward, get really direct feedback from some of our key contributors about the decisions were making The things were thinking about, uh, with the goal of, you know, involving our community deeply in a lot of decisions we make, that's >>a working session, meets social, get together. That's >>right, Several working sessions and then, you know, drinks afterward for those who want the drinks and just hang out time that >>way. Drinks and their last night was really good. I got the end of it. I missed the session, but >>they have the peaches, peaches, it on the >>table. That was good. But this is the dynamic community. This is one things we notice here. Not a seat open in the house on the keynote Skinny Ramon Lee, active participant base from this organic as well Be now going mainstream. How >>you >>guys handling it, how you guys ride in this way? Because certainly you certainly do. The communities which is great for feedback get from the community. But as you have the commercial eyes open sores and answerable, it's a tough task. >>Well, I'd like to think part of it is, I guess maybe it's not our first rodeo. Is that what we'd say? I mean, yeah, uh, for Ansel. I worked at ELASTICSEARCH, uh, doing community stuff. Before that, I worked at Red Hat. It was a fedora. Project leader, number five. And you were Fedora project Leader. What number was that? Number one depends >>on how you count, but >>you're the You're the one that got us to be able to call it having a federal project leader. So I sort of was number one. So we've been dealing with this stuff for a really long time. It's different in Anselm that, you know, unlike a lot of, you know, holds old school things like fedora. You know, a lot of this stuff is newer and part of the reason it's really important for us to get You know, some of these folks here to talk to us in person is that you know especially. And you saw my keynote this morning where they talked about we talked about modularity. Lot of these folks are really just focused on. They're one little bit and they don't always have is much time. People are working in lots of open source projects now, right, and it's hard to pay deep attention to every single little thing all the time. So this gives them a day of in case you missed it. Here's the deep, dark dive into everything that you know we're planning or thinking about, and they really are. You know, people who are managing those smaller parts all around answerable, really are some of our best feedback loops, right? Because they're people who probably wrote that model because they're using it every single day and their hard core Ansel users. But they also understand how to participate in community so we can get those people actually talking with the rest of us who a lot of us used to be so sad. Men's. I used to be a sis admin, lots of us. You know. A lot of our employees actually just got into wanting to work on Ansel because they loved using it so much of their jobs. And when you're not, actually, since admitting every day, you you lose a little bit of >>the front lines with the truth of what's around. Truth is right there >>and putting all these people together in room make sure that they all also, you know, when you have to look at someone in the eye and tell them news that they might not like you have a different level of empathy and you approach it a little bit differently than you may on the Internet. So, >>Robin So I lived in your keynote this morning. You talked about answerable. First commit was only back in 2012. So that simplicity of that modularity and the learnings from where open source had been in the past Yes, they're a little bit, you know, what could answerable do, being a relatively young project that it might not have been able to dio if it had a couple of decades of history? >>Maybe Greg should tell the story about the funk project >>way. There was a There was a project, a tread hat that we started in 2007 in a coffee shop in Chapel Hill, North Carolina is Ah, myself and Michael the Han and Seth the doll on entry likens Who still works with this with us? A danceable Ah, and we we put together Ah, an idea with all the same underpinnings, right? Ah, highly modular automation tool We debated at the time whether it should be based on SSL or SS H for funk. We chose SSL Ah, and you know, after watching that grow to a certain point and then stagnates and it being inside of red Hat where, you know, there were a lot of other business pressures, things like that. We learned a lot from that experience and we were able to take that experience. And then in 2012 there there's the open source community was a little different. Open source was more acceptable. Get Hubbell was becoming a common plat platform for open source project hosting. And so a lot of things came together in a short pier Time All that experience, although, >>and also market conditions, agenda market conditions in 2007 Cloud was sort of a weird thing that not really everyone was doing 2012 rolls around. Everyone has these cloud images and they need to figure out how to get something in it. Um, and it turns out that Hansel's a really great way to actually do that. And, you know, even if we had picked SS H back in the beginning, I don't know, you know, not have had time projects grow to a certain point. And I could point a lots of projects that were just It's a shame they were so ahead of their time. And because of that, you know, >>timing is everything with the key. I think now what I've always admired about the simplicity is automation requires that the abstract, the way, the complexities and so I think you bring a cloud that brings up more complexity, more use cases for some of the underlying paintings of the plumbing. And this is always gonna This is a moving train that's never going to stop. What was the feedback from the community this year around? As you guys get into some of these analytical capabilities, so the new features have a platform flair to it. It's a platform you guys announced answerable automation platform that implies that enables some value. >>You know, I >>think in >>a way. We've always been a platform, right, because platform is a set of small rules and then modules that attached to it. It's about how that grows, right? And, uh, traditionally, we've had a batteries included model where every module and plug in was built to go into answerable Boy, that got really big bright and >>we like to hear it. I don't even know how many I keep say, I'll >>say 2000. Then it'll be 3000 say 3000 >>something else, a lot of content. And it's, you know, in the beginning, it was I can't imagine this ever being more than 202 150 batteries included, and at some point, you know, it's like, Whoa, yeah, taking care of this and making sure it all works together all the time gets >>You guys have done a great You guys have done a great job with community, and one of the things that you met with Cloud is as more use cases come, scale becomes a big question, and there's real business benefits now, so open source has become part of the business. People talk about business, models will open source. You guys know that you've been part of that 28 years of history with Lennox. But now you're seeing Dev Ops, which is you'll go back to 78 2009 10 time frame The only the purest we're talking Dev ops. At that time, Infrastructures Co was being kicked around. We certainly been covering the cubes is 2010 on that? But now, in mainstream enterprise, it seems like the commercialization and operational izing of Dev ops is here. You guys have a proof point in your own community. People talk about culture, about relationships. We have one guest on time, but they're now friends with the other guy group dowels. So you stay. The collaboration is now becoming a big part of it because of the playbook because of the of these these instances. So talk about that dynamic of operational izing the Dev Ops movement for Enterprise. >>All right, so I remember Ah, an example at one of the first answer professed I ever went thio There were there were a few before I came on board. Ah, but it was I >>think it was >>the 1st 1 I came to when I was about to make the jump from my previous company, and I was just There is a visitor and a friend of the team, and there was an adman who talked to me and said, For the first time, I have this thing, this playbook, that I can write and that I can hand to my manager and say this is what we're going to D'oh! Right? And so there was this artifact that allowed for a bridging between different parts of the organization. That was the simplicity of that playbook that was human readable, that he could show to his boss or to someone else in the organ that they could agree on. And suddenly there was this sort of a document that was a mechanism for collaboration that everyone could understand buy into that hadn't really existed before. Answerable existed after me. That was one of the many, you know, flip of the light moments where I was like, Oh, wow, maybe we have something >>really big. There were plenty of other infrastructures, code things that you could hand to someone. But, you know, for a lot of people, it's like I don't speak that language right? That's why we like to say like Ansel sort of this universal automation language, right? Like everybody can read it. You don't have to be a rocket scientist. Uh, it's, you know, great for your exact example, right? I'm showing this to my manager and saying This is the order of operations and you don't have to be a genius to read it because it's really, really readable >>connecting system which connects people >>right. It's fascinating to May is there was this whole wave of enterprise collaboration tools that the enterprise would try to push down and force people to collaborate. But here is a technology tool that from the ground up, is getting people to do that collaboration. And they want to do it. And it's helping bury some >>of those walls. And it's interesting you mention that I'm sure that something like slack is a thing that falls into that category. And they've built around making sure that the 20 billion people inside a company all sign up until somebody in the I T departments like, What do you mean? These random people are just everyone's using it. No one saving it isn't secure, and they all freak out, and, um, well, I mean, this is sort of, you know, everybody tells her friend about Ansel and they go, Oh, right, Tool. That's gonna save the world Number 22 0 wait, actually, yeah. No, this is This actually is pretty cool. Yeah, yeah, yeah, I get started. >>Well, you know, sometimes the better mouse trap will always drive people to that solution. You guys have proven that organic. What's interesting to me is not only does it keep win on capabilities, it actually grew organically. And this connective tissue between different groups, >>right? Got it >>breaks down that hole silo mentality. And that's really where I tease been stuck? Yes. And as software becomes more prominent and data becomes more prominent, it's gonna just shift more power in the hands of developer and to the, uh, just add mons who are now being redeployed into being systems, architects or whatever they are. This transitional human rolls with automation, >>transformation architect >>Oh my God, that's a real title. I don't >>have it, but >>double my pay. I'll take it. >>So collections is one of the key things talked about when we talk about the Antelope Automation platform. Been hearing a lot discussion about how the partner ecosystems really stepping up even more than before. You know, 4600 plus contributors out there in community, But the partners stepping up Where do you see this going? Where? Well, collections really catalyze the next growth for your >>It's got to be the future for us that, you know, there there were a >>few >>key problems that we recognize that the collections was ultimately the the dissolution that we chose. Uh, you know, one key problem is that with the batteries included model that put a lot of pressure on vendors to conform to whatever our processes were, they had to get their batteries in tow. Are thing to be a part of the ecosystem. And there was a huge demand to be a part of our ecosystem. The partners would just sort of, you know, swallow hard and do what they needed to d'oh. But it really wasn't optimized Tol partners, right? So they might have different development processes. They might have different release cycles. They might have different testing on the back end. That would be, you know, more difficult to hook together collections, breaks a lot of that out and gives our partners a lot of freedom to innovate in their own time. Uh, >>release on their own cycle, the down cycle. We just released our new version of software, but you can't actually get the new Ansel modules that are updated for it until answerable releases is not always the thing that you know makes their product immediately useful. You know, you're a vendor, you really something new. You want people to start using it right away, not wait until, you know answerable comes around so >>and that new artifact also creates more network effects with the, you know, galaxy and automation hub. And you know, the new deployment options that we're gonna have available for that stuff. So it's, I think it's just leveling up, right? It's taking the same approach that's gotten us this foreign, just taking out to, uh, to another level. >>I certainly wouldn't consider it to be like that. Partners air separate part of our They're still definitely part of the community. It's just they have slightly different problems. And, you know, there were folks from all sorts of different companies who are partners in the contributor summit. Yesterday >>there were >>actually, you know, participating and you know, folks swapping stories and listening to each other and again being part of that feedback. >>Maybe just a little bit broader. You know, the other communities out there, I think of the Cloud Native Computing Foundation, the Open Infrastructure Foundation. You're wearing your soul pin. I talk a little bit of our handsome How rentable plays across these other communities, which are, you know, very much mixture of the vendors and the end users. >>Well, I mean and will certainly had Sorry. Are you asking about how Ansel is relating to those other communities? Okay, Yeah, because I'm all about that. I mean, we certainly had a long standing sort of, ah fan base over in the open stacks slash open infrastructure foundation land. Most of the deployment tools for all of you know, all the different ways. So many ways to deploy open stack. A lot of them wound up settling on Ansel towards the end of time. You know, that community sort of matured, and, you know, there's a lot of periods of experimentation and, you know, that's one of the things is something's live. Something's didn't but the core parts of what you actually need to make a cloud or, you know, basically still there. Um And then we also have a ton of modules, actually unanswerable, that, you know, help people to operationalize all their open stack cloud stuff. Just like we have modules for AWS and Google Cloud and Azure and whoever else I'm leaving out this week as far as the C N. C f stuff goes, I mean again, we've seen a lot of you know how to get this thing up and running. Turns out Cooper Daddy's is not particularly easy to get up and running. It's even more complicated than a cloud sometimes, because it also assumes you've got a cloud of some sort already. And I like working on our thing. It's I can actually use it. It's pretty cool. Um, cube spray on. Then A lot of the other projects also have, you know, things that are related to Ansel. Now there's the answer. Will operator stuff? I don't know if you want to touch on that, but >>yeah, uh, we're working on. We know one of the big questions is ah, how do answerable, uh, and open shift slash kubernetes work together frequently and in sort of kubernetes land Open shift land. You want to keep his much as you can on the cluster. Lots of operations on the cluster. >>Sometimes you got >>to talk to things outside of the cluster, right? You got to set up some networking stuff, or you gotta go talk to an S three bucket. There's always something some storage thing. As much as you try to get things in a container land, there's all there's always legacy stuff. There's always new stuff, maybe edge stuff that might not all be part of your cluster. And so one of the things we're working on is making it easier to use answerable as part of your operator structure, to go and manage some of those things, using the operator framework that's already built into kubernetes and >>again, more complexity out there. >>Well, and and the thing is, we're great glue. Answerable is such great glue, and it's accessible to so many people and as the moon. As we move away from monolithic code bases to micro service's and vastly spread out code basis, it's not like the complexity goes away. The complexity simply moves to the relationship between the components and answerable. It's excellent glue for helping to manage those relationships between. >>Who doesn't like a glue layer >>everyone, if it's good and easy to understand, even better, >>the glue layers key guys, Thanks for coming on. Sharing your insights. Thank you so much for a quick minute to give a quick plug for the community. What's up? Stats updates. Quick projects Give a quick plug for what's going on the community real quick. >>You go first. >>We're big. We're 67 >>snow. It was number six. Number seven was kubernetes >>right. Number six out of 96 million projects on Get Hub. So lots of contributors. Lots of energy. >>Anytime. I tried to cite a stat, I find that I have to actually go and look it up. And I was about to sight again. >>So active, high, high numbers of people activity. What's that mean? You're running the plumbing, so obviously it's it's cloud on premise. Other updates. Projects of the contributor day. What's next, what's on the schedule. >>We're looking to put together our next contributor summit. We're hoping in Europe sometime in the spring, so we've got to get that on the plate. I don't know if we've announced the next answer will fast yet >>I know that happens tomorrow. So don't Don't really don't >>ruin that for everybody. >>Gradual ages on the great community. You guys done great. Work out in the open sores opened business. Open everything these days. Can't bet against open. >>But again, >>I wouldn't bet against open. >>We're here. Cube were open. Was sharing all the data here in Atlanta with the interviews. I'm John for his stupid men. Stayed with us for more after this short break.

>> Narrator: Live from Stanford University in Palo Alto, California, it's theCube, covering Women in Data Science conference 2018. Brought to you by Stanford. >> Welcome back to theCube. I'm Lisa Martin and we're live at Stanford University, the third annual Women in Data Science conference, WiDS. This is a great one day technical event with keynote speakers, with technical vision tracks, career panel and some very inspiring leaders. It's also expected to reach over 100,000 people today, which is incredible. So we're very fortunate to be joined by our next guest, Ruth Marinshaw, the CTO for Research Computing at Stanford University. Welcome to theCube, Ruth. >> Thank you. It's an honor to be here. >> It's great to have you here. You've been in this role as CTO for Research Computing at Stanford for nearly six years. >> That's correct. I came here after about 25 years at the University of North Carolina Chapel Hill. >> So tell us a little bit about what you do in terms of the services that you support to the Institute for Computational Mathematics and Engineering. >> So our team and we're about 17 now supports systems, file systems storage, databases, software across the university to support computational and data intensive science. So ICME, being really the home of computational science education at Stanford from a degree perspective, is a close partner with us. We help them with training opportunities. We try to do some collaborative planning, event promotion, sharing of ideas. We have joint office hours where we can provide system support. Margot's graduate students and data scientists can provide algorithmic support to some thousands of users across the campus, about 500 faculty. >> Wow. So this is the third year for WiDS, your third year here. >> Ruth: It is. >> When you spoke with Margot Gerritsen, who's going to be joining us later today, about the idea for WiDS, what were some of your thoughts about that? Did you expect it to make as big of >> Ruth: No. >> an impact? >> No, no people have been talking about this data tsunami and the rise of big data, literally for 10 years, but actually it arrived. This is the world we live in, data everywhere, that data deluge that had been foreseen or promised or feared was really there. And so when Margot had the idea to start WiDS, I actually thought what a nice campus event. There are women all over Stanford, across this disciplines who are engaged in data science and more who should. Stanford, if anything, is known for its interdisciplinary research and data science is one of those fields that really crosses the schools and the disciplines. So I thought, what a great way to bring women together at Stanford. I clearly did not expect that it would turn into this global phenomenon. >> That is exactly. I love that word, it is a phenomenon. It's a movement. They're expecting, there's, I said over a 100,000 participants today, at more than 150 regional events. I think that number will go up. >> Ruth: Yes. >> During the day. And more than 50 countries. >> Ruth: Yes. >> But it shows, even in three years, not only is there a need for this, there's a demand for it. That last year, I think it was upwards of 75,000 people. To make that massive of a jump in one year and global impact, is huge. But it also speaks to some of the things that Margot and her team have said. It may have been comfortable as one of or the only woman at a boardroom table, but maybe there are others that aren't comfortable and how do we help them >> Ruth: Exactly. >> and inspire them and inspire the next generation. >> Exactly. I think it's a really very powerful statement and demonstration of the importance of community and building technical teams in making, as you said, people comfortable and feeling like they're not alone. We see what 100,000 women maybe joining in internationally over this week for these events. That's such a small fraction compared to what the need probably is to what the hunger probably is. And as Margot said, we're a room full of women here today, but we're still such a minority in the industry, in the field. >> Yes. So you mentioned, you've been here at Stanford for over five years, but you were at Chapel Hill before. >> Ruth: Yes. >> Tell me a little bit about your career path in the STEM field. What was your inspiration all those years ago to study this? >> My background is actually computational social sciences. >> Lisa: Oh interesting. >> And so from an undergraduate and graduate perspective and this was the dawn of western civilization, long ago, not quite that long (Lisa laughs) but long ago and even then, I was drawn to programming and data analysis and data sort of discovery. I as a graduate student and then for a career worked at a demographic research center at UNC Chapel Hill, where firsthand you did data science, you did original data collection and data analysis, data manipulation, interpretation. And then parlayed that into more of a technical role, learning more programming languages, computer hardware, software systems and the like. And went on to find that this was really my love, was technology. And it's so exciting to be here at Stanford from that perspective because this is the birthplace of many technologies and again, referencing the interdisciplinary nature of work here, we have some of the best data scientists in the world. We have some of the best statisticians and algorithm developers and social scientists, humanists, who together can really make a difference in solving, using big data, data science, to solve some of the pressing problems. >> The social impact that data science and computer science alone can make with ideally a diverse set of eyes and perspectives looking at it, is infinite. >> Absolutely. And that's one reason I'm super excited today, this third WiDS for one of the keynote speakers, Latanya from Harvard. She's going to be talking, she's from government and sort of political science, but she's going to be talking about data science from the policy perspective and also the privacy perspective. >> Lisa: Oh yes. >> I think that this data science provides such great opportunity, not just to have the traditional STEM fields participating but really to leverage the ethicists and the humanists and the social sciences so we have that diversity of opinions shaping decision making. >> Exactly. And as much as big data and those technologies open up a lot of opportunities for new business models for corporations, I think so does it also in parallel open up new opportunities for career paths and for women in the field all over the world to make a big, big difference. >> Exactly. I think that's another value add for WiDS over it's three years is to expose young women to the range of career paths in which data science can have an impact. It's not just about coding, although that's an important part. As we heard this morning, investment banking, go figure. Right now SAP is talking about the impact on precision medicine and precision healthcare. Last year, we had the National Security Agency here, talking about use of data. We've had geographers. So I think it helps broaden the perspective about where you can take your skills in data science. And also expose you to the full range of skills that's needed to make a good data science team. >> Right. The hard skills, right, the data and statistical analyses, the computational skills, but also the softer skills. >> Ruth: Exactly. >> How do you see that in your career as those two sides, the hard skills, the soft skills coming together to formulate the things that you're doing today? >> Well we have to have a diverse team, so I think the soft skills come into play not just from having women on your team but a diversity of opinions. In all that we do in managing our systems and making decisions about what to do, we do look at data. They may not be data at scale that we see in healthcare or mobile devices or you know, our mobile health, our Fitbit data. But we try to base our decisions on an analysis of data. And purely running an algorithm or applying a formula to something will give you one perspective, but it's only part of the answer. So working as a team to evaluate other alternative methods. There never is just one right way to model something, right. And I think that, having the diversity across the team and pulling in external decision makers as well to help us evaluate the data. We look at the hard science and then we ask about, is this the right thing to do, is this really what the data are telling us. >> So with WiDS being aimed at inspiring and educating data scientists worldwide, we kind of talked a little bit already about inspiring the younger generation who are maybe as Maria Callaway said that the ideal time to inspire young females is first semester of college. But there's also sort of a flip side to that and I think that's reinvigorating. >> Yes. >> That the women who've been in the STEM field or in technology for awhile. What are some of the things that you have found invigorating in your own career about WiDS and the collaboration with other females in the industry? >> I think hearing inspirational speakers like Maria, last here and this year, Diane Greene from Google last year, talk about just the point you made that there's always opportunity, there's always time to learn new things, to start a new career. We don't have to be first year freshmen in college in order to start a career. We're all lifelong learners and to hear women present and to see and meet with people at the breakout sessions and the lunch, whose careers have been shaped by and some cases remade by the opportunity to learn new things and apply those skills in new areas. It's just exciting. Today for this conference, I brought along four or five of my colleagues from IT at Stanford, who are not data scientists. They would not call themselves data scientists, but there are data elements to all of their careers. And watching them in there this morning as they see what people are doing and hear about the possibilities, it's just exciting. It's exciting and it's empowering as well. Again back to that idea of community, you're not in it alone. >> Lisa: Right. >> And to be connected to all of these women across a generation is really, it's just invigorating. >> I love that. It's empowering, it is invigorating. Did you have mentors when you were in your undergraduate >> Ruth: I did. >> days? Were they males, females, both? >> I'd say in undergraduate and graduate school, actually they were more males from an academic perspective. But as a graduate student, I worked in a programming unit and my mentors there were all females and one in particular became then my boss. And she was a lifelong mentor to me. And I found that really important. She believed in women. She believed that programming was not a male field. She did not believe that technology was the domain only of men. And she really was supportive throughout. And I think it's important for young women as well as mid-career women to continue to have mentors to help bounce ideas off of and to help encourage inquiries. >> Definitely, definitely. I'm always surprised every now and then when I'm interviewing females in tech, they'll say I didn't have a mentor. >> Lisa: Oh. >> So I had to become one. But I think you know we think maybe think of mentors in an earlier stage of our careers, but at a later stage we talked about that reinvigoration. Are you finding WiDS as a source of maybe not only for you to have the opportunity to mentor more women but also are you finding more mentors of different generations >> Oh sure. >> as being part of WiDS? >> Absolutely, think of Karen Mathis, not just Margot but Karen, getting to know her. And we go for sort of walks around the campus and bounce ideas of each other. I think it is a community for yes, for all of us. It's not just for the young women and we want to remain engaged in this. The fact that it's global now, I think a new challenge is how do we leverage this international community now. So our opportunities for mentorship and partnership aren't limited to our local WiDS. They're an important group. But how do we connect across those different communities? >> Lisa: Exactly. >> They're international now. >> Exactly. I think I was on Twitter last night and there was the WiDS New Zealand about to go live. >> Yeah, yeah. >> And I just thought, wow it's this great community. But you make a good point that it's reached such scale so quickly. Now it's about how can we learn from women in different industries in other parts of the world. How can they learn from us? To really grow this foundation of collaboration and to a word you said earlier, community. >> It really is amazing though that in three years WiDS has become what it has because if you think about other organizations, special interest groups and the like, often they really are, they're not parochial. But they tend to be local and if they're national, they're not at this scale. >> Right. >> And so again back to it's the right time, it's the right set of organizers. I mean Margot, anything that she touches, she puts it herself completely into it and it's almost always successful. The right people, the right time. And finding ways to harness and encourage enthusiasm in really productive ways. I think it's just been fabulous. >> I agree. Last question for you. Looking back at your career, what advice would you have given young Ruth? >> Oh gosh. That's a really great question. I think to try to connect as much as you can outside your comfort zone. Back to that idea of mentorship. You think when you're an undergraduate, you explore curricula, you take crazy classes, Chinese or, not that that's crazy, but you know if you're a math major and you go take art or something. To really explore not just your academic breadth but also career opportunities and career understanding earlier on that really, oh I want to be a doctor, actually what do you know about being a doctor. I don't want to be a statistician, well why not? So I think to encourage more curiosity outside the classroom in terms of thinking about what is the world about and how can you make a difference. >> I love that, getting out of the comfort zone. One of my mentors says get comfortably uncomfortable and I love that. >> Ruth: That's great, yeah. >> I love that. Well Ruth, thank you so much for joining us on theCube today. It's our pleasure to have you here and we hope you have a great time at the event. We look forward to talking with you next time. >> We'll see you next year. >> Lisa: Excellent. >> Thank you. Buh-bye. >> I'm Lisa Martin. You're watching theCube live from Stanford University at the third annual Women in Data Science conference. #WiDS2018, join the conversation. After this short break, I'll be right back with my next guest. Stick around. (techno music)