Transcript 0:00 [upbeat music] Welcome to Women on IT Hack the Future. 0:23 My, my name is Beata Jung, and today's PhD positivity hack delivered will be by our guest, Sierra Causer Inamdar. 0:33 Let me remind you, this is a grassroot community that focuses on the Women on IT, an inclusive forum of women in technology, startups, and female leaders who are supported by men as well. 0:48 And I bring heart to the castle because empathy is my mojo, and empathy is critical when you are in the world of coding. In today's episode, we are going to learn the world of coding. 1:04 Causer, where in the world are you today? Yeah, I'm in the SF Bay Area in Silicon Valley. That's beautiful location, as well as where am I- I am at the moment, which is lovely, beautiful beach just behind me, 1:22 and I'm attending a lovely conference organized by Arawak X tomorrow at 6:00 PM S- EST, which is midnight in CET, where our cohort is mainly based. 1:37 But if you join the link, you can join us because it's a hybrid event with link to the video, uh, posted later on. So let's dive into the world of coding. 1:50 The process of, process of creating instructions for computers using different programming languages can be fascinating. 1:59 With a long-standing misconception about the involvement of women in the world of information technology, an amazing Women on, on IT role model wo- is joining us today and will be providing all those misconceptions wrong. 2:16 Sierra Causer Inamdar is a senior software engineer. Whether in coding, public speaking, or coffee making, she's always striving for perfection. You can follow her on Instagram @codelatte. This is how we met. 2:34 She has been doing her part in empowering the community by giving multiple tech talks and participating in panels as well. 2:42 Causer will be sharing her expe- expertise in the world of coding, particularly in infrastructure as code, which is called Terraform, DevOps, and continuous integration, continuous delivery, and how they are vital and relevant in technological advancements. 3:04 Don't forget to ask your questions, whatever they might be. We can even give you feedback about the weather. So Sierra, let's go to the basics. What is DevOps? Yes, sounds good. Yeah. Hey, everyone. 3:19 Yeah, tha- I'm so glad to be here. So yeah, so what DevOps is, it's a way to combine, um, people, processes, and technologies for us to deliver value to our customers faster. 3:30 And you can think of it as it's kinda like this overarching kind of like principle, and there's ways we implement it. So in our... So what it's like... Okay, so you understand that it's for our customers, right? 3:41 So let's talk about what is dev and ops, right? So dev stands for development, op stands for IT operations. 3:47 So what previously happened before is sometimes you would have like development teams do their own thing, and then operation teams do their own thing, and those will work in silos. 3:56 Um, what DevOps does, that it combines the two so that you're having teams that are able to deliver value to customers faster, um, shorter release cycles, and overall helps for, um, code, uh, 4:09 better code, uh, release cycles and maintainability. That's just kinda like a high-level of, of what, uh, DevOps is. Good. And how did you get into this DevOp world? Yeah. 4:21 So, um, when I first started working after I graduated from college, um, I worked in an IT organization, and DevOps was actually like instilled in our practices where, uh, my team that I was on, we developed the code that we were working on, and we also, um, uh, took turns being, um, you know, around the monitoring and being on call around it. 4:45 So my first... So when I fresh out of college, I was more on the developer side than the operation side, and currently in my role right now, I do a mix of both, right? 4:52 Where it's actually pretty exciting because not only are you developing the code, you have to also think about, you know, okay, how can I, um, monitor this? How can I operate this? What happens in on-call situation? 5:04 So I think it makes us better developers when we have to work with that mindset. So you also make it better for you to understand what the struggles are for one role and the other, right? Correct, yes, yes. 5:17 So what was that attracted you to that field? Yeah. Um, so I've always been interested in technology as a kid. When I was little, I would watch like tech now, the tech news. 5:30 My mom saw that I was interested in tech, would buy me tech gadgets. So I think naturally... 5:35 So a- I mean, naturally I knew I wanted to be an en- I wanted to be an engineer, but when I went to college, I went in as an electrical engineer, then I switched a major a few times, and finally ended up in computer science, which I love it ever since. 5:47 Um, and so what attracts, what attracts me about, um, computer science is around the problem-solving and how you can literally like solve problem with code, and I just love how there's so many layers to it, right? 5:59 You have like the system layer, the programming layer, and it just, uh, always something new. 6:04 So it always, uh, keeps things exciting.That, it, it does feel, though, a little bit, uh, intimidating because you joined this field that is highly populated by men. How did you cope with that? Yeah. 6:18 I think what helped me is when I was in college, I did see, like, there's obviously a big, um, you know, diff- gender difference, you know, more males than females and everyone like that, so... 6:28 But I think what helped me then is I think just having my own little community. You know, like, a... I made a few friends, and then we all, uh, worked and studied together type thing, and I think... 6:38 I'm glad that overall my experience has been positive from that end. You know, people are really collaborative, things like that. And I mean, at the end of the day, sometimes, you know, you... 6:46 I mean, yeah, we do see that we're outnumbered, but I think that it's, it makes us, you know, wanna be more vocal and more out there. 6:53 Um, so that's what kinda keeps me going, and I'm happy that those that I work with are really collaborative and friendly and smart and everything, so I really like that. That's cool. 7:04 We've got Olga Vasina joining us, and wow, PhD from Nassau, Bahamas in Silicon Valley. Sunny, sunny days indeed. Hello, Olga. Hello. Lovely to see you. 7:16 So, Kawser, you sent me a couple of questions because I'm not really in, deep into technology, so thank you very much for these. Let's dive into, back into the DevOps. 7:29 There are, there's many principles, uh, in DevOps around continuous integration, delivery, deployment. Can you explain to us what are these? Yeah, of course. So DevOps is c- um, you can think of it as a philosophy. 7:46 So in order to implement that, you need the culture, and you also need the tools and processes around that. 7:52 So what, um, some practices you can use to implement, um, DevOps are, are multiple things, um, so as Beata just mentioned, continuous integration, continuous delivery. 8:03 But before I talk about that, I'll take a step back and talk about a few other practices at a high level, and then I'll dive into that, just so you have it out there. Um- Okay... 8:12 so the first thing you're gonna wanna have is, uh, version control. So, um, if you've heard of Git, G-I-T, it's a way to do version control. There's other ways of versioning your code. So what does that mean, right? 8:23 Mm-hmm. Um, so what that means is that you have... Like, let's say you write a... Let's, let's try to, like, translate the domain. Let's say you write an essay, right? And you wanna, um, make a few tweaks. 8:34 How is that r- How do you know what the previous version was? Um, you would have a version control system doing that, so you'd have that. Mm-hmm. So, um, given that, what continuous integration and delivery... 8:46 So there, there are ways to, um, kinda implement DevOps in practice. 8:50 So CI, continuous integration, is the practice of when developers merge their change to the main branch, then it goes to a CI system, which does automa- automatic... 9:01 I'm sorry, automated testing and runs a build against those changes. And once they pass, then it's officially merged to main. So, um, this is implemented in so many ways. 9:11 The main benefit of this is that developers can get o- everyone else's changes without having to do a huge kind of like merge at the end of, like, let's say a sprint, which y- you could think of like two weeks worth of work, right? 9:23 Mm-hmm. So that's the CI part. Um, so this continuous delivery is, takes it to the next step, where, okay, let's say you merge your changes, you know, your code changes to the main branch. It passes the testing. 9:36 Continuous deliver- delivery, um, if you set it up, will deploy your changes to your staging and/or production environment. Um, let's just, let's talk about in terms of staging, right? 9:47 So, um, staging, staging for those of you who ar- aren't familiar, it's basically, um, a 9:55 w- a lighter weight replica of the production environment, um, where you can, developers can test their changes in that production-like environment. 10:02 And then f- the difference between continuous delivery and continuous deployment is that, so continuous delivery requires kinda like a human touch. You know, okay, yes, now that change has passed, um, through staging. 10:13 Now we can deploy, let's maybe every X days or weeks or whatever on a regular cadence to the production environment. Continuous deployment, it's basically, you know, no human touch. 10:26 The only way it will not, your changes will not go to production is if it fails, um, an automatic testing suite. Um- Mm-hmm... that's, that's a high level. There's multiple things that's part of it, but, uh, yeah. 10:37 So, uh, say something goes wrong, then it goes to people, to humans to fix it, right? Uh, yeah, and I mean, you can customize your workflow differently. It's like, uh, the deployment world is really big, but at... 10:49 Yeah, usually in most cases, um, um, a human will go in and, and check out what is the bug, what's the issue, go ahead and make fixes, and then, uh, push the fix. Mm-hmm. 11:00 Can you give us a, a live examples of how, uh, these, um, work in, in example of products, what kind of products you were working on or the most exciting products or projects or, you know, so we can actually see how it's working? 11:19 Yeah, yeah. So I'll just give a super, like, generic example. Um, let's just say you're pushing out a feature for the, for your, for a phone, right? Like you... For your app. 11:28 Let's say you're pushing a feature for the app where you want it to say, "Hello, world." Yeah. So, um, it's your first time, you know, pushing that feature out. 11:35 So what would happen is you push your code to the main branch. What... And then it would... What happen, s- what would happen for CI, the CI server, is it's gonna run tests, like is your app printing "Hello, world"? 11:47 What happens in an error? You know, or error... Is, is error handling appropriately, um, taken, uh, into account type thing. 11:55 So once the test confirms, yes, your app does print "Hello, world," the continuous delivery part will move your testing to the product... to, sorry, to a staging, uh, environment. 12:05 So this is before the product is released to the customers, so it's still within, let's say, your company, your, your startup or whatever. Mm-hmm. Um, and so then you can do some more testing there. 12:16 And then finally, once it all works, then you can push the gate and say, "Okay, this can be promoted to production," and now customers can see your app which says, "Hello, world."So that's just like a super high level of that end-to-end That's, uh, very simply put how you make a coffee, and, uh, that is whatever coffee kind of, uh, type you want. 12:40 Whether it's with syrup or with, uh, some frothy milk, you need to put some components to make it work, right? Yeah, correct, yes. [laughs] There you go. I know. If you love her, I'm like, "Yes, coffee." 12:52 [laughs] Totally. To- it's very simple like that. When you put it in a coffee perspective with my coffee brand, Hanza Coffee, uh, that I used to have, it's, it's very, very easy and self-explanatory. 13:06 So since you work in infrastructure automation, can you talk about what infrastructure as a code is? Yes, exactly. So infrastructure as code is one of the components to support DevOps. What it basically does is that... 13:23 So what happened, what would happen before is, you know, infrastructure teams would deploy to different systems and then they would have custom configurations. 13:31 But eventually sometimes people would do tweaks here and there to different systems, and maybe they weren't tracked, they were a one-off. But as you know, one-off sometimes propagates to bigger issues, right? 13:41 And so, um, these, you know, systems would become snowflakes where we don't know what the... We don't know how it's configured, you know, 'cause it wasn't tracked. 13:50 So infrastructure as code is it r- it literally codifies infrastructure, um, you know, definition and deployment. 13:57 For example, provisioning, you know, um, your networks, virtual machines, uh, load balancers, things like that. And so, um, basically what you do, for example, is you define, um, kind of declarative, right? 14:09 So you're saying, "Okay, I want one virtual machine with, uh, these specs." And then you submit it via a tool, Terraform, um, which I will dive into. And let's say, um, Terraform will, 14:21 you know, talk to different, uh, cloud services or whichever one you configured it for, and then provision that, um, uh, that, that resource Mm-hmm. 14:33 So Terraform talks to different, uh, servers, service, ser- ser- serv- what? Yes. So yeah, different like, different services. [laughs] Yeah, correct. Yeah. [laughs] Tell us about that. Yeah, yeah. 14:46 So one example is, um, Terraform can talk to different, you know, cloud providers for example, like, um, like Azure, Microsoft Azure. And so what... 14:55 So Terraform is ba- is kind of like the, the command tool, uh, you can use, or you can use an automation. And so like I said, right, so let's say you wanna provision something in Microsoft, in Microsoft Azure. Okay. 15:08 You would write the specs for it, and then it will go ahead and do that for you. Okay. Or it'll submit it to the, um, Microsoft Azure endpoint, and then Microsoft Azure will provision for you. 15:18 So Terraform is like a gate... is a, is like a gatekeeper. Mm-hmm. Um, additional, like if you wanna do things in AWS or literally a lot of other things that out- Terraform offers a great support around it. 15:30 And, um, just as, just to note, we talked about versioning, right? So Terraform also provides the ability to version your, um, resources and see like the updates around it, so, um- So, so each version is not colliding. 15:43 So you, you update something and then it's, it's making sure that it's, uh, secure, safe, and, uh, is relating to the right, uh, outcomes. Correct. Yeah. And so the, one, so a way... 15:56 So to give an example of how you run it, like let's say- Yeah... yeah, you, um, you write a file. You say, "Okay, I wanna provision..." 16:03 Um, obviously it's, it's in, Terraform is written in HCL, so it's this HashiCorp, uh, language. So, but I'm just saying the words, right? Yeah. I wanna provision a virtual machine. Yeah. 16:13 So what you're gonna do is you're gonna run Terraform Plan, which we'll see, it's kind of, it's a dry run, which is, which essentially means that it shows you the output of what's gonna happen without actually making the changes. 16:24 So you can see, "Oh, is this what I expect?" And, and, um, then you can review the plan output. Sometimes it's gonna fail because it knows, um, for example, wrong syntax or whatever, you know? 16:35 So once Terraform Plan passes, then you would run Terraform Apply, which will actually do the provisioning. Um, so that's just, um, a few commands that, uh, couple of the main commands that we use for, for it. Mm. 16:50 So, uh, we've got Ermz Maga joining us, and she's got a questions: "As DevOps, what other programming languages should we know? Should we need to be an expert of those, uh, languages maybe? 17:04 What steps we should take to learn something that is relevant in the DevOps world?" Yeah, of course. 17:12 So DevOps is a practice which can be applied on multiple domains, which means you could use multiple language as part of it. Okay. Um, so you can think of them as two separate things. 17:22 Um, I think for personally with the language that I use the most is Python. Um, so because it based on your team, right? For example, let's say my team uses Python, then I would not, maybe not be, um... 17:35 If I'm not an expert at Python, I'm gonna learn to eventually know a lot about Python, which is what I've built up to right now, which I know a lot more about Python than, than I did before. 17:43 But let's say you have a team which is working on, you know, let's say JavaScript or HTML and things like that, you would need to know those languages for your team. 17:51 So to answer your question, um, you would need to know the languages for your team or the project that you wanna work on. Mm. And in terms of being an expert, it's, it's like, uh, we're all experts in our... 18:02 We can all can be experts, right? But it's all about like, um, it takes steps to get there. And also, even if you're an expert, there's always more to learn, right? So don't worry- Yeah... like you'll be okay. 18:12 [laughs] Let's learn some more. That's very encouraging, Kausar. Thank you so much for these encouraging words. 18:19 I'm sure, uh, Ermz, uh, will appreciate that because, uh, quite recently she made a comment on our Facebook page saying that she's very excited about learning new languages, so, and she thanks us. 18:34 Thank you, Ermz- Thank you... for the kind words. Kausar really appreciates that. 18:39 So, um, I wanted to maybe dive a, a little bit into your personal life.Was there a coach or a mentor who was leading you and telling you, you know, what languages you should go into or, uh, you know, how to deepen your knowledge? 18:57 Yeah, definitely. So what really helped me early in my career is having, um, a few different mentors, um, uh, in my first job, and I think that really helped me in terms of, like, okay... 19:09 I think in terms of the l- programming language, it was kind of like whatever the team was using, that's what I used, so I used Python. 19:15 But what these few mentors helped me was around the mindset around, okay, um, this is how you test. These are some best practices. Um, this is how... 19:24 This is w- these are some books you can use and resources to write good code. Um, you know, first job, current job too, right? 19:31 I think the mentors are really helpful, and they've really helped me level up my skills, and also, um, now that I'm a mentor too, I've, I've been a mentor for a couple years now, a few years now. Mm. 19:40 Um, I really like how, you know, I encourage those that I'm mentoring to read certain books. I, um... Like tech books, soft skill books, you know, communication books, and things like that. 19:50 So definitely mentors have helped a lot, and I'm happy to, like, pay it forward, so I'm glad that I'm continuing it. Great. Uh, and we've got another question. In Love and in Pain, thank you so much. Mm. 20:01 What inspires you to do coding? Maybe I can have the same inspiration. Yeah. I mean, I think I'm glad you've asked the question. I feel like, there you go, you have some inspiration, you know? 20:14 You're just gonna, like, tap into your potential. Yeah. Um, but as far as me to do coding is I like it as I really love problem-solving. I like the challenge of learning a new language. 20:23 But when I say problem-solving, what's interesting to me is someone can tell you, you know, "Solve this for me," there are so many ways of doing it, you know? You can look at design patterns. 20:33 You have to know domain experience and things like that. Um, but in terms of, like, just getting started coding, what I would recommend you do is understand, like, why do you wanna start coding, you know? 20:42 Is it just 'cause you wanna learn? Is it 'cause everyone else is doing it? 20:46 Um, so what I like t- to think about coding is it's a way for me to learn a new skill, and y- you just need a laptop pretty much and some tools on it. 20:54 So to, um, encourage you to start coding, um, I would recommend you could check out GitHub, you know, like Hello World pro- you could look up GitHub Hello World projects, things like that. 21:04 Because as you start developing, as you start building smaller and smaller projects just to build up momentum, then you'll get more confident and be excited about it, and maybe you won't be, which, you know, to be fair, it's fine. 21:16 But from your question guides me that you, coding's something you wanna g- look into, and I'm excited for your journey. 21:22 Well, I have to say, Kawser, that there are many females that I met on my journey, and they were just keen on getting there, but it's really difficult to know where to start or what resources. 21:35 So I'm very grateful for these, um, tools that you send us, I mean, these links, uh, that we are propagating now. Mm-hmm. Please make sure after the show to revise them and check them. 21:48 So let's go to the GitHub Hello World projects. Tell us what is that about. Yeah. Um, so, uh, one of, one of the ways that, um... Well, so when I say Hello World, it's basically like... 22:01 And when you s- when you create a new project or learn a new programming language, you th- you look at the Hello World projects, which are the beginner projects. 22:08 And so the output of the beginner projects is to literally print, you know, "Hello world" in that new system. 22:14 So when I mention GitHub Hello World projects, um, it's basically, you know, you can look at the source code for, um, different code people have written which prints Hello World in different languages and different frameworks and things like that. 22:27 So that's what I was referring to. Mm. 22:30 Do you sometimes look back at what you created, and, uh, do you go back to what you made or to see what was the mistakes you made, or you never look b- back, and you just go forward and create new things? Oh, yeah. 22:48 Uh, I'm a huge reflector. I love reflecting personally and professionally, and definitely along my coding journey. 22:53 So I definitely have seen the code I've written back in college, you know, early on when I started my career and right now, and it's interesting to see the evolution. 23:02 I, I think that it's important for us to reflect on that, and, and be compassionate about ourselves because although it's easy to say, "Oh, I didn't write that well back then," you know, you did the best you could, you know? 23:13 Of course. And it was the best at the moment. Um, but it's also good to... 23:17 I think having that experience of reflecting helps you mentor other people because you see where they're at and be compassionate as they're getting onboarded. Um- Yeah... yeah. Yeah, be kind to yourself, right? Yes. 23:29 [laughs] Good. So, um, what programming languages do you primarily use? You, you me- you said you use Python, and you use it because it for work. Is there any programming language that you prefer using? Yeah. 23:47 Uh, I, I was to say Python. Um, I've been to... I, I love using Python a lot. I've been to PyCon, which is the Python conference, uh, for a few years now. 23:56 Um, so that's just the, the main one that I, I like to, uh, I like to talk about. I think I also have a few, like, books on my bookshelf right here about, like, Python best practices and things like that, so yeah. 24:09 [laughs] Yay. Good. And you also told me that, uh, a couple of years back you attended, uh, Grace Hopper, uh, uh, celebration, um- Yeah... conference, right, in The Bahamas. 24:23 Can you tell us a lit- a little bit about that? Yeah. So this conference was act... So I attended Grace Hopper a few times. The first one was not in The Bahamas. Sorry if that wasn't... 24:33 It was actually in Houston, Texas, and that was actually- Oh, right... my team. Um, yeah, and then I attended, like, couple times after. 24:39 And then last year, um, I was able to be a speaker at the virtual Grace Hopper conference, where I spoke about code reviews. 24:45 And so-Um, it was m- when I first went to Grace Hopper in 2016, it was such a life-changing experience 'cause I met a lot of wonderful people, wonderful women in tech, and it got me inspired to d- wanna be a technical speaker. 24:58 Um, before I, before I attended, I was always into public speaking, but that really solidified, oh, I wanted to be a technical speaker as well. 25:05 And so that's why when I was able to talk last year about code reviews, um... I could probably send a link or something. 25:11 Like, the actual, uh, video's not published, but I can send you a link to the summary of what I talked about for code review, so yeah. Yes, please. Okay. Yes, sister, we want it. [laughs] Yes. Okay, perfect. Yes. 25:23 [laughs] I'll give you, I'll give you the details. Okay. But it was one of my favorite experiences in life ever. [laughs] Fantastic. 25:29 So, uh, let's just remind, Grace Hopper was, uh, coined Amazing Grace because she's the woman behind the COBOL, and she also is behind the, uh, quotation that I really love, "A ship in a port is safe, but that's not what ships are built for." 25:50 So- Wow... take your wings and take your ship and go into the sea. So, um, coming back to the world of coding, 26:02 how do you step, stay on top of the tech trends or the, the changing world of, uh, coding? Or how do you stay, make sure that your code is secure? Yeah. So, um, multiple things, yeah. 26:18 So let's talk about how I first stay on top of tech trends. So there are so many tech trends. I feel it's super overwhelming. 26:24 But what I do is that, um, I, I subscribe to kinda this, like, daily news as part of, uh, uh, TechCrunch in my daily inbox. 26:32 I check every day or every few days or at lunch, you know, just to just get a highlight of the top things that are happening. 26:40 Um, I also like to periodically browse on Medium, and just even I look up, like, latest tech trends, things like that. So that's, like, good to know what's happening across different industries. 26:49 And in terms of the stuff I'm working on right now, what helps is, you know, when I was going to conferences, going to meetups to understand the latest and greatest in that current area that I'm in right now. 26:59 Um, for example Python, PyCon for, PyCon for Python, and then the Grace Hopper conference for just, um, di- different technologies. And also just, like, word of mouth, right? 27:09 I mean, just talking with my friends and other, um, people that I know in the tech world. So yeah, also asked about how do I keep coding secure. So, um, security and coding is just such a huge area. 27:21 I just think it's, um, important to understand just... I think I basically looked up, like, ways to keep your code safe and just kept taking different courses. 27:29 And then also when I would go through code review, the reviewers would give me suggestions, you know, "This is safe, this is not as safe to do." Um, but it's like a whole new world out there, so... 27:39 Uh, what's important, um, is to also write tests against your code, so you try to catch edge cases ar- around it. So yeah. O- okay. So what is code review? 27:49 Is that a secret, I don't know, meeting for some coding anonymous? [laughs] Yeah. Um, uh, it's not as, as secret as that, but I guess it could be for some people. 28:01 Um, so code review is basically the process where before you sub... Um, you have the main branch, which has the main code for your application. Let's say it's Hello World. 28:10 Let's say you wanna write a feature which says, "Hello world," and your name. So, "Hello world, Kosar." Um, and then so before that feature is merged to the main branch, it goes through code review. 28:22 So what ha- usually happens is it's on a system. Uh, the code is put up for review, let's say using GitHub, th- and you tag the reviewers that you wanna review your code. 28:32 And they'll say, "Okay, is this feature nea-" They'll, they'll analyze it, right? They'll wonder is... They'll comment, "Is this feature needed? Um, does it follow best practices? Can it be clean? 28:43 Why are you even adding this in?" Different things like that. Once the reviewers and you have a consensus, you know, which says, "Okay, now we're ready to merge," then it is, the code is merged to the main branch, so... 28:54 Um, it's, it helps with the code maintainability, just, um, collaboration, and definitely it's, it's a good practice so everyone knows what... 29:02 Usually w- everyone know what everyone's working on through the code review process. Excellent. And, uh, just a, a question. I know that you're working with a team. 29:13 How big is your team, and, uh, how many of, uh, you females are in the team? Do you feel alone? Uh, yeah. Uh, no, I don't feel alone. I feel very s- supported. I have to... 29:24 I would have to count in my current subteam, but I think under 10. And I think in terms of the entire team it's about 20. But the team is subjective because we have teams of teams. 29:36 But I will say, no, I ha- I'm glad I have a lot of awesome females on my team, and, um, the m- and, um, females, I mean, everyone is super collaborative and friendly, and so I really love my team, so I'm glad that I don't feel alone on my, in my current role. 29:48 [laughs] That's fantastic. Good, good to know. Um, it's good to see a career woman like yourself making it big. And I just wanted to ask you, who is your role model when it comes to coding? Yeah. 30:04 Um, so I think my role model is actually, uh, my mom. 30:08 I know you said coding, but I think just seeing her, the way, you know, she worked hard to get to where she is today, and just also, like, the, uh, work ethic and the discipline. So that really motivated me. 30:18 Um, and in terms of, like, a, a coding, coding world role model, I would say I just have a lot. 30:24 I mean, just the people that I've met through, um, work, that I've met at conferences, the engineering managers and leaders that I look up to. 30:32 Um, and definitely the c- women in STEM that I've met on Code Latte on my Instagram. 30:37 Um, you know, the STEM community on Instagram is really big, and so it's just inspiring to see how many people are on there and how they're continuing to educate people about tech and share their journey and developer life, and so I'm happy that I'm part of that community as well.Here is the code latter, uh- Thank you... 30:54 just making sure that so, um, m- many viewers of ours can, uh, follow you. So, um, none of us are able to achieve things without the help along the way. 31:08 Who, uh, helped you, uh, to get where you are, and who you're most grateful to? Yeah, of course. Uh, I would say in this case it would have to be, again, like my mom and a, a few of my really close friends. 31:21 I think that definitely the mom inspiring me to, you know, always encourage my dreams and support me. 31:27 And then a few of my close friends where they just really, you know, believed in me and they, you know, gave me advice, and they would, um, help me be accountable. 31:35 And I really like how they're always supporting me in my journey, and so that's why it means a lot that they... my, my mom, my sisters, and my c- really close friends, that they support me. So that means a lot. 31:47 That's really sweet to know that you're surrounded by supportive women. We've got another supportive woman joining us, uh, Marianne Madera. Hello, Marianne. Have you tried a hackathon in your team? 32:01 Do you think it is fun to have one? Do people have time to sleep in a hackathon? Oh my goodness, so many questions. [laughs] I love it. I love it. Okay. So I did a few hackathons in college. 32:12 Um, I actually did a hackathon a few months ago in my, in my team, um, with a few people from other different teams. I think, yeah, it's super fun to ha- it's super fun to try it. 32:22 I mean, it's definitely ch- challenging and, uh, it definitely takes a lot in terms of, like, let's say it's a 24-hour hackathon. You know, like, do you even have time to sleep? Um, uh, the, the team one was not the... 32:34 team one was not the sleeping issue, when the sleeping was more, like, in college when we had a 24-hour hackathon. I think I slept pro- probably, like, two to three hours and that's it. But- Oh... 32:44 um, I think it's super fun to participate. I think it really, uh, pushes you to the next level in terms of getting you out of your comfort zone and talking with different people. 32:52 So even if you do a hackathon, you know, virtually with people you haven't met, or you do in your team, I know that you're gonna get a lot of good takeaways. Hmm. Lots of coffee then, right, Kauser? Oh, yeah. 33:03 Um, speaking of coffee... actually, no, I'm drinking tea from my cup. [laughs] Well, you li- li- you know, you can, you can still have a coffee after our, our, our call. I will, I will. 33:16 [laughs] Um, so I just wanted to continue on that journey. Um, how do you say no during a hackathon? 33:27 So let's say that you see that somebody's doing something wrong and you want to vocalize your concern. 33:36 How, how was it for you, especially at the beginning of career when you were surrounded by people who, uh, coded more than you? Yeah, yeah. Um, I, I can't think of a specific example where I... 33:49 Okay, so when you say wrong, do you mean in terms of, like, your team where- Yeah... okay. I guess I can talk about it kind of hypothetically in that sense, but I... I can, I can... 33:58 but give my experience from, you know, pushing back in the technical process, um, based on my current pro- not, like, all my projects. So, um, I think what's helped me is understand... like, understand their perspective. 34:10 Let's say they wanna add a feature in and you say you, you're pretty sure it's not needed or they're going off the right... the wrong track. Mm. But I would, I, I would ask them, "Why are you... why is... 34:19 why are you adding it?" Just a- you know, you're, you're curious, and they would... you would give the reasons why. Then what I would do is then I would say, "Okay, well..." 34:27 You would talk about, like, what is the outcome, right? What is the business outcome, the hackathon outcome? The outcome is XYZ. 34:34 I beli- because the outcome is XYZ, this feature doesn't ali- doesn't seem to align with it. I have a proposal, can we talk about it? And then just kind of talk about it that way. 34:43 I mean, I know that this is kind of, like, a super high-level response, but what helped me is, um, I recently read the book Crucial Conversations. Mm-hmm. 34:50 And so it's one of those, like, super life-changing books which, um, helps you in times like this, right? Um- Mm-hmm... and, uh, around, um, having such difficult conversations. 35:00 But honestly, sometimes you're not gonna get your way, and that's okay, but it's... I think it's important that you should always try to vocalize when you can just to get people's perspectives. 35:10 And, you know, sometimes, yeah, you are gonna be right, and then you'll go with your way. Um- Mm-hmm... it's just, like, it's, it's a give and take, right? I mean, no one is 100% right all the time. 35:20 It's about having a productive discussion. Hmm. So Crucial Conversations is a book by whom? Do you remember? I have it next to me. Patter- uh, like, Patterson, Gray- Kerry Patterson, right? Yeah, yeah, yeah. Yeah. For... 35:35 tools for talking. That's very interesting. We gonna post it shortly so people know and see it. 35:43 So speaking of books, uh, what is the number one book you can reflect on and think, "Oh, gosh, I wish I read it at the beginning of my career"? Oh, yes. 35:54 That would have to be How to Win Friends & Influence People by Dale Carnegie, I believe that's, that's who wrote it. It's just one of those classic books. 36:00 Um, so on Coder Lodge on Instagram, I talk about, like, developer tips, mindset, motivation, and coffee education. 36:07 So I had a series where I was talking about the different technical and communication books that I read, and I also had it on LinkedIn as well. 36:13 So, um, that book talks a lot about, like, active listening, and communicating, and influencing, and it's one of those books where you don't just read it end to end, you have to kind of, like, keep rereading it, and maybe you'll come back to certain sections based on your situation. 36:30 And it's... uh, I was... I like to gift it, uh, to my friends, uh, because it's super helpful. And I have it on a bookshelf, [laughs] of course. [laughs] Great. Uh, thank you very much for sharing that with us. 36:42 So what are some common challenges you face as a software engineer, Kauser? Yeah. Um, I'd say... [clears throat] Let's see. I think the first thing is understanding scoping- Mm... 36:54 so when you're given, um, a request to, to, to do something, understanding the scope of it. What I mean by that is, you know, um, how long is this feature gonna take? Is this feature even needed? 37:06 What stakeholders do I need to talk to? What's required to implement it? So understanding that.Um, another challenge is definitely around, um, just the troubleshooting a bug. So, uh, so b- a bug essentially means... 37:22 Yeah, like it means, you know, like something's not working, right? Let's say you wanna print... Your app wants to print "Hello, world," but it's printing "Bye, world." 37:28 And then, you know, that's a bug because, you know, it's not supposed to do that. Mm. But just troubleshooting around it. And so when I say troubleshooting, there could be multiple reasons why, right? 37:38 You could have like, maybe it's, uh, literally a spelling issue, you know? Or it could be a system issue. Uh, just so many different layers to it. Um... Mm. 37:48 And then finally the third, the third main challenge is definitely around communication, like I talked about. I think that when people think about software engineers or technical... 37:57 In the technical world, they think about the technical skills, the hard skills. But I think that, um, working on your soft skills- Mm... 38:03 communication where you would talk about your feature to different audiences based on, um, their level, right? 38:11 For example, the way you talk to your coworker who's an engineer about a feature would most likely be different than the way you talk to a director about it. 'Cause, 38:20 um, understanding the ways you talk to different people, so... Mm-hmm. Those are the top three. Um, absolutely. We've got question from Lizette Soto. 38:31 "Kausar, earlier you mentioned that you feel extremely supported in your current role. Have you ever experienced the opposite? If you did, how did you deal with it?" Yeah, yeah. 38:43 Um, I think I'm fortunate that I've been supported in both my roles. Um, but I, but I, I will say in college, you know, there was times where I felt like, um, maybe the, um... Not my team, but just some... 38:55 There were people that were unsupportive d- um, around, around, along my computer science journey. And so I think what helped me is trying to find people that I can confide in, you know, about the situation. 39:07 And, um, uh, but I would say, let's say, you know, you're not feeling supported in your current role right now, um, or if anyone isn't feeling supported right now, it's talk... It's like what can you do about it, right? 39:18 There's different ways to handle it. It's could you talk to a different team member? Could you talk to a manager? Could you talk to someone on a different team? That's a work context. 39:26 In terms of a school context, it's just I think talking to maybe like a career advisor. 39:32 I th- But I think at the end of the day what overall has, has helped me kind of push through people that are unsupportive is having, um, people I can talk to and confide in and having a mentor around it. Mm. But yeah. 39:43 [laughs] It's definitely important question to ask, because so many of us, uh, are facing microaggressions. Mm-hmm. And quite often, uh, we need that day or, or night to weep into, uh, into the pillow. And, uh... 40:00 But then you need to regain your strength and don't look back, because you're not going that way. Thank you, Lizette, once again for, uh, sharing with us some of your concerns. I hope- Oh, can I add one more thing? 40:14 Yes, go ahead. Okay. I, I will also say that at... 40:18 There's gonna be times when people are gonna just doubt you for what you are, and so I think what's important is understanding your strengths and what you have to offer to the table. 40:25 And I think, like, some amount of doubt is okay, but I think at the end of the day, like, the way that I was able to overcome a lot of this is understanding my strengths and I think just at... 40:35 Speaking, speaking about it and then also kinda documenting the journey. Because we talked about how we reflect from our past, right? Right. 40:42 So as we document, like even, even journaling, you know, this happened this way, and in the beginning I felt blah, blah, blah. So I think just- Mm... uh, writing it also helps. But yeah, uh, you're right. 40:52 Every day is a new day and we have a fresh start. [laughs] Absolutely. You own that table, girl. [laughs] Yes. [laughs] There you go. [laughs] Kausar, are you working on any exciting new project now? 41:06 Can you share with us? Hmm. Uh, what I will say is [laughs] um, I guess, um, work is pretty exciting. But although I can... 41:15 I can't really speak to the work products, I will say I, I do love how I'm continuing to work with new technologies over there. Um, in the coffee world, I, I guess it'll... I, I also have to talk about coffee. Yeah. 41:26 Exciting coffee project is learning a new latte art design, so that's what I'm working on. Yeah. Um, yeah. I'm al- uh, I'm also learning a new, um, programming language called Go. 41:36 Um, I have been learning it for a while now, but I think that's exciting just to learn something new. [laughs] So... 41:42 And you're doing it because you need to or because you want to or is it because you're doing something at work, uh, uh, that involves, uh, this language? Yeah, yeah. 41:54 So I've seen Go a lot actually in different projects, and I just wanted to get a u- get a, a handle of it. And I think I also wanted to do work on it for... to see if I could work on it at work as well. So there's, uh... 42:05 Go is definitely up and coming language. I think a lot of people use it for different things, so I just wanted to learn it as well. 42:10 [laughs] But obviously I'm a lot more comfortable with Python than I am with Go, but one day. [laughs] Cool. Yeah. 42:17 And, uh, again, going back to the resources, t- uh, is it GitHub you're, you're getting some resources from or is there some community out there that we need to know about? Yeah. 42:27 So I like to use LinkedIn Learning, uh, for a lot of, uh, when I learn new things. So I took like... I don't remember the exact name for the Go course, but it was a LinkedIn Learning, uh, Go course. Mm-hmm. 42:39 [clears throat] Cool. That's great. Um, let's go into what advice would you give to other females to help their career? Yeah. Uh, so I think this advice can taken for pretty much anyone. 42:56 Um, so I think it depends on the perspective, right? But I'll just say generically, I think, like I said, what helps me is I really like... I'm someone who likes to document my journey. 43:06 Like, like I said, both latte art, coffee education, and... Or my developer time. 43:11 So I like to have like a weekly check-in or maybe even monthly or quarterly check-in about where I am about certain things.Um, and then just kinda write it out. 43:20 I'm also super goal-oriented, and so what will help, you know, people in their career is understanding their goals, right? 43:26 Like, let's say, their three-month goal, one-year, three-year, lifetime goals, and, um, have check-ins to get yourself accountable. 43:34 What's also helped me is sharing my goals with my, you know, my close friends, and my support system, my mentors, and kinda get their feedback on it. Um, also get feedback on where I am, you know? Mm. 43:45 I think it's also really important to get that feedback. And also we also have to keep in mind, like, um, everyone will have different feedback. Um, but I think at... 43:55 what's important is having a growth mindset, which I also emphasize on my account and just personally whenever I talk to anyone. 44:01 So growth mindset being like, being that, you know, no one is perfect, but you should be working on, you know, yourself and improving. 44:08 And let's say something doesn't go your way, still take it as a learning opportunity, and then you grow from there. So that's the, that's what I would suggest. Hmm. 44:17 So and what are the top five skills of c- all career-driven females should have in your opinion? Yeah. Um, so the first thing I think about is having effective communication. 44:31 Um, communication is super big, um, but I'll just kinda keep it at that. Uh, second is having leadership skills. Um, you don't have to be a manager to be a leader, right? 44:42 I mean, just in your role, what can you, what can you show, um, show up and come to the table with? Um, next would be having good, uh, written, like, documentation skills. 44:53 So you know, crafting emails, writing documents, um, and writing it for different, um, kind of personas type thing. Um, I think, I'm trying to think of two more. Oh, active listening. 45:07 Uh, you know, we always like to talk. Maybe some people don't like to talk, that's fine, but being an active listener is really important. 45:13 Finally, the fifth skill would be, I would say, um, when I said ability to lead, I also... the fifth one be ability to influence, right? Those are slightly different things, but they're pretty much related, right? 45:25 And so those are the five, uh, skills I believe are really important. Mm. So, uh, what do you think makes a perfect influencer? I mean, ability to, uh, influence is quite a hard one, right? Oh, yeah. When you... 45:43 influencer word is all these Instagram babes sitting on the beach, sipping martini or something like that, right? [laughs] Yeah. 45:52 Wait, sorry, when you say influencer, do you mean, like, in the business context or the Instagram context? [laughs] No, I think, I think we are thinking about the same, which is business context. Okay, okay. 46:03 Influencer now, um- Oh, oh yeah, yeah. Yeah... rather, rather, you know, misconception of influencer word. Yeah, yeah, yeah. But how do you actually influence your, your audience? 46:13 I mean, how do you become a leader that has influence? Yeah. Um, and it's something that I'm continuing to work on as well. But I... 46:21 like I said, what's helped me is at least having a foundation, so kinda reading the two books I talked about, um, How to Win Friends & Influence People, and then reading the book Crucial Conversations. 46:32 So what I found when I wanted to influence certain decisions and, and people for certain things is understanding, 46:38 understanding my outcomes, the, my goal outcome of the situation, and understanding what their perspective is and, like, why do they want something, right? 'Cause they could be pushing for something, 46:48 um, but not getting to the why they're pushing for it and solving for that will... it'll make it harder to influence. I think, um, just, uh, understanding their why. I think also the way you phrase things, right? 47:00 It's like you can influence through force and might or you can influence subtly. E- everyone has different ways, and sometimes I've... I mean, I've done both, right? 47:08 I mean, we do different, uh, things based on the situation. Hmm. Um, but yeah. It's just a b- it's just a big world out there. I'm trying to figure it out, too. [laughs] O- oh, absolutely. 47:19 And sometimes you just have to try, because the worst thing that can happen, you hear no. Yeah, exactly. Gotta try. And try again. [laughs] Fantastic. We are coming to the end of our show. 47:32 If you have more questions for our lovely guest, uh, Kausar, who's with us today speaking from Silicon Valley- Hmm... speak now. 47:43 Kausar, I wanted to ask you, because your name and surname sounds very Oriental, what is the story behind, please? Yeah, yeah, yeah. Um, my family, um, they're, they're from India, and so that's, uh, so I'm Indian. 47:59 And so yeah, so Saeeda's like a, like a family name, and Kausar is, like, my name. Um, but it's funny because I used to go with... 48:07 I used to be called Saeeda from college and before, so half my friends call me Saeeda and half my friends call me Kausar. Um, so yeah. But yeah, you can all can call me Kausar. [laughs] Kausar. 48:18 It's Kausar, S- Saeeda, uh, whatever, uh, the name you prefer, uh, we... you definitely rock Silicon Valley. Did... was, were you b- brought up in, in, uh, America? Yeah, yeah. 48:30 I was, yeah, I was born and raised here, so yeah. Great. Born and raised. And your parents? Yeah, uh, in India, and then they came over. India. Yeah. 48:37 [laughs] So your parents made all the way to America for your better future. Mm-hmm. There you go. Well done. No wonder your mom is your role model. 48:49 But let's imagine the pandemic is over, and, uh, who would you invite to have a private breakfast with, and where would you go to? Ooh, yeah. So I would love to invite Michelle Obama. 49:03 I, I've always looked up to her, and especially after I read her book Becoming last year, I finished reading it last year. Super strong, powerful, smart, and I would, like, love to have a conversation with her. 49:14 In terms of where, I would wanna go to a, a cafe in Paris. Just, you know, the views are nice and the food looks really good, and I've always wanted to-... travel there. So that's, that's where I would choose. 49:24 [laughs] Well, that would be definitely closer than, uh, eight hours, uh, flight, uh, for me, so we can definitely go and, and spend, uh- There you go... a weekend in Paris. I would join you, girl. Great. 49:37 [laughs] Thank you. [laughs] So any particular cafe in Paris, or you have not made your mind yet? Uh, no, there's just so many out there. Right. All of them. I don't know. [laughs] You tell me some. I don't know. 49:50 [laughs] Absolutely. I'll, I'll send a couple of, uh, suggestions- Great... uh, later on. But let's go into the life lesson quote. 49:59 Is there any life lesson quote that leads you throughout your career or at this stage of life? Can you share it with us? Yeah. Yeah. 50:09 So I'm, I'm not remembering the exact, like, wording of it, but I think, uh, at a, just at a high level, I... Like, everything happens for a reason. 50:17 I, I, I mean, that's just kind of like the motto since, like, you know, forever, where, you know, pe- things are... 50:24 People are gonna flow in and out, and situations are gonna test us, but I think what's important is, like, how we address those situations, and it, like, shows our resilience in overcoming them. 50:35 So everything happens for a reason. It doesn't mean it's okay for bad things to happen, but it's just, it just ha- it's just something that I understand, like, okay, things are gonna happen. 50:44 It's just like how do we, you know, come back, or how do we address it and kinda like work- move forward? Hmm. So you come... 50:53 You're c- you're joining us from Silicon Valley, uh, the place where people are bragging about their fuck-ups. What is your fuck-up that you remember you thought, "Oh, this is end of my career"? 51:06 [laughs] Trying to remember. I think, uh, granted it's been a while, but I think, um... I'm trying to remember if I pushed a bug or something. Yes, I pushed a feature, and I think, um... 51:21 It wasn't, it wasn't, like, as, as serious as, you know, other actual systems have been down, but I pushed a, a feature I had... 51:28 I thought I had tested it thoroughly, and it turns out that, um, it was pr- co- it was provisioning something incorrectly, and I... And then, and the end user really needed that. 51:38 But lu- and luckily, um, you know, our team has a system in place where I was able to create the bug fix and then get it deployed to production, but it was stressful because I thi- I don't remember, I th- I don't remember what it was exactly. 51:50 No, I do now. But yeah, it was basically... Uh, luckily it didn't bring the system down, but it still was frustrating, you know, uh, when you thought, "Oh, I'm done with this," and then, oh, it turns out you're not. 52:01 But I think, like, ev- any s- most software engineers, I think, have had situations, like, where they thought they pushed something that worked, but then there was a bug, and then you fix it. And- Yeah... yeah, yeah. 52:11 Look at Facebook last week. Exactly. There's so many- [laughs]... so many things. [laughs] Every, every system, everyone. [laughs] So- It's a bad owner if you do it. I don't know. 52:20 Like, [laughs] someone has to be the tester. So the system went down, and how did you cope with that? Did you admit immediately, or did it took you a while to- Yeah, yeah. I mean, I took ownership, right? 52:29 When I, when I... I f- I'm trying to remember how, like, how we figured that entire thing out, but essentially, like, I took responsibility of that feature missing something, and then I fixed it, and then I pushed it. 52:40 So yeah, I think taking ownership of what you're doing is super important. I think it also helps to have that culture, um, where, you know, you're... 52:48 as you take ownership, you know, it shows okay, yes, you know, you're willing to take action, and then you fix it. So yeah. Absolutely. It, it takes a lot of maturity as well. Mm-hmm. 52:58 So I just wanted to remind you about tomorrow's conference. If you would like to join us, it's tomorrow at 8:00 a.m. uh, CET, which is, um, uh, no, s- EST. So 8:00 a.m. 53:14 EST, uh, RWAX X Investor Ecosystem Conference. Uh, and then at midnight CET, which is 6:00 p.m. EST, is going to be me speaking about women empowerment. 53:29 Um, the links are going to be included, uh, in a second. And I just wanted to thank very much for joining us today Olga Vesina, Arms Maga, In Love and in Pain, Marianne Madera, Lizette Soto. 53:45 Thank you so much for all of your questions, contribution, and very insightful and thought-provoking, uh, questions. 53:57 "Tell people and they may forget, show them, they may remember, but involve them and they will understand," Confucius. You definitely understand the world of coding. 54:07 Just a final word, um, Kauser, can you tell us how to encourage more girls into technology? Is there a secret sauce how you were encouraged to g- join this field? Yeah. 54:24 I think this is something that a lot of people are solving in different angles. I think at the foundation is it starts young, right? 54:30 So what helped me was Mom noticed that I was interested in tech and, you know, helped me join these different kinda tech clubs and things like that. 54:38 So I think having outreach for pe- for, you know, for girls in elementary school, middle school, high school, at different levels, encouraging them to go to college in different tech fields, and once in college, have that, have that support system around that. 54:52 So yeah, I like how people are doing many different things, and I hope that it works out. Definitely don't go into pink just because it's a girl. 55:01 Uh, it's okay to let her play Barbie, but also think about ways how you can encourage different mindset, opening your mindset to, uh, Lego bricks. 55:14 Uh, recently Lego admitted to have a rather biased view on who can play, and they are trying to fix it. So that's your opportunity. 55:24 If you're a mother, if you're a father, make sure that your boy is learning the world of others and is not really only, uh, accustomed with, uh, with, uh, cars. 55:40 Um, and the same applies to a girl. So when you focus on the positives, the positives get more positive. 55:48 Kauser is a positive thinker, and she developed, uh, many beautiful quotes she is sharing with us today, some of her links. She's going to share another link, uh, with us. 56:03 We are going to post it later on, uh, for your knowledge, to expand your knowledge. 56:09 As always, our positivity quote comes from positive uf- thinking only and goes: "Look for something positive each day, even if some days you have to look a little harder. If you don't like something, change it. 56:24 If you can't change it, change your attitude," as Maya Angelou said. Today is your day to hack the future. Hack the positivity you want. Thank you, Kauser. Thank you, everyone. See you next week or- Sounds good. 56:40 Thank you so much. Thank you. Actually, see you in two weeks' time, or see you tomorrow at the conference. Thank you and goodbye. Thank you. 56:51 [outro music]