I'm an everyday woman, woman, woman, in everywhere, yeah, yeah, I'm living my life, life, life, living day by day. Welcome to Every Way Woman. There are some major changes happening in the talk show world. Welcome back to Every Way Woman. So let's have a real conversation about women taking over traditional men's roles. Madison, you've seen in sports, you've seen in marriages of your friends that women are kind of stepping in on the men. Okay, but I'm not exactly sure what you mean, like women are becoming football players? No, well there are women who are trying to be on men's pro teams. There's the woman who just joined as one of the assistant coaches on a men's basketball team. What do you think about that? If a woman is trying to be a coach on a man's basketball team, it's not that she isn't smart enough to understand strategy and all of that, but there are physiological and psychological thought processes and things are going on in a man's body that a woman may not fully understand. So yeah, I think you can cross boundaries sometimes where you take it too far, absolutely. So do you think we've taken it too far? I think in some ways we have. Not because I'm saying women can't be everything they want to be, they're not smart enough, it's just that sometimes it's like no, actually you can't be a man. Can you be a basketball player? Just be a proud woman. There's nothing about me that wants to be a man. Why not coach women's basketball team? Why go into men's sports?  There's so much work that needs to be done with women. I really wish that instead of competing to be a man, we invested our time in supporting the growth and evolution of women. I wish I could get up and kiss you right now because that's so true. Because what happened to just being a plain old woman, sexy, vibrant, educated, nurturer of the family? Why do we feel that? Because the man is moving here, we've got to do that because there's some reason we're going to fall behind. We're not equal. Sorry people, men and women are not equal. We're not even designed the same way. On that note, I have friends who go to their jobs specifically not dressed feminine, not for practical reasons, but because they feel in their office they won't earn the same respect as a man. So they step into this role of almost dressing more manly. I want to wear a choo-choo in heels and be treated the same way, bring it on. I don't want to have to do that and I think it's such a shame that so many women feel that way. Instead of being dressed like this, they put on a suit and look like a man. If a man showed up in his Superman shirt and expected someone to take him seriously, it would be hard to take him seriously.  It doesn't always cross. I want to be girl power all the time. When I was young, we come from a military background, a history of military veterans in my family. I wanted to grow up and be in the military. I was going to be an officer in the military. Were you trying to think like a man? I didn't think of it that way, but yes, I got out into the dirt and did all the stuff with the boys. I did what the boys did and I talked to a female officer and I'm trying to figure out where am I going to go? Where am I going to go with this? When I started talking to the female officers during that time, they discouraged me from going into the military. I thought, well, are you jealous? I'm just younger. What's going on here? The stories that they gave to me were like, no, that's not a place for women. The type of abuse that we received during that time, the type that you're going to be prepared to get defiled regularly. Mentally, physically. Sometimes it just doesn't make sense. Why do we want to push ourselves to the point where we have to make it? What does that look like, think like a man? Are we saying that women are subservient and they're thinking? What does that look like?  Exactly.  It's going to get you a lot farther. In a way, a man thinks in the business world, in the romantic world, you will get farther. Because we're relating to men. Because I didn't want to leave with women that we're sometimes with some dits because we don't think like men. No, absolutely not. No, but there is an art to being able to understand the mind of a man. You can think like a woman and understand the mind of a man. Okay, I have a question. If there was a man sitting here talking to us about our menstrual cycle, how real do you think that conversation would be? Stay on that. When you go to a gynecologist, this is totally off topic. But it's a man and he tries to tell you how it feels like. Right, yes. I understand that. Exactly. So, yeah, there's that crossing where men at some point are going to look at us and go, why am I having this conversation with you? Because there are conversations that we don't have with men because it doesn't make sense. Not that a man can't be educated. Not that a man can't understand it. I understand that. But at some point we're like, do you bleed regularly? I think we're disservicing women and saying less. I think that because women think with their hearts, men think more factual. But if I begin to start thinking factual, I don't want you to say that I'm doing that because I'm trying to be like a man. No, I am expanding my thought process. That's why I don't want to necessarily leave that if you start thinking intelligently, you're thinking like a man. No, you're expanding your thoughts.  Yes. A smart woman. Stay tuned. Stay with us. We'll be right back. Welcome back. So let's chat, ladies. Should couples get married when they're broke? Is there a time financially when it's better to tie the knot? Broke is relative. That's true. That is so true. I think it's good. I think it's okay. If a couple is ready to get married, you don't have to have the big fancy spend tens of thousand dollars on a wedding. That's not why people get married. It shouldn't be a reason. You don't think there should be some sort of financial stability along with the emotional stability of the relationship to build your future? Financial stability is something that you're always working towards. Once you get to a place where you're comfortable, you're always still looking to move to another place where you can get more comfortable and look for a place. So it's evolving. You're financial- I know my finances are evolving. I don't know about evolving. To Madison's point, I think in a marriage what happens is you decide you should talk about it. You should talk about having a conversation before you get married. This is where we are financially. Enough with what you said. What did you and your husband do? Tell me about that conversation. We were broke. We were broke. We didn't have a house. He was just getting out of graduate school. I was working, so he didn't have a job. But we knew that picture was going in, so we got a little apartment. Did he have a ring? When he proposed to me, we did not have a ring. No. We did not afford to have a ring. Really? Right. So we didn't get one until 90 days before we got married. But we talked about it. See, that's the difference. We knew our picture going in. It wasn't like there was some expectation that he had a million dollars in the bank that he was hiding. And I think that's what's missing. People are not having the conversation. But I think a lot of men, even guys I've been in relationships with in the past, have said, you know, I love you, but I've got to make a little more money, get myself financially stable before we build a future. And I'm wondering, is that an excuse because he doesn't really want to build a future, or is he really concerned about his finances? I think for most men, they are concerned about their finances. Men think about it more than women do. They want to see them. They visualize and see themselves, at least I think, in a way where they are successful and they're doing this and then they got the ring and then they got the girl. So they have a different way of visualizing what marriage or weddings look like.  I love my women. However, I did meet a woman who had said to a male friend of mine, she pulled out this picture in Cosmopolitan of this ring that was worth about $50,000 plus. And she tore it out and she said, don't ask me to marry you until you can get me this. See, there's a lot of women out there who are like that, who want to make sure their man can afford their lifestyle that they want for themselves. Now, at the time, I was like, okay, this is a bit shallow. However, at the same time... Is it shallow because she just knows what she wants and she's honest about it? Yes, on the flip side, she was honest. She was honest. Look, this is the kind of life I want to live in. If you can't give it to me, don't ask me to marry you. That's true. She should give it to herself. Absolutely. Well, good that she was honest, but also as women, we have to identify potential. Where my husband and I are financially today, we weren't 22 years ago. But again, we had the conversation across the road. So sometimes as women, I'm a caution the $50,000 ring early when it's not going to be sustainable. But also, your vision of marriage may be different from someone else's. My vision of marriage when I got married was, and I remember saying this to my ex, saying, you know what, as long as we're happy, I'm okay if we live in a trailer park. Now, years later, I get that repeated back to me. I didn't know that you wanted me to buy the trailer park. Well, no. You see, I'm nervous to have that conversation about finances. Well, I don't really want to share all of my secrets. My purchases are like... For some reason, it makes me very, very nervous and very hesitant to be completely open. What secrets are you keeping? No, no. Not necessarily secrets, but debt. I feel like a man who wants to marry me is like, I don't want to be responsible for all her baggage. So you feel that he'll reject you? You know, loans, car payments, et cetera, because I feel like that is just kind of a... I'm a little fashion that way, I think, but when I think when you have a marriage, you are marrying. Absolutely. You're marrying. Yes.  But speaking with your emotional life, then, if you're not as financially stable, does that cause more problems in your relationship? But I think it's where you put the emphasis. No. You know what? It doesn't. You're right. It's where you put the emphasis. Again, you ask me and I'll go back to, we didn't have a lot. We didn't have a lot. But what we had, and don't dismiss this lady, is we talked about what our future was going to look like together. And we said we only make X amount of money, and we worked in those means. And I know people... And I put pressure on him. I know couples who have had a lot of money, and they spent that money ignoring each other. Right. And it didn't help them in their marriage. That's powerful. It's really relative. And I think I love... It's really relative. You have a million dollars, you don't love each other. You have a dollar for... You can afford to spend more time away from each other. You're going to talk about that, Burrito. But you're happy because you're looking each other's eyes. On that note, we'll be back with more Every Way Woman. Stay tuned. I can buy my own trailer park now. Absolutely. I'll put them in. Stay with us. We'll be right back. You and Every Way Woman. Have you ever thought about making a career out of your passion for makeup? We'll keep watching, because we're going to talk to Ann about just that. Next up on Every Way Woman. Welcome to Every Way Woman. So women are launching themselves into entrepreneurship. And today we're talking to Anna about just that. She turned her passion for makeup into her career. So tell me, what is it like to be a makeup artist? Girl, it's not all glam as it looks in the social media. What do you mean by that? Honestly, if you look through the social media, all these people put up pictures. We only let you see what we want you to see. It is not all glam. You do put on a good face. It's long hours. There's a lot of driving. Really, my friends really know. They hardly ever see me. And it's a workout. I've seen the case. You are lugging. You have to be in charge of all your own tools, your products. Yes. It's a lot of tools, a lot of products. Searching for different type of brands that fit different types of people. Not the expensive kind too sometimes. So rewind. Take me back to the moment when you decided you wanted to become a makeup artist. Wow. Well, I never really wanted to become a makeup artist. It was more of a hobby. It just happened. You just won. It just happened. I mean, I literally had a full-time job and doing makeup and hair was just a hobby. I would do it for prom. I started back when I was 16, girl. So how did you turn that into a business? It just naturally happened. People were calling me. I remember I ended up doing a friend that ended up with Gothic. And she ended up saying, you know, Glamia for my wedding, she wore the whole red dress. No, she wore a red dress for her wedding with the YVEL. That's correct. But I ended up transforming her. It was a whole transformation that people were like, wow, you did that. And I think I was probably like 20 when I did that. How did that make you feel when you were able to transform someone? Well, in the beginning, it felt good. Now it's a different feeling because I ended up helping organizations and nonprofits where I ended up transforming and giving back. Different like cancer patients, you know, stuff like that.  It feels good. It feels good. It feels like I'm doing something. And even if it's for those couple, you know, minutes, you know, that they're sitting in my chair, I'm happy that I touched the life in that way. Yeah, to make someone feel beautiful is a true gift. Definitely. And you really have it. Thank you. There must be a pressure to always feel beautiful yourself. Oh, so look beautiful. Yeah, every time I go into a job, I mean, all my ladies here probably know that when you go into a job, it's kind of hard to wake up every time, every morning to put on your hair and put on your makeup, you know what I mean? So doing, being a makeup artist, you have to look presentable. You have to be the part. Oh, yeah. And especially me, I'm known for retro, so I gotta wear my red rose. But so how long have you been working as a makeup artist? 18 years. 18 years. You don't look old enough. I hope nobody just said my age right now. Yeah, nobody's doing math at home. I promise you that. So what's next for you as a makeup artist? Well, definitely I want to do my own salon. I'm a type of person that anybody that knows me, I reach for the stars, you know, and nothing's impossible for me. So right now, I have plans to be able to open up my own salon. But tell me about the networking. You have to network being a makeup artist. It's really important to network. A lot of people that I interact with, inspiring makeup artists, they always tell me, like, I don't like to work with other people. Or, you know, stuff like that. And I just look at them, and even though I shake my head, it's like, girl, you gotta learn to work with other people. It's all about networking. Well, yeah, what's the dynamic with your team? Oh, everybody in my team needs to know how to work with each other. That's why you're in my team. But definitely when you network, you're finding another job, you know, a wedding could turn into a fashion show. The next person has maybe a connection to a celebrity. You know what I mean? So it's all like, you know, then you're working on movie sets. Then you're working, you know, so it's a possibility. And you're working on Every Way Woman, making us all look good and feel beautiful. Well, we're gonna have more of your tips on a few more episodes of Every Way Woman. And of course you can find tricks on everywaywoman.com. More when we return. Stay tuned. Stay with us. We'll be right back. Are you in Every Way Woman? Up next, we have Manji from 88 tequila, bringing you Slim 88. Salud. If you're already being naughty with a cocktail, well then who needs all the calories? Manji is back and she's talking about the Slim 88 today. But before we get to that, let's talk a little tequila.  Yes. You're proud of that? Of course I am. And who's not proud of drinking tequila? No, but not only do you drink tequila, you work tequila. Yes. I mean, is your day ever not tequila? No. No. Tequila isn't every day work. It's our brand. Because when my night is tequila, my morning hurts. Let's just put it that way. You know? And how do you avoid that? Tequila has such this, like, kind of stigma. Well, it depends on what kind of tequila you drink and also how you drink them. So, for instance, ours is 100% blue agave. It's the good stuff. Obviously, that's high end. The more it costs, the better it is for you. It's pretty much how it works. Isn't that the story about life? Tell this to my father. Exactly. So, it has to do with what it's made with. It has to do with the process. And then also what you're mixing it with. If you're going to take tequila and pour a bunch of sweet syrupy products into it, it's going to give you a hangover. Because of all the sugar. Sugar and alcohol are typically what would cause you to not feel so great. So, those multiple margaritas hurt? Depending on how they're made. I mean, it depends. So, like, the one we're going to do. Do you have a family secret? I mean, if your life is always tequila, what's the family secret? What's the hangover secret? Tell us. I drink a lot of water and an Advol before I go to bed. Oh, come on. That seems to help me. Okay, come on. All right. So, but is tequila typically like a skinny liquor? It is. It's lower in fat. It's lower in calories overall. As well as it's actually good for your digestive system. It helps to... Tell that to my doctor. Actually, it... Is it really? Yeah, it's a known fact that it helps with digestion. So, I mean, obviously, it's still alcohol. It's still in moderation. Of course. I'm not trying to drink the whole bottle or anything like that, but definitely a little bit here and there. A little dose will do, yeah? Yeah. Absolutely. Okay. So, typically, you know, I don't ask anything, but we can go to tequila as an option. Definitely. And I love to host events. So, having a non-margarita is... Thank you. Right, right. Exactly. We like to do different things. So, today we're doing the Slim 88. Okay.  Thank you. All natural ingredients. And the first thing we're going to do is pour some tequila. Why the tequila? So, this is the blond foam? Yes. Okay. We use this one because you're using less intense flavors and if you used a repulsador in Yeho, you could. You definitely could, but you're going to get more of the oakiness and the wood, whereas you want to enjoy the lemon and lime flavors with agave. Keep it light, fruity, eccentricity. Yeah, exactly. Keep it fresh. Sure. So, let's do a shot. You could measure a two ounce shot, typically, in the shot glass. Okay. Yeah, this is a test. So, you don't measure and I'll measure. I don't. You know what? Bartender's usually do like a three second pour. So, I'll just go ahead... She's the pro here, obviously. And do that. Uh-huh. And I'm just going to go ahead and... So, let's hope I'm right. Yeah. I was going to say, let's see how good... Oh my gosh. See, now I just... Okay, see, you just lost. That was my fault. That was my fault. All right. I'm just going to free pour it into your cheers. All right. So, pour yours back in there. Pretend that you ever have it. And three. Got it. Okay. What's next? All right. So, we're going to go ahead and do the agave nectar. I want to... You know, I've always seen people sniffing their liquor. What is that about? It's just like...  You want to definitely smell it. I'm trying to laugh. You want to inhale all the different ingredients. And... I'm inhaling water. Just enjoy it. And when you taste it, you'll be able to taste everything that you smell.  Isn't it? Yes. So then you taste more if you actually smell it. Exactly. You pick up on more of the flavor that way. Okay. Absolutely. What's next? So, we're going to do a agave nectar. We'll just go ahead and squeeze a little bit in there. Agave nectar is very thick and very sweet. It's kind of like... It looks like honey. Kind of like honey. Okay. Kind of like honey. But I personally think it's a little bit sweeter. Other people might think it's not... I mean, how much am I going on here? Squeeze some fresh lemon juice into this. And how fun are these glasses, too? I mean, one lady doesn't like a martini glass. It seems very sophisticado, if you will. Okay, so we're going to go ahead and just squeeze the lemon. Woo! Talk about fresh lemon juice. Look at that. I love that. What is this? Lemon squeezer, I guess. I don't know what it's technically called. Because, you know, this is how I usually squeeze my lemons. Let me show you. And then I get... And you're more than welcome to get the seeds. Exactly. And you get a lot more juice this way. Okay. Well, that's good to know. Okay. And then we're going to do... Yours is always going to be prettier than mine. That's just how it is. Now we've got some lime, too. Now we're going to do the lime as well. All right. You know, I'm just free pouring free hand in this one. All right. Oh, that's fine. And most bartenders would make it that way. Sure, sure, sure. What else do we have? And then you can add a little light ice, if you want. A little ice. Sure. Sure, sure. Just to chill it a little bit. And then what we like to do to spice it up sometimes is just toss a few jalapenos in there. Well, talk about the jalapenos. Well, I don't know if I can handle those. I'm going to let Patsy try mine. And for this information, you can go to everywaywoman.com. Thanks so much, Maggie. Cheers. Salute. Every Way Woman gives back to the community. Go to everywaywoman.com to find out how you can match our donations of undergarments for baby kids. Thanks for getting to know Every Way Woman. This has been an Every Way Woman production. I'm an everyday woman, woman, woman In everywhere here here I'm living my life life living day by day you in every way


