 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. So once you decide which roles you are taking, you just decide to, then you should decide where you to begin and then 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.