This is it, three, two, one. This may very well be the wokest Asian clip that mainstream television has ever made. Welcome everybody to the hot pop. Boys, David and Adrian here. We've got a little different set up today. Let me know in the comments down below what you think. But first, we are going to be talking about this Grey's Anatomy scene that is bringing some Asian Americans two tears. Let's run the clip. When I was a kid, I used to stare at my face in the mirror and wonder if I could use my mom's makeup to make me look more American, which of course I understood to mean more white. You want to be like all the other kids? I had my teachers and people I saw in movies and on TV. I wanted to feel normal and get along.  We are Americans. Your face is the American. I wasn't called for help. No one intervened or even took a video. I'm just kidding guys. It was emotional. It was very well made. Listen guys, Yahoo posted this clip so I know it's going viral. Of course, Reddit had its classical range of responses. Some people loved it. Some people hated it. Some people were in the middle, but guess what? We're going to break it down from the micro perspective to the mid to the macro. So make sure you like this video. If you like what we're about to do. Alright everybody, let's start off with the micro. David, really what is this scene about? I mean, I know people just saw it, but quick breakdown. This scene is trying to encapsulate a dramatized version of what might happen in real life if a bunch of Asian doctors had to solve an old Asian lady that was attacked in an Asian hate crime.   And basically the sadness is coming, right? Some doctors are like, why'd they do this? She didn't even do anything. She's like, will they ever accept us in this country? They're blaming us for COVID. And then this old Japanese lady comes in and says, yeah, don't ever question it.   And somebody in the observation room who's another doctor is just like, nobody even called the police. Nobody tried to stop. Nobody cares about us. I can't believe it.  But I don't know what to do. I mean, I thought the scene overall was a pretty good job of encapsulating a lot of people's initial emotions of like a year and a half ago when this stuff started to happen. Now maybe that's when they wrote the scene and then they performed it and then it finally came out. But overall, like these are emotions that I feel like a lot of people have been through a while ago. Now my question is like, you know, for some Asians they really don't get the message unless it's wrapped up in a high-budget TV show or movie because some people need it to be dramatized with the good lighting and editing for them to really get hit by it because they don't really like having the street conversations or watching the YouTube videos about this type of stuff. Or you might not live in a ultra-dense urban environment. I mean, obviously we live in New York City where a lot of this stuff is happening on a day-to-day basis. Also, I think for the 35 and up generation, you know, they're not tapped into social media. A lot of these discussions that we have, Andrew, that are very difficult harsh realities on comfortable truths, they take place on social media but they don't take place with like a Grey's Anatomy budget with a nice refinement in the polish. Some people need those things. You know, some people needed everything everywhere all at once to reconsider their relationship with their mom. You know, but that's just how human nature is.  It's fair. All right, let's go on to the mid real quick because I got some questions for Asian-Americans out there. You let me know in the comments down below what you think. I think one of the main questions that was brought up from Alex Landy's doctor character when he goes, do you think they'll ever stop seeing us as foreigners? And I'm like, man, you know, it's such like a fragile thing to put your American-ness in the hands of people who never want to give it to you. Like there's a lot of nice people out there who will grant you your American-ness. The law will grant you your American-ness.   So I'm just like, you know what, at some point either you don't care about what those people say or you don't care about being considered American as a whole.  To be honest, to answer Alex Landy's character, I know those aren't his words. They just, what the writer wrote for this character. But I'm just saying that it's like, to be honest, I think more Asians need to study more American history as well as Asian history. And we'd understand how Asian or American we are. You know, America has always had this question of like, who's American, right? Anglo-Protestant people come. They essentially like wipe out all the Native Americans. Are the Native Americans American? They were here first, right? But then Irish people come that are Catholic. Italians come that are Catholic. And at one point, Irish and Italians are not considered white. Then Latinos and Asians come even more different looking people. They enter white status. We're not American, right? Because we're like the new groups that arrive in Mass in 1960, 1970. So this type of question that Alex Landy is asking is very tenuous because it's like, you're putting your validation on an outside group that has probably some self-incentive. And you know, the reactions are mixed to not accept you. So obviously as an Asian American, Andrew, you're saying you don't like that question because it's like, hey, will you give me something you don't want to give me? And then, well, can I hinge my feelings on how you're feeling about me? No, I mean, at some point, as an American, you've done the work and you are an American and just nobody can take that away from you because it's also built into your passport. Whether or not other people identify, whether or not you're wearing the American flag on your forehead, like you got to just believe that you're American. Or like I said, stop giving an F if people think you're American or not and just being like, I don't even know what that means. I'll tell you this. I've been to Texas where people are like Billy Bob and stuff like that, the educated people, they actually tend to be still less nativist. They tend to be like, well, if you're about American philosophies, not all of them, but like, more than you think it has to do with education, not necessarily just geography of how people feel about you because education and the tribalism levels and the visual presentation all kind of go together. I will say this, Andrew, the last thing, my last point about the mid, there's nothing more American than de-gaffing whether or not people see you as American. Yeah, you're right. Think about it. The most rebellious art forms come from America, rock, rap, hyper-American art forms, super rebellious.  You just go get yours. That's very American, you know? All right, David, moving on to the macro. Let's zoom out. What's the analogy that you can wrap this all up in? All right, so I'll say this, and I got to shout out to the Grey's Anatomies writers because it sparked a very interesting analogy in my mind. Imagine we're all in college, Andrew. There's this huge frat party that we're all trying to get into. Oh, frat parties. There's a side yard. There's a main room. You know, people are hot boxing in the garage, doing keg stands in another room, whatever, right? There's a bunch of Asians trying to get into the frat party. The frat party, by the way, is America. So some of us, we're trying to get to the door, right? But then they're looking at all these Asians, right? And they're like, I don't know. Maybe some of you guys are cool, especially the pretty girls, and then maybe some of the super cool dudes. You guys are cool, but everybody else is not cool.  But while we're like knocking on the front door, Andrew, people are throwing juice and beer bottles down from the second floor. These are the bad actors, right? So some of us are getting hit with beer bottles. Some of us are getting splashed with like Hawaiian punch, right? Some people are on the back of the line, not experiencing any of this. And some people hit the right attributes, whether they're a super pretty girl or a cool dude or whatever. And they go into the side yard into the cornhole spritzer zone. You know where people are sipping mimosas and playing darts, but it's not the main room where you know like Kid LaRoy and 24K are playing in the main like rap room or whatever. It's a side yard room, but they're in there and it's comfortable and nobody attacks you and people treat you nice and it's part of the main infrastructure, but it's a second tier room. So you're saying it's the set, it's almost like a purgatory perhaps or some type of middle stage. I would more compare it to the base pod at EDM versus Kinetic, the main stage.  When you're Joe Rogan, Andrew Schultz, you know the hyper-mericant mainstream cultures. They're not in the main room where like you know other college students are hooking up with all the hot athletes and vice versa, but this is the cornhole side where it's like these are nice people. It's yuppieism. It's yuppieism. I mean, it's essentially where the doctors are in Grey's Anatomy. So like I said, there's this huge variance and experience amongst the Asian-Americans. Some of the Asian-Americans that are way in the back of the line they figure they're never getting in. They're starting a party at a rambler across the street, Alpha Zeta Nu, AZN. It's a new frat. It's right next to the Latino frat and the African-American frat in rambler houses across from this nice frat. Some people are like mad that they see it happen. Some people are still like, I'm getting in there. And other people are, like we said, are in the cornhole side. Like some of the people in the cornhole side are just like, ah, thank God I got in here. F everybody else. And other people are just oblivious. Like, yeah, why isn't everybody here? I thought that that was the naps. Like everybody could get in, they got in. But actually they were hyper-selective to get in.  Whether they got hit with a beer bottle or whatever reason they got beat up and they stumbled their way into the cornhole side and now they're like have cognitive dissonance and they're surprised and they have to have a reaction to it. So the people on the cornhole, they meet these people who are coming from the outside being like, what? You couldn't get in the party this whole time and then what? They threw beer bottles on you? Oh my gosh. I'm here playing cornhole with the spritzer and the light beers. And the nice white people. I thought it was all good. We're having seltzer. This is where the trulys are in the white claws. Right. Yeah. I'm out here partying with like the whole cast of like Big Bang Theory and Silicon Valley and all that nice whites. So where would we be? Where would the fungrows be? Are we like selling vape pens to the outside or no, we're in between the streets of the two parties being like, hey, if you guys want to leave the cornhole side coming to the Alpha Zeta new party over here. We could either be like some sort of comedian DJ that's like trying to offer our services to the black frat, the Latino frat, the AZN frat and the white frat or probably selling like vape cartridges. But that's what gives us our perspective, Andrew because we've probably like not been only native organically to one of the groups, you know, because there's so many different players in this equation, the scene that I painted. But we've been like visitors to everywhere. Oh, you know what it is? We might be trying to float around to the different cornhole sections of the other parties too. Oh, okay, yes. They got yards too. I don't know if they're playing cornhole. They might be playing basketball. Yeah, maybe they're playing basketball in the front or we hop in a game and then we hop out. But we're not really in the main room of maybe any of the parties. So anyway, for the Asian one.  They're not in the Joe Rogan section. Joe Rogan doesn't care about Asians. He doesn't like Asian things. But they're over here and they're like seeing it. And they're seeing this old lady who was obviously probably a poor elderly person that nobody identified with. She's a victim of this vicious attack. And they have to start to consider how much do I identify with this lady? We're of the same, you know, race or ethnicity or country background. And that's actually the situation Andrew that a lot of yappy yuppies that have assimilated to a certain extent in America are going through right now. So Grey's Anatomy, kudos to you. Made me think of this analogy. Shout out to Grey's Anatomy. Now, what do you think should happen? Well, I'm going to leave it up to people who are watching. You know, I want to hear your thoughts because you heard our thoughts for a while. Obviously, my plan would be that the people probably in the cornhole understand the structure of what's going on and the help somehow, but it's difficult to understand how to help because they don't even run the search of their end. And honestly, the whole idea of people from the cornhole leaving that and then starting their own auxiliary party on the side of the side. It seems unlikely though. It's just not likely to happen. They should take what they learned from the advanced white frats cornhole to start cornhole at Alpha Z to New. And I think that's starting to happen on some level. We know some of the organizations sort of that are doing that.  Well, they care about, I'll tell you this, a lot of Asians seemingly, and this is not all Asians, they care a lot about the comfortable metric more than maybe like the pride metric. Hey, you guys, let us know in the comments down below. There's a lot of food for thought right there, every front thing from David's analogy to the questions we posed in the mid. You know, because we always like to take things from the micro to the mid to the macro. Those are three different ways to view things. So you let us know in the comments down below. We are the Hot Pop Boys. And until next time, we out. Peace.


