So, and welcome to this special CUBE conversation here in Palo Alto, California. I'm John Furrier, the co-founder of SiliconANGLE Media co-host of theCUBE. We are in our studio with special guest Dheeraj Tolia, who's the CEO and co-founder of Casten. Hot startup in the cloud native space, doing some very interesting things. Really kind of a modern approach to bringing software development data and cloud all together. Welcome to this conversation. A great to be here. Thank you so much for having me. Congratulations on all your success. I know you guys have done a lot with your seed funding. Take a second before we get into some of the things that I think are the most important stories in cloud native, which is Kubernetes, obviously it's a hardware coming back out of CUBECon. What's going on with Casten? Talk about the company, when you were formed, how many employees? I know you did the seed rounds. Just talk about what you guys do. Great, so Casten is a company, for those of you who are curious, it's actually a German word means container, so it's very apropos for what we're doing. We were founded over a year ago at this point in time. We're based here in California in the Bay Area. We did a $3 million seed round. We, it was angel only, so an institutional, lot of interest from people that are working with other entrepreneurs in the cloud native ecosystem. People in the industry. People inside, kind of inside the ropes, kind of, with the individuals. Yeah, so personal investments from, you know, all the top five cloud companies as an example, folks that have been funding other co-founders for a while, so we're very happy to have them in our corner, in particular, Majeed Gil, sits on our board. So he's had multiple successes, both in terms of investments and personally, so we're so happy to have him as one of our backers. And, right, so we are roughly nine people right now, all local, people with a lot of both startup and enterprise experience. So it's the right set of people. It's a very diverse group of people, so we're very happy with the team we've put together here. Yeah, diversity just was at Sundance and even on the film side. Some of the most successful virtual reality companies are Stanford Symbolum Systems majors. Huge diversity interdisciplinary dynamic, and I want to drill into that. Okay, so no Series A yet, so no board members from VCs, I'm sure they're knocking on your doors, clamoring down on some of the success you have. But what's different about your approach you guys are taking? Is the positioning assessed? What's the product? How do you guys make money? What are you seeing that? Okay, great question. So at the very high level we're focused on making it very easy for enterprises to deploy, manage, build, stateful applications in the cloud native way. In terms of how we see people adopting it, I think that there's been a tremendous mind shift as well as an ecosystem shift where we see this blurring of lines between applications and infrastructure. So one of the unique insights we saw ourselves was that to approach this problem, we need to come at it from a developer first point of view and application first point of view instead of like I'm a recovering infrastructure person coming at it from the bottom up where you think about disks and volumes and storage arrays. This is really about the application, it's about the cloud, it's about the deployment model, it's about how we enable and empower developers but also operators in these large scale environments and make it and get through the right balance of responsibilities between the two. And that's really what's resonating with the customers we work with today. Yeah, and certainly the cloud native trend has been the hottest day, and it's exciting for me because early days of the Clouderati, 2008, 2009 timeframe, you saw the first generation DevOps and these are folks who were open source guys and gals who had to build their own stuff from scratch. I used to say, eating glass and spitting out nails, hardcore techies. Then as it goes mainstream with cloud computing, this is the modus operandus that people want to program in, just infrastructure as code as it's been called, this now is mainstream. It's okay, given that, we've been covering that till the cows come home. But now you're talking about orchestration, you're talking about some of the next level thinking which is how to make things easier, how to automate, how to make it so the developer doesn't have to do the provisioning and all that stuff. This is key, okay, I get that. Now everyone goes, oh no, where's my data? That seems to be something that you guys seem to be taking an attack. What are you guys doing specifically around data management because now data is now not only part of the app, it's a critical linchpin to the value creation in whether it's collective intelligence or any kind of coolness at the app level is data-driven. What do you guys do? So a great question. So when we talk about data management, somewhat of a nebulous term, but to make it more concrete, we really care about protecting your data, making sure it is safe in particular when you're working across multiple environments, multiple clusters, multiple clouds. But we care a lot more about, as you talked about, enabling and making it simple. So what does data mobility look like? What does data manipulation look like? So whether you're talking about moving entire application stacks with the data across clusters in the same cloud or across multiple clouds, those are some of the things we make it very easy for people to do because it is highly relevant and these are the odds that come from, and it's not just the CICD environment, but also talking about production environments and operator challenges there. So more concretely, when we look at use cases for a product involving disaster recovery, involving data protection, backup and recovery, multi-cloud migration, that's where we come in with our customers today. Okay, so to go back in my generation when I was growing up in the business, when we had to build all of our own stuff, build our own stacks, that's how old I am, remember those glory days? You had data architects. Yes. And it was siloed based. Your app was your database and schemas and all that good stuff. But now data is horizontally scalable to cloud. Beautiful thing, right? So this is a key dynamic. What do companies and developers specifically have to think about when they think about being a data architect?  This is important because now workloads are sharing data. So you might have two workloads, A and B sharing data. That's kind of outside the current old guard mentality. Yes. What are you guys doing there? Do you see that as something that's important? It's important, right? So what's happened is a lot of power and responsibility that's shifted the developer from the former data architect role. Sometimes it would be a database engineering team, et cetera. And we want to empower that. There's still challenges, especially when you look at things like compliance, auditing, when you have sensitive data at play. So we make some of those things easier from having auditing compliance features in there. But what we really care about is, and some of this we also do it in an open source manner, that is we work with people to make sure that developers don't slow down. They can pick down technology stacks, where they store the data. And it's all really part of code for them. But from the operator, from the architect point of view, they have visibility into that. That's what they really care about. Who's the operator? The fine operator in that context. Okay, it's a great question. The operator tends to be one of two people. It tends to be the people that care about infrastructure, but keeping the lights on. That's what they worry about. So this would be the data. Yeah, what used to be IT guys, now it tends to be the DevOps team, the SRE team, et cetera. But so they have been transitioning into this role as you see skills change over time too. Or sometimes it will be the team that used to be a former database engineering teams. As an example, they used to provision this, but now their goal is, and we hear this from customers, is that we care about developer experiences. It's not about shipping binaries and patches anymore. This is about making sure for our users, we can make our developers fast and empower them. So how do they deliver that without getting in the way, but still getting some of the things they used to do earlier, that is being able to make sure that it is stored in the same manner, that is it services the needs of the broader business, whether other groups using it, whether it be disaster recovery, business continuity. So all of those, so we want to be able to empower both sides of this party, so they feel comfortable moving into this new world today. You know, I go back to the open stack days when, and still going on now, you see them more in the cloud native, the distinction between stateful and stateless applications. What's your reaction to the growth of stateful applications? Is it growing? How is it growing? What is some of the characteristics of how that is shaping out with stateful applications? So let's talk about sometimes even misconceptions that the community has today, that platforms just communities are not ready for stateful workloads. We definitely believe that is not true, and it's not just us, they're a plethora of companies using stateful applications in production today. It is, it was late, initially we saw the compute part handled, you know, more advanced scheduling orchestration that you saw in terms of multiple flame works with Kubernetes vending the game. We saw a lot of networking innovation in there, including service measures, which I know you have covered a lot in detail earlier. But now we're seeing data come into play, and that is the third leg of the stool that we believe it'll be important for real life large scale production workloads in these environments. With new features being geared in Kubernetes 1.9, such as the whole workloads category with other open source frameworks popping up to support that out of tree, we see a lot more people feeling comfortable going deploying stateful applications. But what they really want is the same ease of use and flexibility that they had with stateless applications. And that is a gap that still needs to be bridged in the multiple people working on that. Okay, I got to ask you, since you're an expert here, we have a lot of our audience is learning about the space. So, you know, we talk and we're having some fun here about some of the most important stories in cloud native. But some people just don't even understand the difference between stateless and stateful in context to unlocking business value. So there's a lot of now people coming in saying, okay, I get DevOps, where's the business value? What does some context is? So what is in your definition the difference between stateless and stateful applications? So the way I look at it is when I look at stateless applications, it is much easier to blow them away, bring them back anywhere you want because they might have some cash state but nothing persistent, right? And generally all those apps depend on persistence where it's stored outside of your cloud native environment. We want to bring that in when you talk about stateful applications. But it's not just that, it's also the model of building stateful applications is changing, where you get polyglot persistence where people using like, if you use GitLab as an example, they use Redis, Postgres and other data services all in the same app. You want as a part of being embedded within your application and you want, you're also getting shorting of data. What used to be a large monolith database the same way we see microservice evolution on the stateless side of things. We're seeing the same thing on the stateful side where data sets are getting broken up logically into multiple distinct components that are managed and operated independently. So let's talk about that for a second because stateless applications was an approach people took because it was easier, right? And it was relevant at that time. But it's been said certainly in theCUBE many times, it's hard to do stateful applications. Why is it hard and what are the benefits of doing it? Okay. It's hard to do stateful applications because A, there's a greater risk. You never want to lose your customer's data. So you treat it with slightly more care. Some of the primitives, especially when you look at the cloud native world weren't ready 18 months ago as an example, whether you talk about things like the container storage interface, whether you talk about things like stateful sets, whether you talk about applications that come with a notion of permanent. Sometimes they remember their host name, the IP address. And we see a lot of traditional applications moving into this environment too. But that has been fixed by the community which is a very amazing thing. And they've approached it with a developer force focus. The benefits of bringing it into this environment are tremendous because you get this business agility side of things, not just developer agility where you can move much faster because you don't depend on external resources anymore. You get the advantage of being able to clone application stacks at a click or at an API call level. You get the advantage of being able to take these applications and port them across multiple places because these primitives that are provided by underlying container orchestration layer make it so much easier to do so. So there's a lot of advantages to bring it into the fold source to speak than leaving it outside right now. I was talking to someone in the industry I won't say their name without outing them but I was like, oh man, it's so hard.  Stainful application is never going to happen. It can't scale or the scale is the problem. So I got to ask you if you can address that because if you go down this road the enterprise is going to start thinking about the most important thing which is scale. What are the challenges that enterprises have with Stainful at scale? Okay, that's a great question. So there are two or three different kinds of things. The obvious thing, especially that jumps a developer's mind when it comes to scale is things like performance, right? But I think there's only one aspect of things and there are scale out systems when you think of Cassandra, et cetera that are getting a better handle on some of those issues. But more important when we deal with scale especially from the enterprise point of view as far as state is concerned people care about visibility, right? Show me where all my state is as developers are constantly changing architectures, constantly deploying. They have scale issues when you spread across multiple clouds with multiple clusters. So help me manage some of those things. They have issues around compliance of the state which is much larger, especially as it gets segmented out, right? Because it's not just we know customers that are running hundreds of instances of MongoDB as an example in some of these environments. And just trying to wrap the minds around managing all of that at scale is another issue. So these are all the things that enterprises think about when they talk about scale and not just performance scale or IOPS scale but it's about management scale. How do you guys solve that problem? So we solve it by a number of different ways. First of all we believe in treating the problem as an application first with the application first approach. So we think of it as the application first so it doesn't matter how many volumes you're using or how many disks or even if you're not using shared storage because you have no single point of failure in modern cloud native database systems. So there is that. And then that's the uniform encapsulation that we provide high levels of abstraction on to give people an easy view to see what's unmanaged, what's managed in the system, where do I have workloads? It's something you show up instantly so we can notify about that. So those are all the things that we make it easy. Apart from just monitoring things like health of the system, validating things which are table stakes right now. So I've got to ask you, as you see this evolution happening, you guys are at the forefront of it with your startup and again, congratulations. Like what you guys are doing. But the challenges in the enterprise are, well, where do you have a data management solution? You must get that a lot. So I got to ask you, when you roll into a customer or potential customer that you have now, you say, hey, well, we got this cover. We can do stateful applications. We're application centric. We're doing DevOps, we're doing the lines are blurring. You should look at us and the clients, whoa, hey, you know what? I already got a data management provider in my application. What do you say to that? It's a good thing. We see that not across a large fraction of our customers. We definitely see that across some. The majority of reasons why sometimes we don't see it or how we responded this is the large fraction of tools out there used to cater to what now we say legacy environments, but they tend to be very server or VM centric thing. Things that don't move, things that are constantly on scaling up and down, things that are quite static. When you go look at tools that come up from large companies in the storage vendor space as an example. So one of the things that we help provide this is tools that are cloud native themselves that can adapt to cloud native workloads that are built first for a cloud native world. So that very easily resonates with customers. And the other thing we talk about is extensibility. Again, when you talk about data management solutions right now, they don't really, they operate at the infrastructure level. So they can't figure out what it means to take a consistent view of a large distributed Cassandra system as an example, or how to stitch together things such as consistent across multiple data stores. We have an extensible framework that allows people to inject their own code into our system that says, you know, I want to do things in a custom manner. I want to do things that's particularly to my context, my enterprise. And we help enable that, which again, none of the existing data management tools can do today. Okay, so you guys have, this is what they call, you call the K10 platform. It's a K10 platform and the extensibility part I talked about is called Canister. It's an open source project. You can find it on GitHub. And- Did you guys sponsor that? Is that a different one? That is sponsored by us. So we did evolve that as again, based on what customer needs came out to be. And we said this is something that doesn't make sense for us to hold. We would like to build a community around it. We would like to see people contributed and be the common place where people can share recipes of blueprints for managing- So Canister is a community approach. Yes, Canister is definitely. How's it going? What's the uptake on that? It's good, right? So apart from get up stars, we have people on the Slack channel. We have people reaching out independently. We have people that have asked us, how do they develop their own blueprints for more complicated workflows? So even though we released it roughly a month ago at this point in time, the input we've gotten both on public and private channels has been really good. Great, okay, that's awesome. Well, I want to shift gears a little bit, talk about multi-cloud. It's the hottest story in tech.  Just have an app in, I have 365 on Azure and I'm doing something on Google TensorFlow and I'm running some stuff in Amazon. That's multiple clouds, but it's not the same workload, right? I don't consider that multi-cloud per se. I think that's multiple clouds having a workload from a company. So with that, what are the biggest problems customers are facing with multi-cloud, in your opinion, because you guys are kind of teasing this out. You've got Kubernetes and all this stuff going on. What are the challenges with multi-cloud? So because we help customers in multiple public clouds, we see a lot of this. In terms of a target category for enterprises, the vast majority, I'm talking 85% plus are in multiple public clouds. Different reasons, we can talk about that why, but then multiple public clouds. And what we see for them is that there's a spectrum. Their multi-cloud doesn't mean one thing. We see people at different degrees on the spectrum. Small minority care about check boxes, insurance, that is push, come to shove, help me move to different cloud, but really the majority of use cases we see is not about moving on a daily basis and application between cloud A to B, but they see problems in terms of I want this application to run on cloud A and B and sometimes and C because they have a global footprint and they might not always have the cloud provider of choice region in the region they want to expand into. Before you go further, I'll just double down on that because that seems really easy to just go, oh, we're just going all three clouds. But you got S3 on AWS. I just got a different storage. So each stack has its own coding. And that's a problem. So is it a problem or how bad is it? It is a problem. So let's talk about two or three things happening that helps solve this. So some of it's a problem. Kubernetes has done a great job in particular of abstracting some of those things away, not all of them, but some of them away. There are other new abstractions coming out such as the open service broker that originated in the cloud foundry movement and now has been picked up by multiple different platforms that's again helping abstract some of these differences away. We help with some of the management as well as portability across these environments because we can take care, you're making sure policies, management, all of that looks the same no matter what cloud provider you're working on and we understand the underlying infrastructure and we translate business level or operator level objectives into infrastructure level objectives. So there's some that we do to also help in that space. So overall, I think the situation is much better than it was say three years ago in terms of being able to do some of this. Obviously the devil is sometimes in the details but now we are, it's getting. The goal is not to hire a whole development team for each stack. Exactly. That's kind of the end game that we're trying to get to.  Yeah, some customization. I mean if you look at the open source distribution maybe 10% and 90% reuse or using abstractions. And that is a realistic goal that I believe most people are pragmatic and shooting for. How has Kubernetes and Kastin helping specifically solve the multi-cloud problem? It's a good question again. Right, so Kubernetes again, so let's talk about a customer base, right? A lot of people are picking Kubernetes even though sometimes they squarely on-prem because they know they will be moving to public class sometimes a compliance issue, sometimes a roadmap issue but they know they're moving there and this gives them the abstractions that they're not tied into a particular infrastructure underneath whether it be a VMware-based platform, open stack and tunnel or some public cloud vendor. They're picking that with that golden mind because a lot of the concepts are a cloud neutral. What we do is we help take also some of the data around it. Data that might be sitting on a storage provider of choice and make that cross-cloud portable either by doing it at the application layer which is a great thing or by able to understand the differences between clouds if you just click a button or call an API you can say, I want to migrate this entire application stack including services, configuration, your state, your container images, all of that into a cloud, into a different cloud, a different region. So we take care of all the complexity for our users, for the developers, for the operators. So I got to ask you the cloud question that I always like to squint through all the marketing height from the cloud vendors and that is regions matter, right? So when you're talking about regions there's some locality issues that need to come up that could impact safe code and services. GDPR in Europe is one and even in Asia specific there's also some geopolitical things going on and hackers and malware out there so you got security and whatnot. How should a company look at the region and the multi-region approach on each cloud which then is complicated and it's even more complicated when you do that across multiple clouds. That's the future that's coming down the street very fast. What's your view on that? So there is a lot of buzz around this, a lot of things being proposed. I think people need to take a more nuanced look at this compared to some of the things I see out there where speed of light is an issue especially when dealing with multiple regions. So either we architect applications correctly to be able to handle that and sometimes again some of these newer cloud native data stores have the ability to hide some of that performance gap in there. But overall when we look into architecting things this is about how do you deploy different application stacks at different clusters and maybe it's global load balancing to shard across them as an example. But we see a number of newer emerging patterns of building applications that's making it much more feasible to do as things go over. So I do not think enterprises should be scared into adopting some of these approaches. I think multi-region within the same cloud provider is definitely the first thing people should try and then moving out across which is again the adoption pattern we see within the enterprises we work with. So let's talk about the entrepreneurial journey of your company. Obviously you're the co-founder. Yes. You're in an environment now where it's been pretty brutal and you can almost see a lot of trends really jumping out now. And we were doing theCUBE the 10th year doing SiliconANGLE ninth year at theCUBE. And I covered all those companies were funded before 2012.  A lot of them, that was pre-cloud. I mean if you think about it they didn't see the visibility mocking Amazon or using Amazon. Didn't see Amazon and now the cloud as that disruptive enabler. So the wave is getting sucked out for the big tsunami coming. So it exposes that water that now's, you see all the clams and crabs running around. What's different? I mean, because now you can get things faster done. You got nine people. A lot of entrepreneurs are trying to crack the code of how to be successful in this environment with cloud, with data, new dynamics never have seen before. So I think from the entrepreneurial side of thing, the thing in my advice is to figure out what is the unfair advantage that small teams have? There's always this challenge, right? This is equivalent of five, eight years ago people would say, what if Google did this and before that what if Microsoft did this? I think where does the unfair advantage for smaller companies come from in these environments? Now a traditional go big or go home approach doesn't work anymore. What we have found a lot of success with is concentrating very hard on customer needs and their pain points. Before force line of code was written, we really spoke to customers to say, what are your pain points? And that's when we also started latching on to write this multi-cloud thing. Where generally we see a lot of solutions working, being provided by some of these cloud providers, but they're tailored for the particular cloud. They do not fit the enterprise model of working across different providers. So helping with that pain point, helping with that portability has been really good for us in particular. But it's also, I do not treat public clouds as competition. I do look at them as partners because I think there is a win-win situation. We've been very, very happy with some of the conversations we've had with some of the bigger cloud providers out there. We have joint customers, things of that nature. And that has been very successful in terms of that operating model. Because I think a lot of people realize this is not a zero sum game. On, if you're looking at just on-prem environments it's less than a zero sum game these days. But being a part of a rapidly expanding system I think the pie is going larger and I think there are less incentives to be seen as strictly competitive versus a partnership play there. Well, great to chat with you. I want to get your respect because I think it's completely changed, it's interesting. But as an entrepreneur now you're optimized for something different. So it sounds like a lot of product management going on really early, really fast, a lot of iteration. You're funded by angels and friends in the network so you have a good advisory funders or backers and three, the role of the community. These are new dynamics that are accelerated in the front end, all kind of going on at the same time. Just react to that and share what you think of that, those dynamics, any examples, do you agree with it and how important are they? So let's see, I think in particular community is one of the most important things and it's not just paying lip service to that but I believe the community has been very empowering for the end users, the developers, the people everyone really cares about. It definitely impacts us as to how we build for it. Having empathy for other people, a lot of those things make a very significant difference and community is something that we start thinking of first. Even when we were instilled, we wanted to make sure that no matter what we did was- Define community, open source community, customer community, peers, there's a strong overlap between those things right now. Our peers, our colleagues at different companies trying to tackle the same space are part of the open source community, a part of the cloud native community. So I think when you look at the Venn diagram, there's actually a very large intersection in the middle. So all of those really are more, have come together a lot closer than they used to be a few years ago where open source was different from commercial vendors. No, there's a very strong mixing and the thing is how do we move the community forward and that's also how we think about things here. And so that's a very big thing. The support system around you and in particular, it's amazing in the Bay Area, Silicon Valley, I've known people working in different places trying to get companies off the ground. The support system is amazing and not just for our investors, but the number of people that have no financial ties to us, have no vested interest in us that benefit and help we've gotten from them has been amazing off the charts. Well, I got to ask you, Niraj, I mean Silicon Valley is supposed to be like the cesspool is the worst place on the planet, it's evil. You're obviously an example of what's going good in Silicon Valley. Cher, in your opinion, if people ask you, hey, what's going on in Silicon Valley these days? Is action happening there and what's it like there? So it's a good point to make, right? We see a lot of stuff in the press and a lot of the articles are not complimentary and I'm not trying to say that those aren't real problems but I'm very glad that we are talking about those problems and we're diving into this and we're making sure that the next generation of companies that emerge hopefully do not suffer from that, right? We care a lot about that at Casten. We've built a very diverse team, even though it's small right now, people that underrepresented and I've always had that history of doing that even in the previous groups I've led because it creates for stronger teams. I see people, more people getting, being aware of the challenges being faced and we're working together to also go solve and address some of this. So this is one of the things where you can't throw the baby with the bath water but we have to figure out what's wrong, what isn't working, go work on fixing that while retaining the things that have given the valley a unique edge and I'm very proud of being a part of that. You could lead by example rather of being a social justice warrior throwing mud around and obviously highlighting what everyone already knows of being aware of it's something that we've been promoting and it's also too humanizing it, making it human and having proper conversations rather than people putting their head in the sand or running from it, running from these problems. Okay, so I got to ask you on a personal question. We're kind of older, you're a lot younger than I am. Obviously you can tell that difference but there's a lot of great young guns coming up. Men, women, all kinds of great talent. They're coming in, they don't even, they don't know what a local host is. They don't even know what, they've never installed a patch. A new set of programmers, developers, artists, creatives are coming into the software business, changing the game because it's really interesting. Dev Ops is happening. What's that culture look like in your observation when you recruit people, when you talk to people? What are these young developers interested in and what are they good at, what are they gravitating towards? What are some of the observations you could share? So sometimes there's also, you know, there's overlap between young developers and millennials and sometimes I believe millennials get a bad rap. When working with those communities, I see a lot of enthusiasm, a lot of passion, a lot of ambition. I see a lot of community driven stuff. They care about how they make an impact outside of the particular role they're playing and I think those are all things that it makes sense for companies to help enable as well as leverage. So when we see these new breed of developers coming in, I think it's about, you know, if someone doesn't want them, please send them my way, more than happy to take them because they're just so passionate about getting stuff done. What are they coding and what language is they, can they write lines to see, are they writing in C or are they, what language is they programming? So the way we look at it as a problem is I think programming language is a secondary. They worry about what does it take to get the job done. So they're adaptive. Yeah, exactly, right? So when you talk to them just because they don't know what local host means to it, doesn't mean they can't pick it up. If they discover they need to figure that out as an example. So sometimes they'll come at it with other higher languages focused but then they will quickly adapt to either new different styles that they really want to learn to or they'll adapt to new programming languages, right? So to give you an example, in our company, we use Go as an example. It's very popular for especially for doing application infrastructure focused on. But the majority of people when they came in did not know Go as an example. I think maybe one person was really well-worse with it and the rest of the people just picked it up because it was the right tool for the job. They learn, they learn the basic data structure and they can jump in. It seems to be something that they pride themselves on. Be multi-code, multi-coders. All right, another personal question for you to end the segment. If you could talk to your 23-year-old self now, if you were 23 now knowing what you know, what would you tell yourself right now? Does motivation, observations, rules of the road, how to be successful, what would you say to your own 23-year-old self who's coding away all those great opportunities? Oh, I know very well what I would tell my 23-year-old person because I've learned it the hard way, right? So, I came out with a strong technical background but I think what I tell my 23-year-old is concentrate on two things. That is concentrate on the soft skills which will really, really help in terms of making a greater impact on people around you, on the industry, no matter what it is. Involving the communication, leadership. We've talked about community. So the soft skills that help you leverage that and optimize for growth. And this is something people sometimes tend to fool themselves about. Personal growth in particular, right? Where people tend to fool themselves where they get comfortable in a place and they're like, yeah, I'm learning but in reality, I think taking more risks, taking more chances, making sure in an environment that you can learn from people. And this is not about small company versus large company, just to make it very clear. Always be learning. Yes, always be learning. And I think those are the two concrete things I would tell myself. I would also tell myself to move to the Bay Area but I already did that. Because of just being in the technology space. And raising money. What would your advice be to yourself? How's he doing a good job right now? So raising money, start five years before you want to go raise money. You don't want to show up at someone's door and ask for money. And that'd be the first time you interact with them. Because, and this is about being genuine. This is about being authentic. But it is about making sure you build those relationships. People have a chance to know you. People have a chance to see what you've done. And being a part of that ecosystem I think will really help when it actually comes on to you wanting to do something. And that has really helped me. Yeah, and the other advice we hear a lot in theCUBE is the successful entrepreneurs have paid it forward. Yes. They always are giving back. And always be learning. Great to have you on theCUBE. Great to be here. Neeraj Choliya, co-founder and CEO of Castin. Hot new startup. You getting a new round of funding? What's happening? You want to announce that here? Or is that happening? We'll talk again in a few months from now. I'm sure you got a lot of easy and nothing to do. A great, great success in the hot space. Cloud native. It's the hottest market in cloud computing. As we all know, what's going on in cloud. That is really, really shaving up to be a really, really big market. Real impact across the board from data analytics, application development down to the infrastructure and creating new opportunities for wealth creation and innovation and invention in AI, entertainment. You name is happening. This is theCUBE conversation here in Palo Alto. I'm John Furrier. Thanks for watching.


