 Okay, thanks for the introduction Elisha, hi everyone, good evening. We are team tech ladies, I am Huemin, I'm an analyst. This is Shalene who is a pet groomer and this is Maggie who does project management. So for our presentation tonight we will be breaking down our time into three sections. We're first going to be touching on very briefly about the organisation that is Tech Ladies. We'll then talk a little bit more about the application and then finally we'll share a little bit with you about bootcamp journey. Okay, so Elisha has already spoken at length about Tech Ladies. So for the purposes of our presentation we'll be focusing mainly on the bootcamp itself. So since Tech Ladies inception in 2016, Tech Ladies have already organised three bootcamps to date. So that means that as Elisha has spoken before, they have accepted scene 264 bootcamp submissions. Out of these 264 they have taught 29 bootcamp participants and finally out of these 29 they have successfully helped eight of these ladies land technical internships or jobs. However, have you ever wondered like what goes on behind the scenes for Elisha and the coaches when it comes to the selection process? So unfortunately Tech Ladies have been ranking and sorting bootcamp applications manually with Google Forms and Sheets which had been incredibly time consuming. What they need now is an application to integrate this entire process. Okay, so this is a snapshot of what the application looks like which was way too cluttered and way too many words for anyone to read. So let us now take you through very briefly how a typical bootcamp application was processed prior to this app that we've built. So as an applicant you would fill in your application into Google Forms. All the applications would then be consolidated into Google Sheets and tidied up by Elisha. She would then nag the coaches via Slack to get in there and assess all these applicants. The coaches upon being notified would then go into the Google Sheets, make their assessments and get back to Elisha with the results after which Elisha would look through for a final selection and then communicate either a rejection or an acceptance offer to these applicants. Now as you can see the old evaluation process is time consuming, it is inefficient, it's repetitive, it's not scalable, not to mention a little bit naggy. Now what this means is that with the application that we've built not only will this evaluation process, inefficiencies be eliminated, it will now become an integrated platform that not only is more streamlined, more efficient, more scalable. We have built in additional components to flag incomplete applications, to sort applications to team, applicants to teams and finally we will also have a system for ranking. Now this application will bring about time savings for both Elisha and the coaches, particularly for Elisha where she previously had to spend upwards of 15 hours to manually sort, reconcile all these applications. Going forward she will be spending less than 50% of that time to do the same. Good for Elisha. So that is equivalent to more than 50% time savings with this application built. I guess I'll now pass on the mic to Shaleen who will share a little bit more about the application that we have built. Thank you. Thank you, Hoi Min. Just a check. Can everybody hear me from the back? Back row? Okay good. Okay so hi my name is Shaleen. I'll take you through the application itself. Sorry we're having a bit of problems the quicker as well. So I'll just go on with the application. So this is our design process for the application. The three components are the entity relationship diagram, the wire framing and the toolbox. So I'll go into more detail. Nope, that's a work. Nope, it's okay. Sorry, sorry. Okay, so to start with this is an entity relationship diagram. Can I see a show of hands? Who has seen an ERD before for short? Okay great. I have like one-third of the room. That's good. So basically this is a visual representation of the entities and their data elements and how they relate to each other in the app. Don't worry if I just spoke French. Just to introduce. So the first two boxes you see in blue, namely the applicant and the boot camp, these two are entities that are related to each other. So for every application process we have an applicant applying into a boot camp. So in this case to demonstrate a relationship an applicant will always belong to a boot camp and a boot camp will have many applicants. So for this application we identified eight entities which forms the back end ERD structure of our app. Okay, so that's the back end. Moving on to the front end, we have wireframes. So wireframes are a set of images that represents the user interface or the front end of how the app looks. So we hired UX designer, we worked with the UX designer Esther, I'm sure she's here. Yes, who came up with this three cat icons, especially for Elijah. She's the main user of the app as an admin. So yes. So what we wanted for the app was a very clean and intuitive interface. So even the color coding of the buttons were well thought of. So these buttons actually represents like certain statuses of the boot camp itself. So now on to our toolbox. These are the tools that we use to build the application. On the left we have Slack and Trello. Slack and Trello we mainly use for our team, communication within our team and coaches. And on the right are the technological stacks that we use. So the app was built mainly on Ruby or Rails for the back end framework. And for collaboration we use GitHub. So one of the best practices that our coaches taught us was like the submitting of pull request for our code to be reviewed by them. So we cannot just, Sukasuka just put any code up there, right? So we had to submit our request and then after that they will look at our code and they will review it. And then we have on top of that we have integration tests. So only when the tests and the coaches approval are met, are we allowed to merge it into this master code base. So this ensures that we actually have less errors, less room for errors in our application and introduce less bugs. Okay, so now on to the highlight of the presentation, which is our product demo. So for the purpose of demo we'll be taking you through the entire process, the application process to the bootcamp. So from the application form submission to the coach review and on to the final selection. Okay, so the users of this app we have three different stakeholders. So just for the purpose of demonstration, Hui Min will play the role of an applicant. She will be applying as herself. Maggie will play the role of an admin. And myself I'll be representing the coaches. So I think without further ado, let's start the application process. Right, so as you can see most of the public pages over here we have kept as per the existing Tech Ladies page except for this additional button here that says apply. So if you click onto that you'll be able to see all the bootcamps that will be open for application. So once you click into that as an applicant, I will be able to fill in all my details right here. Right, and then at the end right after I answer all the questions to the questions I'll be able to choose my team. So suppose I want to pick a where Singapore for now. So when I create my application, I will automatically get an email that puts in a link for me to access my application. So suppose for this time round I want to pick SPCA as the team that I want to apply to. So once I update my application, that will be the end of this submission. So Maggie right now as an admin will take you through how my application is processed at the back end. Okay, sorry. Okay, here as an admin, step one, lock into the admin console. So here we go. Okay, over here this is the admin console. I'm able to create, add a new bootcamp, create new questions and even create coach criterias. So back to the focus on the selection of the... back to the focus on the selection of the participant. So we will click on view first card applicants. Here is the list of applicants which has submitted for the... after the list of applicants that have submitted for the final submission, after completing the technical task list, click on Huiming. Okay, as Huiming as the applicants, we click on it, we will be able to see the... answers that she has replied for the applications. So should I... there's only two options whether to coach to review or to reject. So should I reject Huiming or should I send to coach to review? Okay. So we have accept Huiming for coach to review. Okay, so over here. Okay, after the coach to review, you will see the whole list of applicants that is to send to the coach. So we will click on send to coach. It will create a magic link, a special URL for the coaches to view. Okay, so hand over to Charlene as the coach. Okay, yeah. So as a coach, I will receive an email with a link and then when I click on it, I will end up on this page. So this is the assessment index page. Over here I should see the list of applicants that has already been chopped the first time by Elijah. So these applicants are the ones that are applying to my team. So I can see that Huiming's name has gone through the system and appeared here. And when I click on edit, the questions and answers that she has submitted during the application process, I can see them here. And as a coach, I have to click on the GitHub link because there is this component which is the technical task that I have to access. So clicking on this will lead us to a GitHub page. So anyway, I'm not going to click on that. Sorry. So we can move on to the scoring part. On the right side, you can see the criteria that have been set by the admin, which is Elijah and the coaches. So these criteria for now, they are just criteria 1, 2 and 3. But basically, there are two different kinds of criteria. So the first criteria is a yes and no. It's a Boolean criteria. And the second criteria is a rating from 1 to 10. So let us go ahead and fill in this for Huiming. So the first question is a yes and no question. Usually there will be questions like, so is this applicant female or identify as a female? So I guess mostly you will put yes, right? Okay. So the second criteria will be something like rate the participants' technical skills from 1 to 10. In this case, Huiming's technical skills quite good. So I'll put 9. And then for the rest, I'll just put a random and I'll probably rank her at 2. And for coaches' comments, they'll probably put something like, oh, you know, good technical skills. And then they will update their assessment. So when I go back to the assessments page, I can see that Huiming's rank has been updated as 2. You can see. Okay. And the comment is there for show as well. So in order to fill in and submit these coaches' ranking as a whole, I need to fill in all the rankings. Otherwise, it will throw me an error. Okay. So I go on to fill in the other rankings. And then I click update ranks. And then as a coach, I'll click on submit coaches' ranking. So once I click on this button, as a coach, I'm no longer able to access any editing of assessments. And this result will be sent to Elijah for the final cut. Okay. Okay. As an admin, I will back to the admin console itself over here. So what I should do right now is after the coach review, I click on the View Final Cut Applicants where it will list down all the applicants that has been selected. It's sorted according to the ranking. So as you can see, Huiming is among the top few of the applicants that is of this BookCamp selection. So just click on Select. So right now, as you can see, she is into the BookCamp. And over here, Elijah will be able to update the payment status of the applicants. That's the end of the whole selection process of the BookCamp. So over here with this, with the application is streamlined, the selection of the whole process of the application. And finally, our baby is out. To give birth to this baby, we face a lot of challenges. Three of us actually come from different backgrounds. We have a steep learning curve. And for coding, we have to understand syntax methods to use and more. Thanks to the coaches for the extra hours of coaching and sharing of extra results, things get tough when it comes to communication, especially for introverts like me. It's slow to warm up and plus our busy working schedule. We have to work off site to get different parts integrated together. Next come our biggest challenge, which is the box fix. We have become a box killer, hunting down the box so that the application can run smoothly. Although it is challenging for us, but it's rewarding. Three of us, our friendship has grown and most importantly, new skillsets has added. Lastly, we like to share our individual BookCamp journey. Let me start first. I have been working alone on interactive database software and most of the time I'm just getting stakeholders to stick down what they need in the application and start working on it. My biggest takeaway during the BookCamp is I get to learn more collaboration tools and experience working in a development team. I used to believe that I just need to communicate with the computer, not with humans. A lot of communication and understanding in the team and between stakeholders is a need. Thanks to the BookCamp, I can apply what I learned and understand what is happening behind the development scenes in my current new job. Pass on to Charlene. Thank you Maggie. Hi again guys. Sorry. My background, I actually come from a sports science background but I've tried different industries and my most recent industry was in the pet industry. My key takeaway for the BookCamp is my understanding of what is good code. I guess there's been talk in the industry saying that this guy can solve this problem in a one-liner. So that shorter code means better code. So that's a debatable question. So our coaches actually made us come up with the definition of what good code is and because I think as my teammate, Maggie, has said development and programming as a whole is a very collaborative activity. So we are not really just coding for ourselves. We're not just coding to look at our own code but we're actually coding in a team. So it's very important that other people understand our code as well. So to me, I think what good code is is that number one, it should be readable or you know, have emphasis on readability at least. Okay, so my misconceptions of programming and the industry as a whole is that you have to be good at math to start coding. So this actually deterred me from beginning programming at a start for quite long because my max is really, really bad, really bad. But then after I started programming I realised that the key skill to learn or to transfer over is not the max per se but it's the ability to break down very big problems into smaller chunks and then to apply a little bit of logic to solve that small problem. So it just revolves around a bit of common sense and logic, at least for web development at least. Okay, so I'll move on to the results and what's next. Having graduated from the Tech Ladies' Book Camp and also full-time book camp at Alpha Camp recently, I think the key learning point also is it actually helped me to build my confidence in programming. Compared from now to the last six months, I think I've improved a bit and also these book camps taught me how to learn. Programming is like a different skill altogether right? To be able to learn that new skill and apply how to learn that new skill I think I can use the same model and apply it to other kinds of programming concepts and programming languages which I think is very valuable for me on the whole. And what's next for me, I think with these new skills, I hope to go into the tech industry by looking for junior software development role. I'm also open to internships and most importantly, I think that learning never stops. So for this book camp, we were taught Ruby and Ruby on Rails. The next area that I'll be going into is JavaScript namely React and Node.js. And I'm very excited to see how this actually differs from Ruby and Ruby on Rails. So yeah, so on to Huimin to further conclusion. Hi, Huimin again. So I'm a part-time analyst and a full-time coffee enthusiast. Just kidding. For me, my take away from this book camp I think is to step away from the code. Sometimes you really need to do that because oftentimes I find that when I'm stuck in a rut, you know, either debugging or working against a timeline my time tends to be counterproductive because I get overwhelmed by all the things that I have to do and solve. So oftentimes when I step away from the code and take the time to breathe and refocus, I find that I come back a little bit more like I can focus a bit more and then my time becomes efficient because I can think through problems more logically. So my advice is to step away from the code. My misconception prior to entering this book camp was that I used to think programmers are intimidating because they're smart. They're focused. They don't want to talk to you. But that's not the case at all. I find that throughout this experience at least in the Ruby community people are extremely incredibly supportive. They're always so willing to teach, to mentor and to coach and to these people I and we are all very grateful for. So results for me after this book camp I have picked up some side projects mainly dealing with web design. I'm also beginning to help out with a friend, semi-shadowing him to build an enterprise system for a mid-sized company. And so what's next for me? I want to build more applications. I'm keen to pick up side projects. So if any of you have any ideas to share looking at you guys come talk to me and come talk to us at the end of this presentation. So that's all we have for you. Thank you for your time. I'm kind of small, I'm here. So we're going to take the next few minutes for Q&A. Does anyone have any questions for these ladies? They think that you're curious about what's on your collection. So how long did that take you guys? How long did what take? Doing all the app like it. How long did it take you to do that? Okay, so our book camp was formally three months. In July. We want to say we are 95% there. The only thing that we have to do right now is to push it into Heroku, I think. But yeah, it takes about three plus one, two months, I would say. So I'm going to use it for the next book camp. So the next book camp, you'll see this in what I will see this in action for the next book camp. Any other questions? Should I assign someone to ask questions? Anyone? Okay, if not, these ladies will definitely be staying through the event and feel free to talk to them, ask any questions. The business people looking for tech co-founder, you know, who to find. And yeah, thank you very much.