Cool. Thank you Joe. So today I'm going to talk to you about frictionless data for wheat. This is a project that we worked on at the early Institute to myself and another guy called Shindong Bian and we work for a guy called Rob Davy. I'll talk to you about it now. So to begin with, we are funded as part of a sort of infrastructure program that covers eight different research institutes and universities and there's over 25 groups of scientists. And the idea is basically to try and increase the yield of wheat. So effectively by 2050, we need to produce 60% more wheat to meet global demand. So any research we could do to try and make that easier for users, for people to get. So what do we do under DFW? Well, we produce lots of scientific data and it can be in various different types. So we have field trial experiments, we have data sets and we have genomic sequences amongst many other types of data. On top of that, we have also different groups of users. So we have breeders that have particular needs and academics and data scientists and people in the industry and all requiring different needs from the data. So the challenge we have is how can we make this data accessible and usable for everyone? So our solution to this is we came up with a software platform called the Grassroots Infrastructure and this is a suite of tools that wrap up industry standard software tools along with our own custom open source ones. And it works on the principle of communication between different systems all using a JSON API. So it's programming language and platform agnostic. And the idea is that these grassroots instance can be federated between each other and data and service can be shared. And also we try to make sure everything's done in a fair way. So if you don't know about fair, I'll just quickly run through those. The four principles of fair data. The first one is findability, as in can you find what you're looking for out of a system? So making sure the data is well described and can be searchable for both humans and users. It needs to be accessible so once people can find the data can they access it to the need authentication or is it openly available and so forth? We have interoperability. So the idea that even though you've got open data you need to make sure that it can be integrated into other systems whether it be different workflows for analysis or so forth. So it needs to be well described. And in terms of reusability we might want to make sure that all the data is well described so marked up and with detailed provenance. So now that I've given you a quick overview of fair data I'll now go on to the grassroots infrastructure. So what we have, we have a set of common core libraries which take care of things of how we describe our parameters and our web service APIs, how you call different systems writing reading files and so forth. And we have that attached to an Apache web server via our own Apache module that we write so that connects all of the plumbing together with the system. The bits that actually do the scientific analysis are what we call services. So this is either where we've taken adapted existing programs and we've wrapped them into our own sort of API or we write our own bespoke tools. And as long as systems conform to our API which is a well-defined set of standards and adjacent schema then they can run inside it. So we have various different types of tools. So we've taken existing tools such as BLAST which is a really common one in bioinformatics which is where you find areas of similarity between different biological sequences as well as our own sort of custom services like field trials, field pathogenomics, searching and stuff. And to chat about these in a bit more detail. So typically when you do a web service interaction say you want to go and do a search across two different systems for a particular sequence. Normally in this case you'd have two servers, one for the elements that you hear and one for the University of Bristol.  So the problem there is you have to access each one individually. And then once you've done that you have to collate the results together and do anything like me. You've prone to human error and not cut and pasting things together properly. You might mistakenly run the services within parameters so you might not be able to compare them correctly. And it's time consuming. So one of the things we tried to solve was the idea of federating services. So if two different places are running a grassroots instance they can be hooked up together on all the services shared. So the idea being it doesn't matter which one you log into you see the same list of services and functionality. So one of that you can also amalgamate services themselves. So the service can actually see the databases all on one system and all on the other but to a user they appear like they're in one place. So from user point of view they just log into a system they see a list of databases to search against and they can just run their analysis and that's fine, they get results back. For example, the hood obviously has communication between the two different systems and all the results get collated together. So that's sort of an instruction to grassroots and I'm now going to talk about a couple of systems that we've done. So the first is as part of this project, the DFW program we create lots and lots of data and all of this we need to make available. So we have a data portal for this and this is everything on this system is based upon the Toronto data agreement which is an excellent license which allows you to pre-publication data sharing. So the idea is if you do some scientific analysis you can make your data available for everyone else and they can access it straight away but they can't publish on it until you have. So you still get first rights if you like but it makes sure that everyone else can do their analysis and pipelines with it much earlier than they normally would. So where we store this, we store it in a system called iRODS which if you haven't come across is an open source data management software and it's used by a variety of research or commercial organizations worldwide and it has a number of sort of cool features. So one is that you can virtualize the data as you need it doesn't really match from the user's point of view it doesn't matter where the data is stored so you can shuffle it around on your servers and from their point of view it doesn't move. It has data discovery so because once doing the standard typical file and search things you can also attach metadata to the files. So for instance if you have you run experiment and you want to store the parameters you run an experiment with you can attach that as metadata to the results file and if the results file gets moved around metadata stays with it. And in the same way that we have the grassroots instances can be federated so too you can do that with the iRODS which is where we got the idea from. So what we did is we took an Apache module and we forked it to make this available on the web so the idea being that we can make the data appear in like a user friendly environment but add lots of extra features we want to expose the metadata so that can be displayed and that can be edited and give the whole system a full rest of web service API so people can program against it if they want to. So in terms of the metadata we store we use the minimal information about a plant phenotype experiment or MYAPI and that has a list of certain parameters or certain metadata attributes to store and keep so we stick with that. On top of that we have an extra field so we have things like the title of a project the list of the authors description of it and the license details along with the actual data itself gets indexed with an our own search engine which is based upon Lucy again everything we do is open source it's all available. Now last year we were lucky enough with a tool fund from the Open Knowledge Foundation and with the goal being to expose these data sets, the frictional data packages and if you can see in the little red box we have a little data package JSON file. So what is friction data? I'm sure you've heard lots about it over the last day and a half but just in case you haven't we have a simple container format used to describe and package any type of data and it has many advantages simple to use can handle anything, it's easily extensible that you can package your metadata in there and it's human-editable and machine-usable. I like the fact that users re-use existing standards and because it's in JSON it's language technology and infrastructure it's great, love it. So we've put all of our data into that so each of the projects that we have in the data portal now have these frictional data packages automatically generated it's not like the user has to go and create it and it contains all of the files that we have actually sitting on the website as well so the things like the license, the name, the description and so forth. We've done this by adding some extra functionality to the Apache module that I mentioned that connects to my rods so it has a number of features so that first is it can whether dynamically creating these files if a particularly large will take a long time to generate they can be cached and written back to our rods so next time that file can just be served that's really good, and because it's in Apache you can use all the standard Apache configuration directive so you can just say at a particular level in your file directory hierarchy these things can have frictional data packages generated. Obviously we can't control what metadata keys people use to describe their data within iRods so all of this is completely configurable so you can set up in your configuration you can say use these iRods keys you can use these frictional data metadata values and the iRods metadata values can all be combined together so you can take the results from multiple different metadata values concatenate them together and that becomes a frictional data value that you see so as well as the basic data resources we also support tabular data resources so these are typically things like spreadsheets or CSV files and in much the same way all of the column headings and variable types again completely configurable and can be pulled from your iRods system so we try to make it as little with no hard coding as possible so that anyone can configure it for their own systems so the second thing I'm going to talk about are field trials so field trials are experiments where scientists will put loads of different crops within a field and apply different treatments to them could be fertilized and so forth and then measure particular traits it could be how quickly it takes for the crop to grow or how high it grows or so forth so we worked with the data producers all within DFW and we came up with standardized template for submitting the genotype which is the genetic material of the crop i.e. what type of seed it was and the phenotypes you want to store which is typically the characteristics you want to measure like I mentioned plant height and so forth we're trying to facilitate all of this so everything is we're keeping the fair shared principles in mind of everything that we produce so in terms of findability we have a Google maps type approach you can go in on the map and search around to find any trials that are in a particular part of the world or alternatively you can go in for a normal text based search web page but eventually you come down to particular set of studies so everything we do is openly accessible and they all have unique identifiers that are fixed URLs so they're accessible and we we will keep them those addresses so people can reference to them and know they're still on existing in terms of interoperability in the grassroots API we also have adopted something called BRAPI or the breeding API which is a community driven standard for developing a web service API for enabling interoperability between different plant breeding databases so that's another API that we use in terms of what we actually store in a system we have GPS files for where the plots are within a particular field so as well as storing lots of different metadata such as a description of a particular study what is trying to calculate any design notes or anything like this we also have these on the individual plot level and we've allowed automatic map updating so someone can have their phone or tablet and walk through the field and know which plot they're on so they can then tap on that and see the details of that plot to try and make it as useful as possible so what we store for the plots well we have lots of generic data such as its dimensions, its length its width, when the crop was sown when it was harvested and any user comments for the person putting it into the field you can also attach images and they can be obviously taken with your camera or we can have drone based images along with what crops have been sown there where the accession and seed so you can actually go and order the seed for that particular variety the sown in that particular plot and then obviously what people do they're interested in measuring stuff so the phenotypes or the measurements that people are interested in are typically comprised of sets so core or triple of values the first is a trait as in what to measure and this could be the plant height, this could be how long it takes to grow the method of how it is measured it's the next part and finally the unit so it could be if you're measuring height it could be in centimetres or in metres or so forth along with the value of potentially a date now all of this stuff and everything that we do and all the data we store we try to make sure they're well defined terms so everything that we do comes from the crop ontology so everything is marked up and has proper provenance from there so as I mentioned we've got a couple of web service APIs the grassroots and wrapping but another thing that people requested that we work with is they're not way experts in the field way better than me but they're not necessarily comfortable scripting or programming and they just want to get the basic data and the ideal solution for this and I'm not being paid to plug it is frictionless data so what we've done is we've come up with a load of schemers for the different classes of data we have we store where would be studies the data and the plots and so forth and we package those all into frictionless data package and we're not just the only people on DFW working on frictionless data we have collaborators such as Richard Oslo Rotham's research who's working in a similar field and doing data carpentry lessons and frictionless data so what do we store well we've got within the frictionless data packages these are all again all generated the user doesn't have to do anything we have the various different resources so one for the program that's in then the field trial then study this inside that and then the plot data so we all of the fields that we have in there are standardized and on a study level as I mentioned there are standard attributes such as length and width and position and stuff well specific to each individual study you might be having different treatments or measuring different phenotypes so all of that again is calculated with the software and it automatically creates a spreadsheet including these values so it might not be easy to see from the screen on there but just an example of one of the sets of tabular data we've got and it shows the particular phenotypes within that study Simon just to say you've got about four minutes left that's awesome thank you Joe so as well as exposing this to the frictionless data package we thought can we make this even easier for users to use but so I know that it has great APIs and great tools in Python stuff but could we make it even simpler for them to unpack the data so it's another thing we've been working on it's a tool to extract resources from within a frictionless data package and the way this works is a standalone tool that you can download again it's open source with a link at the bottom and the idea is that it will read the contents of a frictionless data package and for each data resource within it it will look at the schema that it uses with the profile attribute go over to the internet and download it and then write out all of the data resource fields using from that schema so currently we support the data resources being written out to either markdown or html but we're looking to add more different types and any tabular data resources we can take them out with csv this tool is cross platform as we plan to make it available for as many different platforms as possible and it's absolutely nothing weak specific in it so it could work with any frictionless data package that you like and the URL is there for the pre-release version hopefully we'll have proper releases soon so in terms of further work we want to write frictionless data as many different places as possible within our systems and add machine learning to try and detect the scientific values from media such as photos and we're looking to try and standardize on frictionless data schemas between different types of field trial experiments you might have one we typically work with ones that are over a single year but in some institutions they might go over 10-15 years and so forth so finally I've got lots of acknowledgements of people who work with so various different people that work across the FW that have helped us enormously so with the Ironman Institute where I work and at the John Innes Centre and University of Bristol and finally a big thank you to the csv con organizers for inviting us and that's it thank you very much and thank you from us to presenting to you we do have a question I'm just going to see so we're going to give you again a very short answer for this one so maybe you can answer it in a bit more detail later because we've got the keynote starting in two minutes can you tell us a little bit about your users it's a question that I had as well actually yes so we have for many institutes themselves we have lots of research scientists that are particularly trying to do to get this data and like work out what particular things they might have particular phenotypic values we also have breeders that are trying to work out whether they're particular seed lines that they can cross as in like have two parents or and come up with a species that's particularly hardy to say a particular disease or a particular characteristic you might also have people working in the industry that are doing similar things and we have academics so we have like a variety of different users and that's part of the challenge is going well you can't have a one size fits all you've got to make it so that everyone can get what they need out of it