Good morning, president. Welcome to Camp David. Sir. Yes, sir. Good morning. Good morning. Welcome to Camp David. And I think it's especially important that we move the economic summit of all nations, just as spring is renewing nature. We can renew a lot of commitment, a lot of relief, and a lot of extra treatment, a lot of trade. Our cooperation and defense and foreign policy have never been closer. We've still got an air of frustration some of our business circles and in our conference. We recognize your own role in moving Japan's economic system to one more and harmony with the global economy, and appreciate the tough steps that you've taken. I hope the opportunity for a historic shift represented by the NACAO effort can be realized and we want to help. If I think myself and my party can play a bit, all of the Japanese people are very grateful for this invitation. I would like to convey to you, Mr. President, that I would like to convey to you, Mr. President, the verse of his Master. This is another thing which I think you should open because before we walk up there I'd kind of ask you to put it on. Thank you very much indeed. I'm going to ask it open because I'm going to ask it aware of how we walk up there so we can get a photo of that. May I open it? Yes. Thank you Eddie. Very nice one. There. I hope it's yourself. Thank you very much. I must recall the result of my golf. Golf squad after using that. The name is written on it. The name is written on it. I see. Thank you very much. Which one is this? This is a TV pocket. A TV pocket. This is a TV pocket. This is a television set. Please open it. The smallest one in the world. Well for heaven's sakes. That ought to get me through a lot of dull cabinet meetings. I'm going to try to think about it. That's the one in the back. That's the one in the back. It's wonderful. That's the one in the back. Wow. I didn't think it was ready to work already. What channel do we have here? The basketball game. The basketball game. Watch them in Philadelphia. Watch them in Philadelphia. Now it's a tennis match. How do you turn it on? This is Darian. Huh? The window behind it makes it kind of ugly. Beautiful color. What size of batter are you using? Full batter. Very nice. He can turn you off. I'm going to listen to it before I want to hear it. Number three. That Japanese guy in the ice cream shop. Here. Let me know if that kind of thing will invade you. Ask me to convey. Use TV tomorrow. It shows better. That's something. I've never seen anything. I have just said the wrong. I'm afraid that this kind of thing will invade your market again. I understand about her son. Yes. I'd be the same. The election of House of Constraints will be held on the 22nd of June. And she's very busy. Yes, yes, yes. The Japanese cake ball. I have to tell you, one lovely thing about Japanese gifts. Are the boxes? It's going to say the box. Yes. No matter what's in the gift. And the way it's wrapped. The box is so beautiful. Pretty. Isn't that pretty? Oh, look at the inside. Yes. Can I have the box? Thank you very much. It's just beautiful. Thank you. Thank you very much. It's lovely. Yes. It's just beautiful. Thank you.


