 Hi Ashwant, let's start with a little bit of work yourself, but you would not know. Can you introduce yourself, who you are and what you're doing? Okay, so my name is Ashwant, I work as a principal engineer at NDEX. I'm basically a developer and I like code for work and I have a lot of interest in operations, like how my code actually works in production and what both behind the scenes to make it work. So that's how I entered into this whole operation space before it develops. That's what I do. So I talked about NDEX, so NDEX is a data as a service company. We crawl and collect products that you find on save the cards, and after you'll target whatever, Walmart, and then we sort of normalize them, classify them, and then catalog them, and then give that to work NDEX. So that's somebody who wants to work with product information. NDEX is a data source that you can work with. So that's basically what we do as a business. And where are your clients basically? So predominantly most of our clients are from US. We do have some in India. We're very small, we're just expanding the whole catalog in India space. Great. Can you tell us a little bit about your background and how did you stumble upon your current job role at NDEX? Okay, so I did my data computer science from Shasta University. And then I landed NDEX as my as graduate, just after finishing my college at John's NDEX. I started off as being a software engineer, worked on the whole big data system, working with jobs, working with large amounts of data. And then as I started working with them, I realized that there are a lot of things that goes behind the scenes that we take for granted. And sometimes I get these prudious errors that is an out of memory that happened, or a GCO that didn't happen. And you really don't know why. I mean, at that point in time it was early in my career. And I was fortunate enough to have a very good team of mentors. Actually it was a team of mentors because I was the in-guest full-time employee at NDEX when I joined. So everybody who I worked with was very senior. So I learned a lot of stuff from them. And then when I realized that operation is something that I really found interesting, NDEX was also helpful enough to be an opportunity to work on that space, to contribute to the company. Challenges that come with the show? I mean, the being in... Okay, I'm not a first-class operationals engineer. I don't work in operation space. But as the culture at NDEX is that even if you are a developer, you need to take care of your operations. The one thing that you will learn is generally when I was in college, I was all about writing code. Can I get this outcome? Can I get this output? Can I make this page more prettier? That's basically what you work on. It's what you focus on. And you don't really worry about how does something like Google work? How does a system company like Twitter or Facebook work? They have also HTML and CSS for you. But there are a lot of systems that go behind the scenes. Now, if you're really passionate about learning, you don't just want systems. But how also they operate? Now, it's very easy to say it was a database to solve, to store your blocks. It's very easy for you. What do you... I need your database. I'm not saying you need to write a query and stuff, which is a good thing to have. That's what DB here holds at fault. But what does it mean to maintain a database? What it means to have a backup in place for a database? How do you keep replicas and things like that? What goes to make sure your production... I mean, as somebody, if you're working with, say, Twitter, you're using Twitter or Facebook, and then you suddenly see they don't open up, the first thing he goes is at down.com and then check the Facebook.com or Twitter.com to check if it's really down or not. And there are people who work day and night and put in wrong hours to make sure that doesn't happen for users like us. Now, if you are interested and passionate about stuff like that, now that's how you sort of get into understanding what was being in the scenes and then you get into these whole operations in this place. Got it. So, should you also act there in an order of community, like tech communities, some of the sort of gender, like the local gender group and the gender and tech community and such? Can you tell us a little bit about why people should even get involved? You know, they have a job, they're doing their programming, they're coming back home, they're sitting, spending their time, they're having a lot of fun. Despite that, some of us put in, I think, recently a lot of time and effort to promote the events, to speak at events, to organize events and do that. Can you tell us a little bit about why that is important? Personally, for me, I participate in a lot of events right away that I can organize and be just a participant and listen to what people are saying because to me, it opens a perspective. So, I mean, I work at a startup and I'm exposed to a bunch of a problem space that I get to work on and I have enough opportunities to work on that, but there are also other people in different domains who are trying to solve a similar problem probably in a different way, taking inspiration from somewhere else that you might not even know of, they are not of. Now, going and meeting, you know, it could be a small meet-ups or conferences like these, it helps you share ideas, it helps you grow as a person. To me, I mean, it's like a difference between you writing examinations by reading textbook, this is you doing your research or doing a project on your company, that's to get into that zone, the next zone of doing this if you want to do a project or a research, you need to have more additional inputs than what it takes for a service. So, that's when you come out of your circle, go meet new people, just listen to them, you can still be passive if you are starting off, I would recommend be a passive participant, just go listen to what they want to say and you can see in your community you get a lot of repetition, same people turn up over and over again for different set of things and you know, you can learn from this person and most of the times all people are super helpful, you just have to go talk to them or ask them, you know what, how do you solve this problem? And I learned a lot from going talking to people there and a lot of stuff that I do at work is not technically my own, it's just the inspiration that I got from different other people over time. So, that's one of the reasons why I go attend these meetings or talk at conferences. That's how I would recommend anybody to go to school also. Got it. Can you also, I know today has not been yet but so far what has been your team recovery at this conference? I mean, it's, my first and foremost thing is it's very nice to see there a big operational interest at conference like this, I think it's the first time that's happening and there are quite a bit of crowd, honestly, much larger than what I expected, so that's really good, which means there is a lot of school, there are a lot of people and I've seen a lot of people for the first time, so I've met a lot of people that I can go interact with, learn from, so that's one key takeaway. And then there are individual talks each of them gave me, to me it comes in two parts, one is some of it is a validation that some approaches are ideas that I follow, though I might think that maybe I discovered it, I follow it personally, if you get validated with the idea because a lot of other organizations in your exact same city know the same thing, all of them talk about resource schedulers, that's exactly what a key learning was, all of us, all of people talk about centralized DevOps, there's not a wave of scale, that was our key learning takeaway, so one thing is definitely the validation and hopefully from my talk I was also able to give some part, I mean though I didn't have a lot of time for feedback I'm hoping to interact with a lot of people post this thing, to get some feedback on what they thought about some of our evolution, to me that's, I mean it hasn't, it's not efficient take away, but I'm really looking forward to those discussions, so that's something, I think we are the main thing for today. Thank you so much for spending time with us. Thanks.