come outdoors with me for an LGBTQ plus nature walk. To be in nature just is really grounding. We walked about two miles. We were stopping quite a bit just to take a lot of pictures. We also collaborated with Big Al Backpackers Boise, the body-inclusive free-of-diet culture hiking group. At the very end we had a picnic together. After every outing I just I feel so much joy to be a queer person. Walking on the trail there were so many times where people were like what group are you guys with? The rest would be like oh like we're a queer outings group through the Sierra Club. Being unashamedly ourselves and taking up space just shows me the strength of the queer community. It made it extra meaningful. Having some kind of entry point where people feel like they can try something new in a community of supportive people. Power in numbers is a really comforting feeling. I always just get emotional and also really happy that we all are there together out and proud in nature. Bye!


How many of you think it makes sense to combine your diet and fitness programs together? We don't think you should. They're njrew22.com here with another low carb, keto, carnivore, chat. I got a little bit of a mess going on here. I was fixing my tractor this past weekend. A lot of times when it comes to a health improvement, you'll see people combining their diet and their gym. And it's this whole big complicated mess. You can get really confused when you say I'm going to go to the gym, I'm going to work out five days a week, I'm going to do this, I'm going to cross fit, I'm going to eat right. And you may certainly experience positive gains with just being healthier and more active in general. But you don't really know what's working and what isn't. It's not a good experiment to perform on yourself. And I've seen this happen with a lot of people, myself included, where if you had a good week at the gym, I'm going to reward myself with some sandwiches or disgusting junk food. And that just holds you back. And you really don't know how to be in tune with your body if you have, let's say, a heightened sense of fitness, which never lasts, only for the top 5% of people, does it really become a lifestyle. The second thing is that people get sold on these before and after images.  They have this before and after. And everybody thinks that when they perform whatever program or engage in any program, I can't speak today for some reason, that they're going to get this body. And that's what sells them, that image of a body. Instead of just getting the fundamentals worked out, so it's sustainable for a very long time. This is why people go on these flip-flop diets, the yo-yo diets they're called.  So it mucks up everything. So my suggestion is to start with the diet. Get your food, because I believe 90% of your health comes from what you put in your body. The workout should be the cherry on the cake, no pun intended. I mean, it always makes sense to be an active person. You do not want to sit in front of the television and binge watch, even if you're on a good diet. It's just probably not a good idea to be sedentary. Some people have sedentary jobs, you know, a lot of the tech jobs, nobody's really doing anything. That's why they feel that they have to compensate with some activity. And I guess busy people have to go to the gym just to get their fitness or stretch their body out. Sure, I guess why not, but don't make it into this crazy thing where you think that you're working out is making a difference. If you have to squeeze in a little bit of activity now and then, that's probably not a bad thing, but I wouldn't put too much emphasis on it. Focus on the diet, and that's what we're doing. We've lost probably around 90 pounds since our worst, and I'm guessing I have 10 to 20 more to go before I want to bottom out where I can't really go any lower. I don't want to become emaciated. Obviously, I'm busy too. I work. I have a lot of household responsibilities and kids and so on, and I'm definitely not sitting around. But I'm going to get to the point because I know I have extra body fat to lose, and we're taking our time with it. We're not taking our time in the respect that I'm not doing anything about it. Oh, I'm just going to...  But I have a chart, and it's going down, down, down, down, down. Maybe next year when I truly feel like I'm at the... As far as I can go in terms of perfecting the diet, then we will focus on bringing back the muscle mass. I'm sure you could argue all... If you do have the perfect low carb diet, or a carnivore keto diet, then sure, it probably is not harmful to combine it with a fitness program. But it's still hard to figure out what works. For me, all the things you read aren't true, and they may not even be true for you if it's true for me. So you have to figure out exactly what... Once you can iron out and big stamp of approval your diet, and you know what works and what doesn't, then I suppose it probably wouldn't hurt. I could probably start doing the gym now and quite likely accelerate my achievements. I'll probably drop 20 pounds in two months if I combine this current diet with a serious three to four day a week strength training program. But I just don't want to do it. I want to make sure that I know how far I can go. And it's possible that my current expenditure level for energy is not high enough to lose weight rapidly. I doubt that. I think it will continue getting better. So just be careful with these quick things. The 30 day things. I want 30 day results or two month results. When you correct your food intake, it's going to take a long time. I would say two to three years at least. You'll lose maybe half your weight in the first month or two. And then the last part is always the hardest. Along with the mistakes you make or alcohol, that's the thing I'm working on right now. I'm really trying to find a correlation between alcohol and body fat loss. And I think it was possible, and this is just an initial theory I have, but it was easily possible to lose weight and enjoy regular alcoholic beverages and lose weight. And then you may hit a plateau on the way down to the point where you probably have to go several days in a row every week to get another few pounds knocked off the block. Because I think alcohol in your body, if you don't eat bad, alcohol doesn't necessarily like vodka, for instance, or low carb seltzers. Don't make it gain weight, but they make it a whole lot harder for you to burn that stored body fat. So taking days off, I've noticed when I go on these streaks where I limit my alcohol consumption tremendously, that improves my body fat composition even more. So I'm working that out. If I figure that out, then it's going to be on to building myself back up again. So that's my advice for you. Diet first, figure it out, perfect it. And then get down to where you want to go in terms of body size, clothing size, and then continue the diet and then start your fitness program. That's our recommendation based on experience and observations. Have a good week ahead and enjoy those juicy burgers without the bun.


