 Hi, I'm Casey and we are part of engineers.sg and Sharon is actually not here today, so we're just going to tag team it, okay? So a little bit about engineers.sg, so they're the first only organization that actually had a platform. What they do is they go to all the different meetups from developers and other engineers and they record the meetups because sometimes other developers just have to go home and they can't always go out to all the meetups and there's quite a lot in Singapore so they do an amazing job of going out and recording so that people can view all the meetups online. And our team was really awesome because we had the Baldy Buddies, so our two coaches or mentors are Michael and Ted, so Michael's right there and he's doing there. He's got that cool video going on already. Unfortunately Ted could not be here as well. He's in Sweden. Yeah, so he's in Sweden. He sends great pictures into the Slack channel and makes us all feel jealous. Like I said, I'm Casey and Sharon is not here and Xin Chen is this lovely lady right here. So they did have a couple of actually a handful of problems with the existing platform. So users were unable to get notified when any new videos came up and they tended to upload them quite often. They had no idea to know what was coming up. There are a lot of different events that go on throughout the country every week and there was no way for them to keep track of all the events that engineers.sg was going to be at. Users were also unable to search videos by category. There was no social interaction on each video and the loading of the site was pretty slow and if you're an engineer, you want things to move really quickly. So here are some of the tools that we used. So Ruby and then Ruby on Rails, Postgres, Trello was to keep track of the tasks. Slack was used for our communications and we still use that. And then GitHub was also used. It was our version control system. So we'll talk about the first thing that we tried to fix which was that the users were unable to get notified of the videos. So one of the solutions was to actually integrate a newsletter sign up using a MailChimp API. And if you don't know what an API is, it's kind of like if you are trying to talk to a different system. So that doesn't happen automatically. You actually have to physically code it in there and make sure that two different technologies are talking to each other. And that's what we did. Actually Shintian was part of the, what you see right here is actually what she worked on. So in Rails, there are three different parts to the architecture for the technology. So you have the model. I guess the best way for me to explain what the model is is if your mom tells you to do something. That's how I explain the model. Then there's also the controller. So the controller part that you have to code is actually you telling a different technology or a different database what to do. So it's like your mom, you know, you tell your mom or your mom tells you what to do in the model. And the controller, you actually go out and do it. And then the view is actually when you go out and you tell everybody that you did this awesome thing that your mom tells you to do. So that's how I explain the view, which is what Shintian did here in creating the newsletter sign up. So walking through it, you would actually type in your name and your email and hit that submit button. So once the submit button goes in, oh, thank you, thank you. So once the submit button goes in, it actually goes to MailChimp and tells them, hey, we have this new person into our system. But it also tells our database that that person is in the system. Whereas if you just did an embed, which many people do on websites, it's really just going into MailChimp's database. It's not really talking to your system or your database. The other problem that we needed to solve was that users didn't have any idea of the events coming up. There was like a really small little link at the bottom. Is that right? Correct. But it really wasn't visible and people didn't really click on it. So we built an events calendar using an API from webuild.sg. And so what we did was pulled all the information that was already readily available on one of the sites and just kind of like, it's kind of like cheating. I'm pulling it in into our site. We also put in a Google Maps and that was a lot of fun. I actually went down to Hacker Space with Michael and that was really fun. And we also made it so that people could actually see how many people were already going because people always want to go. They don't want to be the first person there. They want to know that other people are going. So we built this events calendar. Do you want to do this? Yeah. Okay. So I will move. I will pass this off to Shen Tian. Okay. So the third problems that are faced by engine.sg is users unable to search videos by category. So what we did is actually we add in videos tagging system for admin. So this is basically the admin page of engine.sg. So you can see at the bottom of the page, we add in a place for us to key in the tags. So this is basically the tag list. So after key in, after we save, it will appear just below the videos. So this is the videos page. You will see there's a few tags appearing on beside of the page. So when you click on the tags, we link it over to all the videos with the same tags. So this is basically what we did with the video tagging. So the fourth one is there is no social interaction of each video. So which I actually add in Facebook comments column. So this one is if let's say you are not logged in in Facebook during the time being when you want to comment, it will prompt you to actually log in. So the last issue is actually with the loading of the website is slightly slow. So what we did is actually we did a fragment caching. So for those who don't know why it's cached, it's actually for example, today you need to go for mathematics exam. So you know that you have to study for example algorithms. So imagine you have a very thick textbook. So every time you want to go to that particular chapter, you have to flip through all the things and go to that particular chapter which is very slow and time consuming. So what you will do alternatively is you will put a bookmark. So when you need the page, you can just flip over to that page. So this is what basically a cache is. For information that we need to load oftenly, we will put in a primary storage cache. So every time we retrieve it, we don't have to go back to the main database and retrieve it, which will improve the loading of the web page. So this is basically what we have did for the past eight weeks. So Michael and the volunteers really put in a lot of effort in engineer.sg. So if let's say you feel like contributing to this project, you can just follow the repository from this link. Yeah, that's all. Thank you.