Hello, Lavaz. If you guys don't recognize this set, this is the set of Shan Budi is your perfect date We are in season two at this point. Season one was all about creating a connection with anybody without the help of hair Makeup and wardrobe just really sitting across from somebody and bonding season two every single date that I go on I'm doing a different Psychological sex love and relationship based experiment, but I have zero idea how they work in practice So this is the episode where we get the complete unfiltered unedited raw feedback from all the guys I've been dating you're a step above Yeah, you're a staircase above dating a porn star. Was there like a menu before because I didn't get to pick this Did you pick yours? Here what you can cheers on this one. I'm trying to get some of this off so that works great Perfect. I think that all men should date a stripper at least once in their life and you're 12 Bring the motherfucking ruckus. I'm gonna get gray hair by the time I'm 32 products So all season long while you guys are watching each episode and seeing what people say about me I actually have no idea I want to know that these lessons can work for you guys that they are Transferable to anybody so to refresh everybody my hypothesis is that 80% of these guys will say yes to a second date And eight out of ten of these experiments are going to work that being said let's roll on into our first Experiment which is she's got the look with Evan Gomez this experiment was really to prove that season one was true That looks were not everything so I dressed myself up to look like Evan's ideal type But I was the exact opposite mental of what he wanted in a woman You may have forgotten who should head Shan was aren't you kind of small to play football? But what really counts is what Evan thought let's go see where do I begin with my date with Shannon? Speechless is this girl racist is she insulting me on purpose or just like Accidentally, and I was like oh, it's accidentally even better You know you're not sure if it's getting across it definitely got all across I feel bad It actually feels kind of sad to hear some of you refer to me as racist I don't want to be that person were there any qualities that attracted me to Shannon physically speaking. Yeah She's a pretty girl. I'm into light eyes body style was on point and she seemed to have a nice simple sense of style That I also appreciate it that is exactly what I needed to hear So if he says no to a second date that proves 100% that looks alone are not enough Would I go on a second date with Shannon?  What is one thing that I had to know about you?  So I don't really know how he felt But we're gonna find out I I think shana is great. I think she's intelligent Smart a conversationalist, you know, very Sure of herself And and her confidence came through and the way that she even asked and posed questions Well, the questions were kind of can I think it's cool about that is that people love Talking about themselves so much that even if you're going through a list of 36 questions And you are hardly talking about yourself ever to them They're like, yeah, like she was really open and forward thinking and funny and honest when motherfucker I'm just asking you questions. I would go on a second date with shannon Because I think she's an excellent person and I would love to explore that. Yay So we got yes to second date But the main question of course is did he feel a feeling close to love? A strong bond and connection with me because of the 36 questions I think that there was a genuine moment where we connected, you know The questions I thought they were really great and making me feel comfortable Um and connected and feeling like okay, well, I can open up and share this information with this individual I think I'm going to keep a lot of those questions I think that they're they're great first date questions. Awesome Okay, that kind of made me feel sad a bit because it's like, oh jokes on you Thanks for telling us all your private information But it was for science and if lamar was a little butthurt that is worth it because you guys now know the truth That these questions work this experiment works We got a second date and we got yes to the experiment And so take these questions and go forth with them and multiply Unless you don't want kids then don't Rolling out of that one we're going to experiment number three, which is mama's boy So instead of researching grant our day if you guys recall I go skiing a lot I sometimes wear this like ducky onesie. I got a target for like 15 bucks And so I researched Andrea his mom her mannerisms her hairstyle the way that she dressed We wanted to give him that same mom kind of feeling But the question is not only did it work, but did he recognize the fact that like, yeah I do want someone who reminds me of my mother. She was really cool She was she was really dope. Um I like the vibe. I like the the outfit the hair the eye like the whole thing the whole package was a nice one I felt like there was there was chemistry there for sure an enhanced familiarity between us That seems really promising off the top. First of all guys, I would never wear my hair like that So the fact that he liked my hair like that which is Andrea's hair. Nope. No offense to you, Andrea It's a fly-ass hairstyle, you know, I'm sure in your in your neighborhood, but not in mine This is a step in the right direction. I feel like the familiarity the liking of the look Maybe we can already call it. Yes. I would you know, like I would love to go on a second date with her So yes a second date though. That's good. So we're halfway there Did we get the most important one though? Okay, now that I know those facts I I mean the physical attributes the even the the the shirt the hair She's trying to be like my mom and I can see that my mom and I have a semi-close semi-strained relationship at times and I don't really look for somebody that's like my mom Now I want to know how she really is because now it's Not date my mom I don't expect people to own up to the fact that they're looking to date their parent Which is kind of creepy. So I do think that this was an absolute success Like he said I had the look down. He felt the connection. He felt the familiarity What other proof do you need? So I feel like we're in great shape right now and it can only get better I hope moving on number four was sex sells with tim. How about yourself? I don't think I can see the kind of nuts I prefer but I think second to that would be We use sexual innuendos. We use aphrodisiacs I used fertile arousal based makeup and I made myself look as horny as possible without being a dead giveaway To see if we could incite sexual feelings without of course being overly lewd crude and sexual So it's a really bland date. If you guys just listen to the audio of the date I work basically off and on the coast of southern california from san diego up to san Luis abismo But if you watched it Other parts of you would wake up. I promise you that but did tim get woken up though My date with shanna went pretty well I think shanna made me feel a little comfortable when she squeezed the lemon in the glass and it's spelt out And just kind of the fact that she actually made a little bit of a hiccup there and made me relax even more Come on. I made a lemon. Come. I'm feeling a little discouraged right now because the date that I was on I was jacking off a water bottle and molesting some avocados the date that he was on I was humble nice immigrant turtleneck Yes, I would absolutely go on a second date with shannon Because I would like to get to know her better. She was very humble and mellow And I also she was just very nice and it's rare to meet nice people like her these days Hopefully once it's revealed to him then he's like, okay, I'm gonna be honest with you guys. I still got a boner That's what I'm hoping for but it's kind of seeming like that's not the case So, yes, I felt a stronger sexual connection on this date Related to other dates that I've been on in the past Even though I didn't pick up on it and at that moment I think some of the things she was doing such as the avocado rubbing definitely just naturally being a guy processes Hey, this is sexual All right, that sounds like good news that the sexual innuendos again We're speaking to the subconscious that maybe he didn't really realize him at the time But he knew for some reason he felt more sexually attracted to me than he would on normal dates So I would say that even though he is like the dorkiest The most whale penis guy out there This experiment was a success and a testament to the fact that you should go with science over sleazy The results are just the same. You go and get you some Rolling on last but not least I went on 10 dates with 10 different dudes I had 10 minutes for our speed dating episode Now this one the goal was to try to recreate season one, but instead of having 10 episodes We had one episode. Okay, so I don't remember none of y'all names But I am extremely excited to see what you over there has to say Shannon was very elegant very pretty It's fun kind of vibrant. She was willing to play a game like on the fly She's willing to lose and like still be cool about it. She goes around giving people advice on aids I don't go around giving people advice on on aids to talk about hiv prevention and of course living with it But nonetheless, the goal here was to make that fiery first impression I think we did that but do they want second dates? Yeah, I would absolutely go on a second date with her. Definitely. Absolutely. Yeah, I would absolutely I would go on a second date. I would definitely go on a second date with Shannon. Yes. Yes, definitely I'm an open-minded person. I would go for it So I would go on a second date with Shannon to maybe perhaps a meal or a musical venue And that could be chicken tandoori We got a hundred percent second dates in that one, which is actually above what I hypothesized So we're doing good so far. Yeah, I definitely think there's a possibility. It could be an ideal match Yeah, I think Shannon and I were made for each other. She's definitely somebody I can see myself being with Yes, I definitely can think that I would like to go in that direction For myself, I would prefer to have some time to get to know the person better I don't think you can really grasp a person that quickly. That's kind of early to figure out if she's an ideal match Yes, Shannon would be the perfect girl for me. It's not going to do better than Shannon All right, so we got 100 second dates and 70 ideal matches Absolutely that qualifies this experiment as a success and I officially redeemed myself from season one And it is true. You can make an intimate connection with somebody in a very short spend of time So no excuses guys learn your tips go out there and practice them and go meet people because after that the sky is the limit So there you guys have it Those are our first rounds of experiments and so far we're at 80 second dates and five on the experiments We got a lot of crazy a lot of ridiculous a lot of funny But hopefully at the heart of it all a lot of information and education for you guys These tips aren't just for textbooks. They're for the real world You can take them and use them to your advantage Some of these would work really really well in a job interview will work really really well on an on-the-fly meeting And so even though what they're funny, they're fun to do They're also really practical using these techniques or season one techniques You can always go and find a way to connect with somebody else and find some common ground Even if it is taking the ebb and route just smiling and nodding in your head thinking Fucking hate this much That's how crack addiction starts That's literally that's literally the definition of how crack addiction starts All right guys get some rest get you some food and get your shoulders massage because up next we got shit like this If I could I run into my own arms And then like I'll be like on the beach at the same time like in the corner like jacking it to watch myself If you guys want to see more and watch these full episodes because yo There's a little taste of how entertaining these things were go to fulls.se slash shan booty And you guys can download the full screen app if you are an atnt customer You get one year full free 99 an entire year If you're not you get one week trial for free to test out see if you like it And of course to see a lot of me all of season one is currently on there and now half of season two I don't know what other reason you need and we'll see you guys next episode Well, we have a brand new experiment on the app though not on here. Sorry go over there. I'll see you over there Don't