Should we get started? It's like right on time for being late. Is that like a good thing? So before we start, I have a favor to ask all of you. I am a little bit nervous. And so if you could help me out by every time I take a drink of water, if you could applaud, that would be very useful for me. So let's just practice real quick, pretend I've been talking for a while and you've sort of forgotten about this weird favor I asked you. And then I'm like, OK, yeah, you're so good at that. That's going to happen so many more times. You might get sick of it by the end, but I won't. So OK, I think my slides work. So welcome to RailsConf. Welcome to Kansas City. My name is Lily Shaline. It is not phonetic. Here is how you say it. You can picture Sean Connery addressing Canadian pop legend Celine Dion. A little bit of that list again. Shaline, hopefully you'll remember that forever. So who here is from Kansas City? I am, yeah, it's not true. I don't know who's from Kansas City. I'm from Kansas City. I live in San Francisco now, but I'm super excited for RailsConf to have come to my hometown. So let's see. I'm a software engineer at Omata Health. We help people avoid getting type 2 diabetes via the internet. It's kind of fancy. So I would like to know more about you.  I have. All right, half the room. Have you ever worked with an engineering intern? More people. And who is hiring engineers in general right now? So most people, yeah, OK, that's not surprising in any way. OK, so I'm going to share with you some true stories of internships. Some of the details have been changed. Names have been left out. Some of the people are coworkers I've had at Omata. And some are like stories that I've heard from other people. So I'll tell you which ones are which. So you can be like, oh, yeah, they're wondering the identities of these folks. So the first one is not an Omata person. And this is the CS Hammer. It's a person who starts an internship and they were a recent CS grad and they just wanted to use CS for everything. Everything was a red-black tree. No one wanted to work with this person. It was really sad. They basically, this person went off by himself and just sort of like implemented this interface that they're going to like, we don't need this. And they don't understand why this person wants to do it. And they didn't really want to help him get back on the right track because they had enough work to do that it was like, we don't really have time to get this person to write the code that we actually want to use. So they just kind of ignored him. And then at the end of his internship, they were like, great, it's over. He's leaving. And then they just never did anything with his code. So that's a way to run an internship program. Um, yeah. So another one that I heard about, which was not a Nomada one, was the founder's spouse's cousin was interested in programming. And so they were like, oh, hey, let's start an internship program so this person can get a job here. And it was like, all right. So that's the thing you can do. They ended up deciding to pay all of their interns minimum wage, which is also interesting. So they didn't actually find a lot of good candidates beyond, I don't actually know if the relative was a good candidate or not. They ended up putting all of their interns on these little toy projects that did not matter at all. And it was just kind of this separate thing that nobody else learned from. And it didn't seem like a great idea. So that was kind of sad. Our third intern is a friend of mine, who is the cutting edge cat. Really wanted to use this really cool technology. Like really didn't care about building something useful at all. Ended up putting in, wanted to build a dashboard that showed the number of users logged into the site. So he put in a sidekick job that every minute would report out the number of currently logged in users.  And I deleted his code a few months after the internship was over. But then we hired him because he was actually great despite his terrible, terrible solo project choice.  And then we have just the unabashed, a good one. We just have a really successful internship. This was also somebody at Omata. They were a recent boot camp grad. They were willing to ask a lot of questions, admit their ignorance. And they were just really a pleasure to work with. They worked with our product team to build sort of a lower priority feature, but one that was still user facing. And they copied some patterns in our code base that were just really not great. And we were like, oh yeah, don't just don't do what we did a year ago. Like we had really, really bad taste back then. And so that person was able to get some autonomy, but also support when they needed it. Yeah, and so all of these different internships are going to teach us lessons. Very good, very good. The first one, the CS Hammer. So one thing that you could take from that is don't hire CS grads, because they'll just try to make everything a red-black tree. The actual answer is not that CS is bad, but that giving someone feedback and guiding the intern and actually working with them to create the thing that you want rather than just ignoring them and saying, like, we don't really have time to make you do a good thing. That team also realized just how sort of siloed they were and how they didn't have a really collaborative culture already.  And that's not an effective pattern for bringing on a junior developer. With the relative, you need to have a clear goal in mind that isn't just we want to employ someone's relative.  Yeah, sad. My friend, Andy, he's great. He needed more guidance. We needed to sell him more on the fact that the goal of his internship was not to try out some sexy new technology, that his actually what he could get out of this internship is the collaboration with the rest of the team. And we sort of failed him by letting him like do work on this project that was ended up being pretty dumb. And then from the good one, we learned like a lot of stuff about like our code base that we have these bad patterns that even though we're supporting this person and I think we did a good job of helping them, they still were looking through and seeing things that we were like, oh no, no good, no good at all. So all of these things are audits. An internship program, running an internship program is letting you audit your process, your code. It's helping you see exactly what could be better about it. Okay, because really, sorry, don't move the thing. Okay, because a bad internship really isn't about, is it the intern's fault? Yes, they can contribute to it. Yes, there are like bad programmers and you might hire someone who isn't very effective. But ultimately, a bad internship is looking at it is about seeing what you've done wrong as a company to not support the intern and not to create a structure that could help them succeed. The structure of your internship matters.  And you'll probably mess it up initially. You're probably your first internship you ever run, probably won't be as great, but you'll iterate and get better at it if you're thinking critically. So a quick note on nomenclature. So I've said intern probably 65 times so far. And I'm gonna keep saying intern, but you might say something more like apprentice. I think the patterns that I'm talking about are often called apprenticeships at other companies. You might also just, these are good techniques for onboarding junior developers in general if you've hired them on to a full-time position. And they can come from a lot of different places. I think a lot of people think intern and they think a summer CS student, but they could be someone on a co-op program where they have a whole semester and then you could also have boot camp grads. So boot camp grads or internal transfers, people who were in support or design who want to get into development. So these people can come from a lot of different places in your company or from outside of your company. Okay, so that's enough about why internships are useful. I'm gonna talk a little bit about how we run them at Omata. I think we have a pretty good way of doing it, but can we just take a really quick break and just stand up for a second? We just do that. I mean really helpful. So stand with your feet about hip distance apart and roll forward and back on your feet a little bit. Ah, it's nice. Like lift your arms up and kind of stretch up and kind of stretch over to whichever side you feel like, but press the opposite foot down so that you're actually really getting a good side stretch. So, yeah, that's nice. Okay, thank you for your drink of water. Thank you. So how can you do this? The first thing you need to do is you need to make the business case. An internship program costs money, it costs time. And so you need to convince management that there's actually like a good outcome and it's not just charity work. One thing that this talk is like the slides are mostly just big words on slides. It's like not super useful to go back to. So I've done two blog post versions of this. So literally published right now. So I scheduled those. And so you can go to our tech blog and I'll have the link at the end. So you can use this stuff to try to convince your management team that the internship programs are actually really useful and that you should set one up and then how to do it. Because if you don't have buy-in for management, you shouldn't run an internship program. You just definitely don't do it if you can't pay them and take the time to really support the interns because you're not gonna get as much out of it if you're scrambling and they're not gonna have a good time if you don't have time to support them. And so yeah, having goals is really important. So for Omada, we want to make sure our onboarding game is always on point. We wanna make sure that we're really good at teaching and sort of knowledge transfer. I hate that phrase, knowledge transfer. Like it's really so corporate and weird but people seem to like it better than teaching because they think teaching is like where you're in front of a classroom and you're like, I don't wanna teach people programming and I'm like, you're doing it every day with your colleagues anyway. So, and then we also really appreciate like the different backgrounds that people who come in as interns have. And so they bring a lot of like fresh ideas and they ask a lot of questions about our process and that helps us. So how do we roll? How we roll? I really like this GIF. That's a hedgehog. The toilet paper roll on its face. Just in case you needed narration. All right, so the way an Omada internship works is we start with pairing for about a month or six weeks and then we have them go on a solo project for another month or six weeks and then finally back to the pairing again. It's a pretty straightforward process and they always have a mentor who is someone from their team. And so you might wonder what kinds of teams can support an intern. Don't have a team of all interns. I would try to avoid that. You hear about this like in San Francisco where like people will hire one boot camp grad and then three months later they'll hire another boot camp grad and another one and then you're like, oh no, this doesn't seem good for like the boot campers or the company so you know, avoid that. At Omada we usually have on a team one to two seniors, one to two mid level devs and one to two junior or interns. I joined a team of about three and a half engineers when I first started at Omada and it was super useful. So if you have three engineers you can probably support an intern. Thank you. Stickin' with it. So we do pair programming at Omada. Could you raise your hand relative to the amount of pair programming you do? So I do like 80% pair programming at my company. If you don't pair, put no hands up. Okay, so me like five, six, awesome. Okay, does everybody know what pair programming is mostly? Cool, you know what pair programming isn't? It isn't that thing where you go over to your coworkers computer and look over their shoulder and help them when they got stuck. Pair programming is when there is one computer, two keyboards, two mice, sometimes two monitors if you're fancy. So just try to like socialize that to your team. Like don't say like, oh yeah, we pair like when it gets stuck or when we need to make really big architectural decisions. It's like, no that's not pairing. So anyway, rant over. I like pair programming because it helps us have fewer silos. Communication and teaching skill is expected of people in pair programming environments. You're not just gonna be by yourself so you should be able to communicate to your pair what's going on. And onboarding is so much easier. Just pairing with someone and they get to ship production code on the first day and it's like the next story in the backlog which I really like. So you might think like, oh great, we don't pair but like pairing would be super useful for an intern, right? And I actually would not recommend starting pairing with an intern because pairing across skill levels is a completely different beast than pairing with someone approximately the same skill level as you. Pairing with someone who is around the same skill level is like, for me very fun. There's like a little flow and I like pairing with interns but it's a lot slower. So I would not recommend starting pairing with an intern but start pairing with your current colleagues. Do it, try it, it's really fun, I like it. Just need some more keyboards. If you are pairing with an intern you wanna make sure you let them type. It's really easy just to grab the keyboard or even if you're not pairing but you're just walking through a problem with them. It's really easy if you see a test that's failing that you don't expect to just grab the keyboard immediately and not work through the problem with them. Some of the people that I have a ton of respect for that I've paired with have grabbed the keyboard just immediately upon being confused because it's really hard to just stop and talk it through.  So you're probably gonna start with something like a solo project and code review is gonna be really important. Hopefully you do have a code review practice. If you don't, you should like do that. So once you have an intern and they're working on stuff you are going to learn sad things unfortunately. So bummer, sad thing, number one, you already know your code is confusing. Bart is sad, aw. But yeah, you know that, you know because but you might have forgotten that like that model name that was named that thing because back in like 2011 there was a different thing and then we sort of changed what it did but we didn't change the name because like find and replace is like really hard. You might have to write a migration. Like I don't wanna do that. So you have to explain to someone sort of like how that works but you've basically gotten used to all of the weird things in your code base and you might have some like Stockholm syndrome with your code base. Like yeah, I do. And the bummer is pretty soon your intern is actually gonna get used to it too. So it's important to have regularly occurring interns and regularly bringing people on so they have those fresh eyes and are like why are you doing this? And encouraging interns to ask why even if they're not like it can be hard to question sort of an existing code base if you're more junior. But that is so much their value. So if any of you are current interns please start asking why every day about at least one thing if not five times a day. The second sad thing that you're gonna learn is that some people are just not good teachers.  Like it could have been nicer because you wanna watch out for snark for judgment for people who aren't letting the intern like really do their best work and then coach those people because good news teaching is a skill that you could learn. People are not born teachers. Some people might be socialized to be more empathetic but all human beings can learn the skill of teaching. They just have to try. So one other thing about that is that sometimes as an intern at least for me I felt like it was important that I teach people how to teach me. So if I was working with someone who wasn't a very good teacher I'd be like oh if I could just like ask the perfect question maybe they could like explain this thing to me and then it just would not happen. And so reminding your interns that it's not their job to teach the teachers like they should really just they give feedback to you or their mentor or the managers because yeah it's not their job. Everybody out there is gonna be really wondering why there's like all this very polite applause every few minutes. Cool so the solo project is a huge part of running an internship program after I was pairing for about a month at Omata and then I had to write my first controller spec. I was like oh what are you doing? I had written so many specs with my pairs but I'd never had to write one by myself really. So then I got some code review and it was like you know these if statements like you should probably have tests for those paths or paths and maybe you should TDD those and I was like oh yeah that thing we've been doing really consistently but then I stopped doing as soon as I was by myself. Yeah so the solo project is super good for learning and sort of integrating some of the things. I've talked about this a little bit before but picking a project I think is pretty important for how much the intern gets out of their internship or at least their solo project. One of our most recent interns worked directly with the product team to add a thing as I mentioned earlier and it was just really awesome to see her like go and like pair with her ahead of time and then have her solo and learn a bunch of stuff and then come back to the team and like just know so much more and just have a lot more like confidence was really cool. Yeah so the next up is code review. So it's really important during the solo project obviously it's really important if you don't pair program. We're sort of of the pairing is inline code review school so we actually just all like if it has a pair we just push to master and say goodbye. Y'all might pair and then do code review that seems cool too. So in person code review is really great if you can if you're a co-located team. I don't know how you would run an internship program distributedly but if somebody can give a talk next year about that that would be cool because my team is co-located. So it feels straightforward compared to what I think distributed would be. And let's see so last year at RailsConf Derek Pryor gave a talk about code review and you should totes watch it because it's so wonderful and he talks a lot about how written communication is just inherently more emotionally ambiguous and that's I think especially important when you're working with an intern. Really all of your colleagues you should be like treating with a lot of care and respect but please do check out his talk about code review. Our mentorship is set up kind of from the beginning so it's usually a team lead but it can sometimes be someone else from the team it's a nice opportunity for someone who's sort of management curious to see what it feels like to be in that role. The mentorship is helpful if it's scheduled during the solo project so if you actually have like a five o'clock check-in every day with the intern it's really useful we learned that the hard way by like a couple weeks into the solo project being like hey how's that thing you're working on and you're just like oh my god like wow but you didn't say it out loud you just felt it in your heart because you wouldn't want to make them sad and make like reveal how horrified you were. So we've started doing like scheduled check-ins every day which is really useful for the intern to be able to know that that is their time and then obviously the team is interruptible throughout the day if they have a question if they're stuck on something we don't want someone to have to wait from like 9.30 in the morning all the way to 5 p.m. if they're stuck they can definitely talk to the rest of us. So if you're a consultancy that's kind of different we're a product company so like the cost of an intern just sort of gets rolled into the cost of existing. When you're actually looking at developer hours and paying that person money I don't have a slide for this but you have to pay interns don't ever do a free internship also the law is like wants you to pay them because if they benefit your company then like you kind of need to yeah pay them because that's how that works so sorry aside. Some companies I've heard of some consultancies will bill at a discounted rate from the intern from the very beginning sometimes they'll start billing later in the internship so they'll start doing kind of like internal toy projects and then sort of like ramp up once people are a little bit more confident. I think the how long it's gonna be before you can bill for an intern is gonna depend a lot on their skills coming into the internship. If you have someone who's super super fresh it might take a little bit longer. And then I've also heard of consultancies where an intern will work on a single client project for some period of time for like the duration of their internship and then get hired on by the client at the end of it. So everybody's happy, jobs at the end. It's so much less awkward because you don't have just like listened to me drink the water, I really like it. Okay so secret bonus thing about running an internship program is it's super rad for making your team more diverse. Hiring interns is not the only part of the strategy of making a diverse team because having a diverse team where like all of your seniors are white dudes and all of your juniors are not, like that really sucks, so don't do that. But it's like still kind of cool because it is a way that might be a little bit easier to diversify your team. So some statistics for you. So a rough percentage of people who are women, software engineers, we have about 16% of software engineers are women according to LinkedIn. They probably know like a couple of things, right? 18% of CS grads are women according to the National Science Foundation. And 38% of bootcamp grads are women. What, that's so many more. According to 432 surveyed in 2014. I have no idea whether that's like a good sample size or not. I don't know anything about statistics but it seems pretty cool that 38% of the people who took that survey were women. So if you wanna get more women on your team, having bootcamp grads do an internship or something and then join your team is a great way to do it. The stats on race are like way more depressing. I don't actually understand why the people, so the bootcamp survey, this was their like race box and I was like, what is other? Like, could you really not have more than four options? Like, I'm just really frustrating. I don't know what it is. But it's not nearly as sort of exciting or like the statistics are not as like, oh yeah, this is gonna be a slam dunk. So you, to find like people of color and other underrepresented groups, you're still gonna have to put in some more elbow grease. And so to do that, you really wanna make sure that you're posting outside of your usual networks. If you run an internship program and all you do is like email like current employees friends or if you don't put a posting up or if you like only put it up on your website and don't tell anybody, it's not, you're only gonna find the people who would already kind of clued into your company. And then you also, you can work with organizations like Railsbridge or Code2040 to help them know that you have an internship program and then awesome people will come your way. Half of our female developers came to Omada via internships via Railsbridge. So that's cool. And so yeah, when you are recruiting and interviewing interns, we tend to like just have a little bit of a less strenuous process. We start with a code challenge where they need to fix some broken tests. It's amazing how many people don't follow directions and they're just like, oh, I don't like this test. I'm just gonna change it. And it's like, no, that's like the whole point. Just make the test pass. They still do it. It's useful though, right? Cause then they just don't move on. And then they have a phone screen. They get past the code challenge, short one with a manager. And then if that goes well, we bring them in for a pairing interview. If you're hiring people based on not on their current technical skill, if you're hiring people cause they ask good questions and they have a lot of potential, you're not gonna wanna ask them like algorithms or like whiteboarding things. So just like stop doing that entirely but also stop doing that for everyone in addition to interns. If you could do that for me, that'd be great. So one of the cool things about our internship program is it really helps us also retain current developers. We use the same sort of structure for team rotations. So last fall, I did a three month rotation on to our ops team and it was so awesome. Like I spent, like I literally did like a month of pairing in with the team, a month of a solo project where I just like fought with Nagios and then a month back with the team. And when I got done, I was like, I knew a lot more about monitoring than I started. So I highly recommend doing this kind of thing within your teams cause engineers, like we wanna learn new stuff and we wanna expand our skill set. So give that a shot. So there are a few things that I would change about Omada's internship program. I'd be interested in potentially just hiring these people as junior engineers instead of giving them this like three or four month long like audition where it's like we might give you a job at the end if everything works out. It's nice cause it's like way less commitment and you get to like take chances on people if you're like, well it's fine. Like not giving someone a job is obviously easier than firing someone but it still feels kind of like me to me. I'd be interested in potentially calling our interns apprentices if we're planning on hiring them at the end cause it seems like maybe like the word that people use more. Maybe we should give them health insurance. My bosses are gonna be really excited that I'm just saying all these things. They're gonna love it. And then I would love to see us and I know we're planning on doing this but we haven't done it yet is posting our internship openings to the job boards at like historically black colleges and universities just so that we can sort of like we have a lot of women in tech sort of organizations that we work with but I'd really like to see us focus more on getting more people of color onto our team. So all of this what I'd like to leave you with is that audits are helpful. It's a little bit painful when an intern comes on and it's like it's really hard to explain this part of the code base or they ask like why do you point and then everyone's like oh I don't actually know what is pointing. It's a good pain. It's good to like recognize the things that are not great on your team and then improve them. And doing so will help you like hire and retain awesome people. It'll keep your team on your toes and you'll be better at making software. So that's it. One more drink of water.