What's going on guys welcome back to the channel critical overload here so I'm gonna talk about a few different horror topics in this video here today We'll be talking about scream 7 which is gonna more or less be a theory this time around We'll be talking about Chuckie season 3. We'll be talking about saw X We'll be talking about the exorcist believer and we'll be talking about this lawsuit that is going on between one of brothers and Bonnie Erin's who plays Valak from the conjuring universe now just to start it off with scream 7 Scream 7 could implement a variety of different things one thing that's still on the table is this cult Narrative possibility of course that's been around since the talks of scream 3 and what was canned and scrapped and what What originally was and what they didn't make it into the final cut etc And now of course we have caught like things being teased in screen 6 more more than screen 5 definitely in screen 6 Where you have these two people at the start of the movie who were taken out by the Baileys Greg and Jason? I'm starting to wonder What if scream 7 kind of loops in a connection between those two Greg and Jason and Amber and Richie from screen 5 What if Amber and Richie from screen 5 actually Interacted with Greg and Jason online and unintentionally not knowing knowingly to them they inspired a subsection of stab fans To have like their online little cult if you will who have a desire to finish Richie and Amber story Reason I'm thinking of that is because of the fact that that woodsboro truth or group that makes a brief Appearance in the opening of scream 6 well after the opening when Sam is at her therapist office at Dr. Stone's office we see these images come across her phone of Richie was framed and it's on the woodsboro truth That's the name of the reddit page on her phone that reddit page in that group is still up It's still active not a very popular group But it just got me thinking how much of these posts that I'm coming across will actually make their way into scream 7 One post in particular is I've heard that those dumb ass producers are making Richie and Amber the killers in stab 9 So in scream 7 are we going to see a stab 9 in Development perhaps and then another post on here says since stab 8 was shit Who wants to be my accomplice to fix the franchise and finish Richie and Amber's film and then down in the comment section I'm seeing people saying they should go after these producers and make them pay You know they don't take the fan seriously obviously a nod to their leader Richie so what I'm getting at is in scream 7 what if Somebody who does not have a passion for stab who does not have a passion for the constant exploitation again I've said that my idea for scream 7 involves somebody who just simply wants all of this to end what if somebody infiltrates these groups of Course enlist some accomplices Deludes them into thinking they're on their side in terms of what they want They think they all want the same goal now They all want these survivors dead, but they don't all have the same goal this person who is manipulating these stab fans this cult of stab fans Thinking that they're gonna send a message and finish Richie and Amber's film They think that they're that they're I'll say supposed Leader if you will because this person I'm thinking of who's infiltrating the group has become their leader of sorts They think that this person is on their side and has the same goal This person's actual goal is sending a message to Hollywood that they need to stop the exploitation That stab 9 doesn't need to happen in fact No other stab movies at all need to happen and they want all of the survivors dead because they think that as long as these survivors are alive The chances of a new stab movie or the chances of more exploitation will constantly just continue to exist because somebody seems to always find a Reason to come after you guys and be upset with you They view themselves as someone doing the world a favor a vigilante of sorts Like we kind of had teased in scream six but have that come to full fruition in scream seven Also, this person can be someone who knows that Christina Carpenter had something to do with the initial Woodsboro incidents involving the death of Marine Prescott and she knew what Billy and stew were doing in 96 And yet she did nothing so they could actually want to get back at her and blame Christina and her silence for as to why this Exploitation has been going off for so many years and why the stab franchise exists beyond just the producers and the filmmakers because Christina silence was aiding in the source material being provided to these greedy individuals that this Main villain main ghost face of mine can't can't stand so they're Manipulating these stab fans. They help them track down the survivors They basically let them do all the dirty work for the most part not that this person wouldn't kill anyone But they're letting all the staff fans do all the dirty work and then by the very tail end in the movie when there's maybe Two fans of this cult left because I'm thinking of maybe six max with a seventh person being the main person I'm thinking of is who is not actually having the original goal is them this person Takes out their remaining members takes out their partners double-cross them and gives their whole spiel to our remaining survivors And then that could be scream seven that could I could see some of these posts in the woods Bro truth are just coming into scream seven. I just wanted to share my thoughts on that with you guys as a brief theory I know that was a little long for an intro to the video, but now we're gonna dive into The rest of these topics here. So I've seen you guys Go on about when will Chucky season 2 be available on peacock Apparently according to peacock as they put out this tweet They put out a tweet saying that season 2 comes to peacock on September 4th Season 3 again confirming is gonna be available next day on peacock starting October 5th So we know season 3 again debuts October 4th and is going to be available next day on peacock and season 2 now We know will be available soon for everyone to catch up before season 3 airs It'll be set in DC and episode is expected to be in jail. Nika is hunting Tiffany We know is gonna be probably a factor of the story based on the conclusion of season 2 Mrs. Fairchild seems to be someone to expect back as well based on the ending of season 2 Four episodes are likely to be airing, but if I hear anything different, I will let you guys know Also, we got this cool poster of Chucky season 3 with the with the taglines this fall He's running for your lives and it's a pretty cool poster No, it's Chucky up on the podium like he was in the announcement video So we'll just have to see what Chucky season 3 offers us later this fall diving into This scenario with the nun now apparently one of brother's discovery has been accused of short shorting body errands Her share of merchandising revenue for playing the demon nun in the conjuring universe This is coming from the Hollywood reporter the complaint names warners new line cinemas and scope productions Which allegedly entered into an agreement with errands to play the nun in the franchise? She was paid 71,000 for her role in the nun which grossed over 365 million against a budget of 22 million according to the complaint her contract included a $175 bonus tied to box office performance on top of a share of profits from merchandise exploiting her character instead of accounting and pain in a transparent fashion Warner Brothers obscures and hides the true amount of Mrs. Aaron's Rightful share of merchandising revenues all while continuing continuing to exploit her states to suit file Tuesday in Los Angeles Superior Court now Here's my my comments Bonnie might be the best thing about the solo nun projects So screwing her over is simply unacceptable And of course this coming out on the verge of the release of the nun too while I don't expect it to harm the box office Anyway, it's just very Peculiar that this is coming out right before something that again based off what I know I expect to fully be a completely shit movie Narratively but it will probably save itself based on its own visual aesthetics and the performances that are helping keep the shit shit sandwich afloat I'll say but that was an interesting bit of news to come across this week Hopefully Bonnie gets everything that she's old if all of this is indeed true So diving into saw X the saw X trailer seems to confirm a death already If you dissect it close enough and shout out to you Patrick Burrow if you're listening to this for this Amazing fine. If you don't want spoilers then shove off for a minute or so and hop back in to get the other update Paulette Hernandez's death by decapitation is teased in the newly released TV spots But it doesn't look like she makes it out alive because in the trailer. There's actually a shot of there's a shot of a Surveillance footage camera where John is using and it would appear Paulette is on the ground without a head Because the clothes on the individual in the surveillance do appear to match up with Paulette Now, of course, I could be wrong, but I thought it was an interesting fine Now another could another cool thing Patrick highlights in the TV spot is that Amanda's role may be her getting her feet wet With her first game before the events of saw 2 because I just Remembered this is taking place after saw one So we could be seeing her getting more involved as opposed to how involved she was with the first events We saw in the original saw we could be seeing her kind of guiding these new victims and Helping them in a way because you can hear her say She'll be okay as long as she keeps her head straight or something like that. So when you see Amanda's first game Post her own survival in the bear trap should allow us to see a fun dynamic between her and John Also saw space is still reiterating that a scene in saw 6 is probably worth checking out once more When it's a scene that I've talked about where John is having a conversation with one of the folks involved with his insurance And they're talking about something in Norway, which seems to again be what inspired the events of what we're going to see in saw x so Diving into this last thing here is a brief topic the exorcist believer once again the exorcist believer The movie that I again am also expecting to be quite terrible narratively But it might save itself thanks to some of its visual aesthetics some of the performances and some other components that I Will probably get a credit credit for like its score if it's able to be Bone-chilling in a way this movie is having yet another test screening on Tuesday in Las Vegas now One of the people who actually watch my channel they will be in attendance for this test screening So they will be chiming back to me to let me know if there's been any reshoots or anything So I look forward to hearing if there's been anything changed from the movie since it's last screened if there are changes, I will let you guys know if there have been changes and Kind of tease what they may have been because I know there actually was a post that came out that I did link in the description of One of my other videos Highlighting some key differences that I know wasn't what I was initially told plays out in the film So I'm curious if this was really a recent cut or it might have been a previously earlier cut that this person saw that got completely altered because There then was someone on Twitter who chimed in saying that they had seen the movie But this person has been outed or referred to as an online troll and a lot of people don't really trust them So time will tell what I hear on Tuesday when the ex is believer has what I can only assume Hopefully is this last test screening before it comes out in October Let me know what you think about this down in the comment section below if you haven't already of course Make sure you subscribe turn on post notification at numbers video in the description. I'll have links on my social media accounts I am on Facebook Twitter and Instagram you can message me there Of course, I'm as any movies news or reviews like me to cover in the future and with all that in mind guys I will see you in the next video