Good evening everyone. So, I will share about myself, learn, journey and how I become a data engineer. So, come here, I'm working for Fintech startup as a data engineer called Atlantz.ai. And I'm also the founder of Coding Girls. So my story is beginning back three years ago. Back in that time I was working for Shibokin firm. So my role is operation executive. So my data is like writing sounds of emails, making phone calls, chasing after different parties, and asking them to send me different documentation. So I was boring about that job and I really hate the tedious and repeat list of it. And the worst is, if one mistake, because we are shipping the oil products, the crude oil, so if one mistake can cost you millions dollars, you have to be very careful. And so that is when I was thinking if there's another possibility I can write a program to help me to do those tedious jobs and helping to make fun of mistakes. So that is when I think about programming. How about I write robots to help me to do those tedious jobs. So back in that time I started to do a lot of googling about programming. And I really learned very hard on it. And eventually I become a data engineer after maybe one year after learning. So my journey is not a smooth sailing. So there's a lot of difficulties when you learn on yourself. So the first thing I think for most of the beginners is you don't know where to start. Because once you google it, there's lots of languages you can choose from. And even if you try to learn one language, there's so many resources out there, you don't know how to pick one. So this is your first burial. Then the second is once you start to follow some online tutorial, you're just most likely it's like Cobbian paste. So sometimes even Cobbian paste you will fail. Even Cobbian paste the same code, it still fail. Maybe it's different environment. Maybe you install different version. But for the beginners, they don't know how to debug. They may eventually give up. So even if you have passed this process, you're debugging on your own and successful. But you don't know why. Why this one works and that one didn't work? So also for some of the beginners, they also, I think, because I'm running calling girls, there's a lot of beginners come to us. So they all fail. The same problem is the isolation. They don't know how to debugging and they don't know how to ask for help. So those are the problems. So my, I have a lot of lessons learned here I want to share. So first one is to find your purpose. So before you take action, you need to think twice. So ask yourself, what is your purpose? Do you want, why you want to know programming? That you want to make a side project or some learning? Or that you want to get an entrepreneur and you want to come some product? Or you really want to go into a career as developer? So once if you decide you want to transition in your career in developers, you still need to do a lot of research. You should know different roles and what are those steps looking from and what they do and what will be the career path. So you have to be very honest about yourself and ask a lot of questions. Go back and forth and go back and forth until you can make a plan.  But don't be too ambitious and too rushed. So you have to prioritize in what you should know. So my suggestion is to choose one language first. So use that one language to understand the fundamental programming. Understand those basic concepts like what is loops or what is function. So you don't need to rush to quite a project immediately. I think the foundation is very important. So also when you write the code, especially when you are doing some online tutorial, be mindful of your code. You should understand what's happening. What here, this is the function or this is if she likes the class or those kind of stuff. So the last suggestion is you have to know algorithm. I know if you check on most of those coding bootcamps in the corrector, this part is missing but I think it's wrong. The algorithm is essential to programming. Once you know the algorithm, you will be able to write a better code and more efficiently program. So even if you want to find a job, if you want to apply for Google, Facebook, those matter, take companies, the algorithm is the part you cannot miss. Here is some resource I recommended. So I learned the basic HTML, CSS, and SQL on Diablo 3 School. The best part of it is that the tutorial, I think is very basic about step by step and the result is immediately you don't need to set up the environment on yourself and it allows you to do a lot of experiments and you can just write your code on it and once you click the wrong you will see the result. The second one is Udemy. The best part of Udemy is each of the course that is designed followed by a project. So that is where you can learn how to make a practical project. And so the Coursera is where I learned the algorithm. So Coursera is very academic. So I think you can find some really, really wonderful course on Coursera, especially those fundamental programs. So that is what I recommend. The Facebook, I didn't follow all the tutorial but many of my friends, they just dig to this one and finish all of the tutorial. Maybe it might take you like six months or even longer. But I think this one is where if you can finish all the course on Facebook Camp, you might have the basic skill to become a web developer. So the Data Camp I would recommend for those who want to be data analytics. So Data Camp they have a lot of programs on R and Python. And I check on the curricula. It's like very trendy and the instructor is really the developer from Python and R. So I think this is the top expert who contributes to the curricula. So of course the last one, Stackover Flow is where we find a problem, we're debugging and looking for Stackover Flow for an answer. So of course we also have our friends, Google, who can answer a lot of questions for you. So after you make a plan, so you need to focus on practice. And you should keep working on. So this is lead code. This is where I practice my algorithm. So I think most people don't do it, but I think for the beginners you still need to know algorithm. And they will provide the problems and solutions. Sometimes I think some complex technical tests come from the lead code. So this also helps you to prepare your technical tests as well. Then the third advice is to join a group and a community. So one of the problems I mentioned when you're self-know is lack of help and lack of feedbacks. So I think today you are already here, which means you already know this. So yes, it's good to find a community. I think the community is very helpful and they are very kind to each other. And if you have problems, just ask the experts from the community. And also listening to their talks is the way you can keep up with those real world problems. So from the online tutorial, there is always a gap between the working skills and the online tutorials results. So this is where you can know what other gaps you are lacking. So after this, you should start to plan to build your online profiles and also show the person on the community as well. So my suggestion is you should build your online profile. Maybe you can create a website or maybe you can do some site project and publish it to the... And also you can contribute to the D-HARPS as well and also take complications. So there are some websites for the programmer one is Hackrank and the other one is called Kaggle. It's more for the data scientist people. So also you can take some hack zones. Most likely the organizer of the hack zone, most likely they have some hiring opportunity as well. So join hack zone, practice your problem solving skills and get to know the people from the companies and you might increase your chance to be hired. So how to prepare for your job interview? Do your research on the company. There is one called Glassboards. There's a lot of people share their interview experiences. So you can learn from the answers and get to know what would be the hiring process, how many interviews and what will be the technical question like. And also for the most tech companies they have their referral program. So don't be shy to ask someone on LinkedIn even they don't know you before to ask them to refer you to the job opportunities. Because once you get the job they get the money so they will be more than happy to help on that. So this is a website on how you can write your developer resumes. To summarize is to highlight those skills they are looking for and showcase about the project you have done. If you don't have the learning experiences your site project will be very helpful. So for the technical interviews in general they just want to test your ability on problem solving. So you just choose one language you are comfortable with. And when you answer this question think about edge case and the color case. And think about the time and space complexity. So and you should know how to write the test. And keep the system be like thinking your mind. So if you think you are not there yet but keep those tips in mind. So trying to improve your knowledge on that. There is also a book called cracking a coding interview. I didn't really have a lot of people to recommend so I just put it there. So my last suggestion is fake it until you make it. So for me I think my journey is like this. Back in two years ago I started to organize coding goals. Back in that time I am not an engineer yet. I just get the idea about what is front end and what is back end. But I didn't deny myself and organize those workshops. I can find the expert to teach. And also I take the responsibility to organize those workshops. So I force myself to learn more. So I think also you can think about sharing your knowledge to the community. And if you think you are just junior you still got something to share. So that is when you know actually you are really you might be good at something. So that's all for me. Thank you everyone.