Scientists have listed three deltas in the world most affected by rising sea levels, namely the Ganges, Brahmaputra in Bangladesh, the Nile in Egypt, and a Mekong Delta in Vietnam. Sea level rises are destroying coastlines and protected forests, jeopardizing human lives and the food security of approximately 18 million people living along the Mekong Delta in Vietnam. Khamau is the southernmost region of the S-shaped country of Vietnam. Bordered on two sides by the East Sea and the Gulf of Thailand, its 254 kilometer long coastline spanning from east to west is hippified by its wetlands. The profits lies at a crucial strategic position along the Mekong Delta and serves as a critical biosphere reserve for the region and the world. Apart from its modern significance, every inch of the sacred land in Khamau cave that was discovered by the Vietnamese of antiquity has been preserved by generations through the peaks and troughs and the twists and turns of the country's long history. Scientists estimate that every year tens of meters of seawater intrude inland. The sea level rise in Khamau averages from 1 millimeter to 4 millimeters and is showing increasingly serious signs that this land is at risk of disappearing, jeopardizing the lives of millions of coastal residents who rely on the sea. In fact in 1997 when he first moved here, Mr. Thai's house was still a kilometer away from the estuary covered by other houses, but after only 25 years the house is now highly prone and vulnerable to rising ocean waves. The sea has been intruded at an exponential rate. The house could collapse amidst any fierce storm. Lying in the house, he can even hear the sound of waves crashing and can feel the shaking. Mr. Thai has hardly had a sound night of sleep for a month now. Only the children of the Hamlet remain carefree. They have become accustomed to putting up temporary accommodations around the village. They are also used to skipping school early when studying in the classroom leaves them in as precarious a situation as their families home before the storm. On the other side of the west bank of Khamau Sea, Mr. Lao often paddles his canoe to the area where the family's old house off the coast has been eroded. What is left now only includes an old broken boat and the foundation of his family's house after the evacuation. Previously this mud flat was home to his family and dozens of households earning their livelihood through local fishing. The west coast used to be miles away from the sea, but after only about 15 years the sea drowned these houses. Mr. Lao's family was the last family to leave here when the waves already flooded the floor. Now only the old floors remain with concrete piles, remnants of the days of living at the stormy estuary. Mr. Lao misses the old house so dearly where his three children grew up, where his grandchildren were born and where he lived by the sea to support his family. The sea has sustained the fishermen offering them an abundance of fish and shrimp, but it is also engulfed houses in stormy weather. For a few years now, Mr. Lao has had to move with other families in the village to a resettlement area deep inland. In previous years, fishermen like him could go fishing all year long. But now the time left to go out to sea is only about four months. During this violent swell, Mr. Lao cannot go fishing and has nothing to do but hang out with the other fishermen in the hamlet. To deal with such unexpected leisure time, many people in the hamlet bring fishing gear to prepare and get ready for the next sea trip. Every rainy season, the sea of Kamau becomes less gentle. The waves roar day and night, encroaching the coast, washing away the coastal protected forests. Where the highest forest belt is only 70 meters, in some places only 30 to 40 meters. More seriously, in many places on the west coast, the forest belt is only about 30 meters. This used to be the land of mangrove forests growing in the wetlands and brackish water of Kamau Province and accounting for more than 70% of the region's mangrove forests in the Mekong Delta, which spanned more than 100,000 hectares in 2011, but has gradually been shrinking. More seriously, out of the 254 kilometers stretching from the east to the west coast of Kamau Province, 189 kilometers have been deteriorated by landslides, which can be attributed to the impacts of coastal currents and tides, especially big waves and high winds from the rise in Silam. According to the latest climate change scenario issued by the Ministry of Natural Resources and Environment, climate change is forecasted to impose a strong impact on people's lives in Kamau. In particular, by 2040, Kamau is expected to have more than 4,600 kilometers squared of land flooded from 1 to 1.2 meters under the 25 centimeter sea level rise scenario, accounting for 85.4% of total natural area of this locality. Rising water and land subsistence processes occur simultaneously, while environmental pollution and excessive rain also affect the main livelihood activities in Kamau water such as fishing and aquaculture. This not only affects the sustainability of the master plans of Kamau Province and the Mekong Delta, but also affects the food security of the country and the region. The tides keep rising day by day. Rises in sea level will continue to make many areas of coastland and headlands more vulnerable, coping and adapting to even a small change to the natural environment can create a big impact. Not only on nature, but on the humble people living on the strip of land at the end of Vietnam who are dealing every day with the waves and winds. There has always been a persistent inner strength among them, deeply rooted, rising up strongly on this land amidst the harshness of natural disasters. Today, on the west coast of Kamau, Mr. Tai brought his grandson back to the old mudlands to remind the children of the house where they were born, the trauma that the coastal people have experienced to understand the ferocity of nature and to learn to live with it. The sea is fierce but also full of tolerance. The sacred cape is still preserved by the mangrove trunks that have risen out of the old house, although it will take more time for them to take root and stand firmly on this turbulent shore.