I'd like to call the second annual or a second regular meeting of the 2019 2020 council meeting to order. Would the clerk please read the quote for the day? Setting goals is the first step in turning the invisible into the visible. Thank you very much. Would the clerk please call the roll? There are 10 present. Thank you. Please stand and join me in the Pledge of Allegiance. The republic for which it stands, one nation, under God, indivisible, with liberty and justice for all. Next item on the agenda is approval of the minutes from our first meeting. Alderperson Wolfe. Thank you mayor. Make a motion to approve. Second. Thank you for that motion in support. Is there any discussion on the minutes? Seeing none. All those in favor, please signify by seeing aye. Aye. Opposed? Motion passes. Next is mayor's announcements. Well first of all, happy Earth Day. And remember it's not a day, it's a movement. I hope that we will consider some of the opportunities the next couple of days to celebrate Earth Day. We have a residence water challenge for water conservation going on. And we're asking residents to go to mywaterpledge.com to participate in the online pledge. And Sheboygan is currently in 14th place of the cities and the nation in our population division. So I hope you'll take some time to do that. Also, Arbor Day program is scheduled for April 26th. It'll be at 1030 at J.C. Park. And it'll be celebrating Arbor Day and the city receiving Wisconsin's first 41 year tree city USA recognition. That means Sheboygan was the first Wisconsin community to meet the guidelines set by the Arbor Day Foundation and has continued ever since. And then we also want to promote drug take back day. We want to get pharmaceuticals out of the waste stream and get them off the market. And the Sheboygan Police Department, St. Nicholas Hospital and Walgreens will all be participating in this program on April 27th. And then we also want to remind residents that very soon on April 30th we'll end alternate side parking rules for the winter. And I want to thank the residents for their understanding with the extension of alternate side parking for one additional month. During this time the street sweepers were able to get a head start on cleaning up the debris in our city streets for the winter season. And in 2018 the Department of Public Works street department sweeping operation disposed of 23.2 tons of debris from these operations and logged 5,069 miles during the year. If you'd like to get more involved you might want to consider getting a group together and adopting a park or adopting a trail. The adoptive park and trail programs are spearheaded again by the Department of Public Works. And you can contact their department to get more information on this program. Last year we launched two new pilot projects, the adoption of Moose Park and a portion of the Shore Footland 400 trail. And then there's many other events going on I think mostly on the first Saturday of May. There's some beach cleanup programs that are going on with some of our neighborhood associations and other groups. Other events that are coming up are the Sheboygan Police Department is providing free violent intruder active shooter training. This is going to take place April 24th from 6 to 9 o'clock at Sheboygan South High School in the LGI room. And you should contact Sergeant Andy Cuttinger in order to RSV for that program. And on Friday May 3rd is National Day of Prayer in Sheboygan. Residents will gather at noon at the Faulton Park United Methodist Church to observe this day of prayer. And it's just 42 days until we move back into City Hall for the Common Council meeting on June 3rd. Next we'll move on to item 1.5 confirmation of the Mayor's appointments to standing committees. Pursuant to section 272 of the Municipal Code, Standing Committee assignments are made by the Mayor on Tuesday April 16th and subject to confirmation by the Fault Council at the Monday April 22nd meeting. The code further states that the Mayor's responsibility is to make assignments that will best serve the interests of the city of Sheboygan. To assist me in that process I asked the council members to rank their committee preferences. I made every effort to take those preferences into consideration in the Standing Committee appointments that I have prepared for tonight and present for your consideration. Under the Municipal Code each alder person shall be appointed to at least one committee but not more than two standing committees. In addition to the list of appointments for the standing committees I've shared with the committee preferences and the spreadsheet of the rankings of all the alder persons. I'm pleased to report that eight of the alder persons received their first choice and two received their second choice in a committee appointment. I trust that you as Common Council members will agree that these committee assignments and leadership selections along with the elections held last week will position the City of Sheboygan for a successful 2019-2020 council year. Alderperson Wolff. Thank you Mayor. I make a motion to confirm. Second. Thank you for that motion and support. All those in favor of confirmation please signify by saying aye. Aye. Opposed? We'll consider that an unanimous vote. And then we also have item 1.6, confirmation of Mayor's appointments to special committees, boards and commissions. Alderperson Wolff. Thank you Mayor. I make a motion to confirm. Second. Thank you for that motion and support. All those in favor of the confirmations please signify by saying aye. Aye. Opposed? We'll consider that also an unanimous vote. Next item is adjournment. Alderperson Wolff. Thank you Mayor. I make a motion to adjourn. Second. Thank you. All those in favor of adjournment please signify by saying aye. Aye. Opposed? Motion passes. Okay our next meeting is scheduled for a quarter after the hour and we're going to have to wait till quarter after to convene our special council meeting.