Since coronavirus disease 2019, COVID-19 became a global pandemic, concerns have arisen regarding the risks of COVID-19 in immunocompromised children and adolescents. Here we aim to evaluate the clinical outcomes and risks of severe COVID-19 in immunocompromised pediatric patients. Previous studies reported that most children and adolescents receiving immunosuppressive medications have clinical presentations and favorable outcomes similar to those of the general pediatric population. Treatments and access to health services should not be interrupted in these populations and continuous monitoring of the potential impact of variant strains on the risk of immunocompromised pediatric patients is warranted. This article was authored by Byung Ok-Kwak and Byung Wookoon.


So, as I said, my name is Andrew Gerand, and I'm from Google in Sydney, and I work on Go, the programming language at Google in Sydney. And today I'm going to talk to you about some part of the Go programming language, not a comprehensive overview, only of a short time, so I can't go really in depth. But just to give you a brief overview of what Go is about, Go is an open source, BSD licensed, and it's a general purpose programming language being developed by a team at Google. There's some of us in Australia and some in the United States, quite a small team. And it's also developed by a team of contributors from the public. There's been over 100 people not from Google who've contributed code, and there's about 10 to 20 regular contributors outside of Google. So, what Go is, is it's a simple language, meaning it's very easy to understand, it's very simple in its specification. It is syntactically lightweight, it feels like a scripting language to use, but it's a compiled language. It compiles to native code on 32 and 64 bit Intel architectures and on processors. It's statically typed, as distinct from Python, Java, script, et cetera. And it is memory managed, so unlike C or C++, you don't need to actually manage your memory, like Java or the dynamic languages, all that's handled for you. And it's a highly concurrent language. I'm not going to talk about its concurrency features today, but one of the big selling points of Go is that it has some really neat primitives for launching lightweight threads and communicating between those threads. And it's also one of its design goals is to be very, very fast. So it's very fast in its execution and particularly very fast in its compilation. And as of November, the start of November last year, it's one year old. So just to talk a little bit about the design goals of Go. So the key goal of Go was for simplicity. If you look at any of the sort of major languages, the mainstream languages that exist today, there are countless numbers of corner cases. And it's very difficult to understand exactly how a particular feature set works. But we thought that every feature of Go should be easy to understand in and of itself. And to go hand in hand with that is orthogonality. So each of Go's features need to interact with each other in predictable and consistent ways so that you know what your code is going to do when you see it written, there's no sort of guesswork. Well, it's very difficult to construct those kind of trick programs where you're not sure what it will do. And thirdly, Go is designed to be highly readable on that note. So when you look at a piece of Go code, you should really understand exactly what it's going to do. You don't need a lot of context from the surrounding program to comprehend a particular piece of code. And finally, we wanted it to be usable, which is really a combination of all of the above points. Like many languages force you to make a lot of decisions about how you're going to structure your programs before you begin. You have to think a lot about typing and design considerations. Go sort of gives you the opportunity to write out some data structures, write some code, some actual code that does something before you start massaging it into an actual structured program. So in this talk, in the brief time that I have, I'm going to talk about Go's type system and the package system, which organizes all of Go's code. And I'm going to do it in reference to Go's tar file reader and write a package from Go's standard library. So this is the Go documentation and this is the package tar. So it's a simple package that will read and write tar files. Does anybody not know what a tar file is? We're at Linux Comp, so I presume you will do. So first off, Go's type system. I might as well start with what Go doesn't have, rather than talking about what it does have. Go is an object-oriented programming language, but it doesn't have the familiar notion of classes and all the baggage that comes with those. So it doesn't have abstract classes, static methods or variables, the concept of protected or subtype polymorphism as like a design philosophy. It doesn't have implements in terms of explicitly implementing interfaces. Doesn't have constructors on objects, and it doesn't have a concept of this. So what does it have? Well, Go's type system is based around several built-in types. So we have the numeric types, integers and floats, complex numbers of various precisions, bullions, strings, struct types, which are just concatenations of various other types. Pointers, arrays and slices, which are fairly self-explanatory, and maps, which is a built-in hash map type. And finally we have channels, which is one of our concurrency primitives for communicating between threads. And functions and interfaces are also types, which I'll go into in a little bit. So when you make a type definition, which is the fundamental way of specifying a user-defined type, you just give a name to any of these built-in types. So this first type definition here is the type year, which is an integer. And so if I want to use a year, I have a variable that accepts a year, it's just accepting an integer behind the scenes.  It has two struct elements, a name, which is a string, and a birth year, which is a year. And so in memory, if I have a person, that is literally just a string and a year, which is an integer, next to each other laid out. And thirdly, I have this person list type, which is a slice of pointers to person. So we'll see how this becomes useful in a minute. So here's a type definition from the tar package. This is a tar file header record. So it's just a struct containing the name of a file and all of its associated metadata. So a tar file is basically just a concatenation of header records and file data. And this header struct is used by the tar package to represent that part of a tar file. So I described how types are implemented. You can declare a method on any named type. So these are the types that I've defined before. Here's a method, star date, which is a method on the type year. This is just a normal function declaration, but this here is the receiver, the methods receiver. So y is a type year, and then my method name is star date and it returns an integer. And all it does is multiply the year y by 13, which is a rough approximation. There's no real connection between our years and star dates, unfortunately. I realized after I wrote this example. So, and this second example is a method age on the person p. And what this does is takes the current time in nanoseconds, reduces it to seconds, and then divides it by the number of seconds in a year to give us the current year and then returns the difference between the current year and p dot birth year. So what I'm doing is the receiver person is referred to as p, which is something that I've specified within the method, and I'm returning that value. And the third example is just a method that returns, that's a method on person list, my list of person, and it just returns the oldest person in that list of people. So it just iterates through, I'm using a range statement, iterates through L, finding the oldest person in the list and then finally returning it. So to look at a real world example of a method, in the tar package, there's a reader type which reads from tar files, and it's a struct type, and it has a method next so that when you're reading through the file, you can call the next method to skip over whatever file you're reading and go to the end. So yeah, so this leads me to interface types. Goes interface types define behaviors and they do this by defining a method list. So when you have an interface type definition, it defines a set of methods and any type which implements those methods satisfies that interface and can be used anywhere that that interface is expected. So in this example, I have absa, which is an interface type which contains one function definition, abs, which returns a 64-bit float value. And so here I'll define a type point which contains two 64-bit floats, x and y, and then the method abs on point will return the hypotenuse of a right angle triangle made by x and y, the absolute scalar length of the vector xy. And then if I'm in use in this example function main, for example, I can have a variable a, which is a type absa, and I can store the value, a point value in there because point satisfies the absa interface. And so then when I print a dot abs, it will indirect through to the underlying point and call points abs method. And so to give you a more concrete example of how interfaces work and go, the IO package, which is part of the standard library, defines reader and writer interface types. And many types, both in the standard library and out of the standard library, implement these reader and writer interfaces. And so they can be used interchangeably wherever reader and writers are expected. So the reader type definition is just this, it defines one method, read, which takes a slice of bytes and then returns the number of bytes read and an error value. And then there's a broad array of types that implement reader and this is just some of them. So in the standard library, there's like a buffer of bytes in memory. So you can use that as a reader or a GZB compressor or an HTTP connection or a TCP connection files, our tar file reader, for example, and like a WebSocker connection as well. And so all these things can kind of be interchanged. So in the archive tar package, the new reader function, which is what creates a new tar file reader, it takes an IO reader value. So if you had a file, which was a tar file, you would pass it that file and it would use it as a reader and read the data from it. And similarly, the reader itself, because it implements this read method, it in turn is a reader as well. So just a bit about how code is organized in Go.  So at the top, you have the largest single element is a package. And within that, you have variable constant function type and method declarations. And then with it, and so that's your global package scope. And then within a function, you have a local scope in which you can define variables, constants, functions and types. And the definitions of those at the global level and at the functional level are the same and the rules that they bind to are exactly the same. So it's very predictable and comprehensible to see how these various things work no matter which scope you're using them in. And there are only two compared to the much more complex scoping rules that you have in languages like JavaScript, Python or Java or indeed C++.  So it's kind of like a Python package. But it's sort of a more of a looser kind of collection of things. Packages can consist of multiple files, but they all share the same namespace. So I'll give you an example then in a second. But it means that you can effectively organize blocks of code without having to make explicit decisions as to where you think things should be. Because within a package, the particular file that a function is in doesn't actually dictate how you address that function. As far as things being private and public, Go has one simple rule as to whether things are available inside or outside a package. And that is if the name begins with an uppercase letter, then it's considered public. Otherwise it's inaccessible. So you can immediately see whether something is an exported method or type or variable or whatever at a glance. And the only other errata is really that circular dependencies have been, so you can only import in a non-circular graph. And the top level package of any Go program is always main. So to give you an idea of how you might actually lay out a package, the tar package consists of three files, writer.go, reader.go and common.go. And all of these files share the same namespace internally. But writer.go contains all the stuff relating to writing tar files like the writer type and its associated method definitions. The new writer function for creating a new writer, all of the write-related error values. So if a writer encounters an error, you can compare it against these publicly shared error values to understand what's going on. And also all of its unexported implementation is also in that writer.go. Similarly, this is the same story for reader.go. You have all of its public implementation stored in there and also all of the implementation details that are unexported stored in there. And common.go has the header type that we saw earlier, which is used by both the reader and writer types. And it's exported constants and also some unexported helper functions. So it's kind of like a loose amalgamation of all the tar writing stuff in those three files. And to give an example of one of the unexported like helper types that is used by both the reader and the writer, there's this ignore writer type, which is because it starts with a lowercase i, it's actually only visible to the tar package itself. And all it does is it implements the IO writer interface by defining this write method and it just acts as if it's written data somewhere and then throws it away. And the way this is used is there's a method on reader where when you're reading through a tar file and then somebody says, and then you get partway through or you wanna skip to the next file, you basically wanna skip over all that data and throw it away. So what we do is we do it, there's a reader on the, we perform a copy basically from the reader source into this kind of null ignore writer. And that just skips over or reads all of those bytes into DevNull effectively. But these kind of like help types or wrapper types are very common in Go to just build something and then it's effectively like a throwaway thing. I've been told I'm running for a long time so I have to wind up. But just to the key points of what I'm getting at in this talk is that so the orthogonality, as I mentioned at the start, the concepts of exported or unexported are completely orthogonal to like variables, constants, functions and types. And it's natural and easy to like expose or hide or rearrange various parts of your Go program, move them between packages and reorganize things as you're going along, which is kind of unusual for a statically typed language but goes kind of loose enough that it lets you do that. But the real benefit of that is is that you build everything, both your public stuff and your private stuff in the same state of mind, so that the part where you're actually coding and making code that works is distinct from the part where you've fashioned something into an exported interface. And so going from the version that just works in the very beginning is to the production quality version that's worth sharing. It's usually not a big deal to get to that point. It doesn't usually require major rewrites. And yeah, so there are generally fewer barriers to refactoring and so just like in summation, Go has become for me. I've been working on the project for a year since it was released. I didn't work on it before the release and it's quickly become like my language of choice for pretty much everything for some of the reasons that I've outlined here. In giving the talk, I kind of realized that I probably haven't communicated as well as I could have my enthusiasm for how nice this is, but it really is and I encourage you to give it a try. We've got a ridiculous amount of documentation up on this website, so check it out. Right, so sorry for keeping everybody from lunch. But first let's thank Andrew for the talk. And now if there are some people in the audience who'd like to ask some questions, please raise your hand or run a mic to you. Okay, you then, you. I just want to ask what the state of the library is like, whether or not I can database access, blah, blah, blah. All those other things you depend on when you do something. So the standard library itself is very mature and there's also a really broad range of third party libraries written by people in the community that do a lot of what you might need to do. I mean, it depends specifically what you want to do, but in terms of database connectors, all of the major ones are supported really, like MySQL, Postgres, Redis, CouchDB, all those kind of, all the open source ones tend to have connectors, which is nice. Other than Google, are there any other companies that use Go extensively? Instinctively, internally. Externally, extensively. Well, I mean, as far as extensively, I don't know, but I know that at Atlassian, they're using Go for some stuff. We're definitely using it internally in some production applications, but it's still like very early days for programming language, like Python's almost 15 years old now, I think. Closer to 20. Well, yeah, closer to 20, but it's still only just seeing adoption in the industry. So, yeah. Okay, so we'll take one last question from up here. It's a really horrible one. Issue nine in the bug tracker is related to the name collision of Go, your Go, and everyone else's Go. What's everyone else's Go? Go away. Well, there's only one other Go that I'm aware of, and that Go didn't even have a Wikipedia page until a week after our Go was released. And I've never found a program written in that language. So, I'm not aware. And the reason why we closed that issue is because we said that we haven't actually noticed any kind of confusion between the two languages. Nobody posts on our discussion forums about that Go and presumably vice versa, so I don't really see an issue with it. We all have a slash though. Right. Yeah, no, it's just, I don't know, it's... Well, Rob Pike, who's the team lead on Go, has had, as invented, three other languages before, all of which were, have had subsequent languages called the same thing on him. So, maybe it's like a reverse karma thing or something, I don't know. Righto. So, everybody please thank Andrew for his talk. Thanks for coming. So, we're resuming here at 1.30 with John Cruz talking about Avoiding Development and Honor Culture. Love to see you back here. So, yeah, see you then.