So RubyConf, I must ask you a question, is the title of my talk?  So, okay, boom! And we've already gotten the first curse word out of the way. My body is a big betrayer, but I guess it's just not going to betray me this time, which is kind of a betrayal, right, asshole? Okay, so we're going to start strong now. Years ago I failed my PhD exams twice. How's that for starting strong? And then I really, but I really wanted that piece of paper. I worked years to get the piece of paper. So I bought a PhD from a diploma mill from a sort of a semi-accredited university. And so I do have a PhD. It's on my bookshelf at home because I'm not really proud of it. I don't even post on LinkedIn where I put all of my really important certificates. And that, by the way, in the background is Tara the Goat, which it's not a coincidence she was named after me and she's awesome. But I clearly take LinkedIn very seriously. But back in the PhD years, my first mentor, Jim Schiff, who really ramped up his efforts to get me passing the exams after I failed them horribly, he helped shape my understanding about how I learn, how I process information, and how I communicate what I learn. And he said to me, this is the first new goat. He said to me, Tara, you like to walk around the barn before going inside. And that really sums up how I learn and how I approach different things. And you're all kind of discovering this during the talk as well. We're sort of walking around the barn. But that description has been essential to my understanding of how I process what I'm trying to learn or can't seem to learn. And one of the reasons I'm giving this talk is because I struggle with grasping concepts more than the average person. And this is a talk about learning at all levels. We're always learning. But at least in terms of how we mentor or more informally, often peer-to-peer how we mentor or are mentored and how we learn about ourselves is what I'm going for. My problem with learning was really brought home to me again during coding boot camp. We paired with new people every single day. And we organized our way around the room such that we started with like the slow, people who wanted to go slow were at one end of the room and the people I called the golden children were over at the other end of the room. I was like hanging out by the windows over there as far as I could get. It turns out, of course, that some of my perceptions about what people knew or didn't know was wrong. But I did, I got a clear impression from all of the different people I was pairing with that how I was learning was very different. I was making progress, but it was very different. And I want to emphasize that while there was progress, that knowledge of difference can do a real number on a person. And I don't want to make this a talk about things that you can't translate into your own experiences. So you're just going to have to trust me when I say that the struggle was real and it was beyond the norm. So I'm just going to stop for a moment because I'm going to tell a lot of stories so I figure I may as well make some actual points that you should learn how you learn. It's essential to learn how you learn and it's helpful if you are helping someone else to learn to help them figure that out. But ideally, you'll learn how you learn so that you can communicate what you need. I wish I could go back to those PhD exams. I feel like I have a better chance of advocating for myself and explaining to my professors what I would need in some different test taking strategies in order to succeed. But I can't. So I want you to learn how you learn so that you can communicate that with others. And then learn how you don't learn. Fail a whole bunch of times. I am very good at this. As you know, you go into code and you fail a whole lot trying to solve different things. It's the same thing with learning how you learn and what failed for you one time might succeed for you the next. And so you really do have to try a variety of things in order to sort that out. And I mentioned this specifically in this talk because I think when you work with different people and you're trying to mentor folks even informally, you really need to learn to look for a variety of different ways that they are learning as well and kind of modify what you're doing when you can. And then even though some of your colleagues might attend a talk on being a good mentor, you are really the person vested with the vested interest in learning.  It's my responsibility now to take that and communicate that with others and figure out how to make up for my weaknesses in learning. And I want to make a distinction between what I experience with my slow learning and imposter syndrome, which I also have because I fit somewhere in that circle. A key point from my PhD exam failure example is that I'm a real misfit when it comes to learning and communicating what I know. And I realize that everyone kind of thinks they're a special snowflake and I am, but we all are. And that's why we all think that, but I want to make sure that my own failure is really clear. I'm not sure why I want this so badly, but I do. I want to make sure that you understand my failure, that it was beyond the norm, because prior to me failing my PhD exams, only one other person in the previous decade had failed the exams. And he admitted to taking a nap during the timed exams. And then filed a grievance and was allowed to write his dissertation and continue. And I'm not bitter in the slightest. I'm bitter, but I mean this was big. And I have a large monthly payment that reminds me on the regular that I don't learn like other people learn and how I learn can be expensive. And my story gets worse. Spoiler alert, the reason I'm sharing this is that it isn't this dire for most folks. And I hope that's encouraging. Even if things are this dire in similar or different ways, one can still succeed. And I say that from the stage of the national conference for my primary programming language while gainfully employed. So that's my evidence of you can still succeed. That's all I got. I really like you people. OK, also I want to make sure that we have a common understanding of what I mean by the concept of being a rubber duck. By the way, my friend Robin drew this. She also designed the Goat User Story stickers. And it's so much better when it's not in VGA. You're just going to have to trust me that she's really talented. So if you need a graphic designer. The idea of a rubber duck, I believe it originally comes from the book, The Pragmatic Programmer, where Programmer is debugging by explaining the code line by line to a literal rubber duck. And that meaning has come to mean different things as things do. But it usually involves something inanimate or, say, someone who doesn't provide technical knowledge to the solution. Many ways it's used now, you might start an email or a Slack message to somebody and you solve it simply through writing it out to the person. So in that ways, they're kind of inanimate. OK, back to It Gets Worse. As I was saying, I have a new job recently and I am trying to learn a ton faster and not be found out as a learning misfit. I wrap up my day and then I start reading code books. I'm taking online courses. I'm watching YouTube videos about coding. I'm trying to grok all the things at once. I'm also learning a new programming language, so that's part of it. But my body is a betrayer. I don't know if this is true for everyone, but my body is. And it's like the more I try to keep being a learning misfit a secret, the more my food issues flare up and I gain weight. And I mean a lot of weight. I'm really good at that. It's as if by hiding my misfitness, my body makes me confront not fitting in a physical way.  So now I must ask you the most obvious question.  And I am, in a small part, I am using you. If my own beliefs about psychology and how it's connected to physiology are correct, then by confessing my true fears of being found out as a learning misfit by putting those out there, I'm hoping that it might solve the problem. That because I'm actually very good at losing weight when I'm not struggling with these things, and you're basically all being my rubber ducks right now. I realize you're not inanimate, but just as being part of an audience and not necessarily a dialogue with me, you are my confessor, rubber ducks. I'm Jewish, by the way, which is why it's a rabbinic duck and not a priest duck. So you are all being my rubber ducks right now. And the theory for me is that once this is out there, once I am explaining the problem to you, that the solution will be okay. Like I have confessed this thing that is really difficult for me, and that hopefully will free me after I have a proline, I want one proline, and then I wanna be freed from the sugar, just one. That's all I want.  We're all vulnerable meat sacks, and we might have come to this room or this talk for different reasons, but a key reason that I'm up here is so that you have knowledge, rather than just information, but knowledge you know from me how important smoothing the way for somebody else can be, somebody else who's dealing with outside the norm struggles or even inside the norm struggles, because again, we are all vulnerable meat sacks. So beyond the career related practical reasons that might be a good reason for being a good mentor, I'm hoping to appeal to you on that level. You might not put on 50 pounds every time you're under a lot of stress and trying to hide your learning mis-fitness because you might not have any, but we all need folks to support our efforts and to support the efforts of other folks, and I'm hoping that you will do this because I am why this stuff matters. You are why this stuff matters, and we are to borrow the name of one of my favorite podcasts, We Are Greater Than Coat. We Are Why This Shit Matters, and within your own boundaries, I want to be up here suggesting that you try to facilitate other people learning and growing in their careers, and I'm not saying you have to go in and fix people's food issues, but if you can ease the way in your career with your colleagues and that kind of thing, that can help them deal with the other shit that they've got going on. So I started with this to give you examples other than your own, especially if you don't have any, about how easing the code building process can ease up other areas. So now you may be asking, why would anybody hire a slow learning Tara? And that is an excellent question, but first of all, I mean, hopefully I'm a nice person and people like being right. I don't know how smart you are. That's it, thank you. Oh my God, I love a ringer. Thank you, I'll get you your $20 later. So as you can see, I'm a freaking delight. But really, I mean, people who experience the world differently see possibilities instead of obstacles, and that is a great trait to have when you're dealing with code. My whole life in terms of the food issues and the learning thing, my whole life has been obstacles and I'm so used to failure, I just keep going. I go back around the barn. If it wasn't ready to go in the first time, I'm just gonna go back around the barn again. I am a good person to have around. I'm gonna dig in there, I'm gonna build your feature, debug your problem, it'll be fine. Okay, I'm getting to the practical stuff now. We have circled the barn and Sonia, my first engineering mentor, she was my official engineering mentor. She paid attention to how I learned and when we paired one on one, she would ask me specific questions about the code that we were doing and the context we were doing it and she would say things like, do you understand what object.method is doing here? That was not their names, they had better names. But do you understand what object.method is doing here? Do you know why we changed that thing to do this thing? And the specific in-context check-ins helped me know that she cared about my progress and this is where the more traditional imposter syndrome comes in is that I don't even know to this day whether she purposely asked me things that I would know to instill confidence in me or did I just know more than I thought I knew? It's probably a bit of both but we just never know these things. But I got the opportunity to be Sonia's rubbered up because I really brought very little technical knowledge to the table fresh out of boot camp. But she asked questions of me that were really questions she was asking for herself, not these object.method questions but asking what she should do next. Should she be concerned about this thing or that thing? And that taught me what questions a senior engineer would be asking about their code and it was a mentoring process and even though I was in that silent, mostly silent role of kind of a rubber duck for her, I learned a whole heck of a lot. And so I think one of the things I want to give as a takeaway is that first of all, people can learn from folks more seasoned or less seasoned than themselves. So it can be any pairing scenario but honestly there is an opportunity to teach and to learn in those pairing sessions and I hope folks take advantage of that quite a bit especially if you're helping to level somebody up a bit. I want to talk about a different sort of a mentor than I had. I had a variety of colleagues who were all very good at helping me answer some of the questions that I had but I had questions that I, I call of them stupid questions and you can talk to me later about whether I should ever say that again but I call them stupid questions and they were the questions, like there were the questions that I knew like a junior engineer and newbie would ask and I asked those of across the team, you know, Jeremy you're here, I asked you all kinds of questions but what you may or may not know is that I saved my stupid questions for Daryl. Daryl's there on the right. He taught me how to rebase first of all which was very exciting. He walked me through my first rebases and he celebrated with me when I did one successfully by myself. He was not there when I nearly passed out when I did something really horrible with the rebase once but and I was literally pale and clammy and texting Carrie Miller from the floor of my apartment. I sucked in some code and something happened but Daryl was there for most of my stupid questions and here's what happened is he established trust with me with this rebase instruction and then I asked him one of my stupid questions that I knew would reveal that I should not have been hired and I asked him that and I asked him not to tell anyone that I asked that question and he did not tell anyone. So from then on I decided this is perfect.  What I want to suggest because most of you maybe already have that first job is that you establish trust with some of your less seasoned partners or heck even you're just same level of colleagues establish trust with them and develop a secret pact if you have to but it's important in order to have those special moments and those people who mean so much to you and level up your career it's important to first establish trust in order to get to that place. So here's some easy career boon mentoring and rubber ducking can have is that once I felt more confident that I had reached at least the within the norm spectrum of junior developers I confessed the pact to our boss Daryl and I had the same boss and I told him Daryl was not my mentor but he mentored me and Daryl got promoted. I don't think it was because I told but it couldn't have hurt. Daryl was very talented and so I'm sure that is why he got promoted but it couldn't hurt that he even though he was not an official mentor he mentored the junior developer on the team and I made sure that his boss knew it was career building for me and I wanted to make sure it was career building for him. So the takeaway there, I hope probably obviously is certainly you wanna show gratitude to those folks who do take the time to care about your learning and keep your secrets that you're asking stupid questions but also build trust as a potential secret pack provider. It's very important. This happened recently and I don't know if you can tell but like the VGA it's washed out but can I name you in my RubyConf talk and I get to name him as you can see.  And this is in Slack if you do not recognize it's lay out there but Brian was also a different kind of a mentor. Daryl had been promoted and moved on to a different team so I really picked the right person to tell all my secrets to because he left the team. No one was left on the team who knew I should never have been hired so that was fantastic. I had a solid footing in coding and I didn't pair much with Brian when he worked at Living Social with me. We did some SQL, some active record and we did some jQuery together but we didn't have a whole lot because soon enough the dark days of the Living Social layoffs came and we went our separate ways but fortunately we continued maintaining Slack with a lot of the Living Social employees and so Brian and I kept in touch and when I started at my new job I still had coding questions and of course I didn't want them to know I was stupid and that they should not well I wasn't stupid.  I just thought I'm a slow learner and I did think they should have hired me and I'm glad that they did but I still didn't want them to know how little I knew in those early days when I was trying to learn all the things and I was stressed out because I don't learn very well. Anyway, I would contact Brian via Slack and without sharing proprietary information of course we would discuss the things that I was working on in code and soon enough by the way he would help me and that was great but soon enough we ended up having to reach out because I was asking fewer questions and that became a milestone that I think was important for me to recognize and I would suggest that if you find yourself in a similar position where somebody is asking you questions and they start to dwindle that that's a great thing to point out to them like I don't know if you've noticed but you reach out to me less you're still welcome to do so but that's probably a cool thing that you're reaching out less you're probably feeling more confident and I was and then what happened with Brian is he just turned into a real asshole. No, that's not true it's just because he told me. Yeah, no he didn't but he stopped being able to answer my questions because I mean I'm sure he would have been able to if he'd been working on the code with me but I'd reached a level where I was now working on projects that were far enough along and asking more technical questions that I finally just sort of I could no longer just ask him a question and without us being in the same code base he'd be able to help me and that too was an important milestone and it was great he recognized it and it helped me to really acknowledge that as well that's a pretty exciting thing to realize especially when you are a vulnerable meat sack who has learning difficulties it was pretty exciting to realize that so as I've worked with developers newer than me I've gotten to try out these questions which I think is kind of fun and I literally, I pinged Slackbot to do this slide but this is what I sent to folks and you can tell I was up late. Yeah. That was actually early but I send this message and it's a pretty good icebreaker I mean it's hard not to smile when you get a mustache and an inquiry it's hard to turn down somebody who sends this and I know that because people that I have done that with have sent it back to me, I've gotten it back and it just makes me laugh and I just know this is a person I have a good rapport with and we're gonna do some mentoring no I never think that part but that's what's happening that is what is happening and okay we've only got three more slides we're coming down to it I promise so I've tried to suggest that caring about the vulnerable meat sacks that surround you might be a motivator for asking good questions and being a trustworthy mentor but also becoming a better version of yourself is a good reason a motivator to be a good mentor or a good rubber duck everyone can learn from good questions including the person asking them and mentoring can be as easy as answering stupid questions and keeping them secret I don't know if I clarified that but don't tell anybody I did eventually by the way tell Darrell that I had told our boss so that he could bring that up and it's one-on-ones in performance evaluations but if none of that human stuff motivates you I do want you to remember that Darrell did get a promotion so that's good okay one more circle around the barn back in the PhD days oh my god you cannot even see that fucking owl trust me this is a really great slide okay back in the PhD days I took a few feminist theory classes and that shit bored me to tears I still don't really know what was happening in those classes but the significance was totally lost on me I didn't know why it was important it made no sense to me this is maybe why I failed the PhD exam no the actually women's studies was not one of my areas of concentration so it was fine but I never could have imagined that joining the tech industry would teach me so much about feminist theory and lest you think that I am going somewhere else with this it's this community especially the Ruby community from what I can tell from the various conferences I've attended and people that I've talked to but it's this community that's taught me to see commonalities alongside difference to learn better communication in the presence of difference and to appreciate difference and a series of mentors both formal and informal have helped me level up to a place where I get to learn more about my betrayer body and then reveal it to a large crowd of folks in the setting and most of all that being able to appreciate difference is so important to me and you have all inspired me to share what I've gotten from you so that I can return it all back to you and so I'm sharing this because I want you all to keep this shit up and in a more conscious ways even than you have already and expand on it and grow because it has been so life changing for me I'm eternally grateful for it and you give me hope that we can all treat one another in a way that honors our differences rather than hiding them and I'm extremely grateful for that. Okay, I've shared some stories I've offered some specific questions to ask of others and of yourselves and I hope that you give your best for yourselves and for those around you and I am again deeply thankful that you have all been my rubber ducks at least for a half hour or so so thank you very much I have no idea if I have time for questions and I don't really have to dash but I do have stickers there if anybody is interested in those and I do have a question if nobody else has a question by the way I'm totally blind up here so you'll have to say something if you have a question You have about 10 minutes Oh, I have 10 minutes Okay, I'm gonna start because I've already got the mic Yay, I do have a question because I thought of this far too late and some of my slides don't translate well for visually impaired folks but I went to a slide share I think and I couldn't add captions or anything to my slides and if anybody has a tool that they know where I can post my slides but add captions to them so that people who can't see my awesome pictures like none of you could see the owl then that would be great if you might tweet that at me my, oh my gosh, you can't even see my Twitter account Excellent, media remedial is my Twitter handle and thank you Jennifer so that was my question Are there any others? That is a really good question especially I am considering I think most people have heard about mansplaining before and nobody should go there I think one of the best things to do is to put the, how do I put this? There's a balance of power and there is a power structure that comes into play with the more seasoned engineer and the not a seasoned engineer and that could be just in say this one particular scenario and I think a great thing is to put the action and the power for that action in the other person so even just asking a question I'm a big fan of questions just let, you know, I know a bit about EmberJS components would you like to talk about that or some question in that way and I'm more than happy to hear from other folks in the audience who have ideas but for me asking a question and asking whether they want that assistance is a great place to start certainly do not start with well actually I don't care who's involved in the situation don't start that way I was gonna try to recap it but now you've lost me and I noticed you flailing but I was gonna recap it a bit for the video presentation but we were asked how do you know when to step in and one of the suggestions from the back of the room that I can't see was that you ask what the person is doing or how they're doing and they can explain what they're working on in a very neutral way and then they will as you mentioned get to the part maybe they'll just get to the part where they're flailing about right you don't actually have to say that and that the shout out right before that and what you've said is great I'm kind of gonna recap it a little bit which is just that on the one hand if you're asking what they're working on and how they're doing it then you might just end up being a rubber duck they may during the course of explaining it figure out what's going wrong for themselves or as Betsy points out where they are struggling might be due to how they're understanding what's going on and because they're explaining to you in the way that they understand things you might get a clue on what they actually might need some assistance on so that's excellent thank you I really like having Sam in a meeting so the suggestion which I'm repeating for the sake of audio is that if you have an opportunity you see someone you think might be struggling in a particular way and you are willing to do it ask the question you think that they want to ask but might be a little nervous about asking and that also I think builds that trust as well even if they don't know for sure that you did that on their half they know you're a person who has similar questions and that itself can build a bond so I think that's great how much time do I have left anybody know there's like this huge okay I'm done yay I lived woo