Learning Experience with Crio.do — Winter of Doing

Hey everyone, I am back with yet another blog. But this time, there is something very special about it.

So, few days ago I was scrolling through LinkedIn feed where I found this amazing opportunity called Crio Winter of Doing or CWoD. I was very excited and went on searching about this and landed on Crio’s official website where I was shocked to see the amazing companies with which I can get chance to work with if I get selected. Since, I was newbie to this, but this program’s structure is built in such a way that even a beginner can get his hands dirty by working on some amazing projects by companies like Cred, Groww, Jumbotail and others as well. Thus, I couldn’t stop myself from applying and hurrray, few days later, I received the selection mail for the internship, or Externship as they call it. So, in this blog I am going to share my learning experience with Crio during the Stage 1 of CWoD.

This is how they brief about Winter of Doing :

Crio Winter of Doing is a one of a kind program focused onbringing together budding engineering talent to work on challenging projects for the most exciting startups in the country.

So, the very first day started with an orientation where they explained about the structure of the program and how anyone can get started easily and comfortably with it. The pogram is basically divided into three stages and each stage some students will be selected and they move to the next stage of the program.

• Stage 1 : In this stage, everyone who were selected in the program could participate and the stage was for one week. In this one week, topics such as HTTP, REST API, Linux and Git were to be covered. In addition to that, some cloud fundamentals and AWS was also to be covered and as a bonus, we were to be introduced to Full-Stack Development where we would built a beautiful portfolio for ourselves. The students who successfully complete the Stage 1 were graduated and considered to participate in the Stage 2 of the program.
• Stage 2 : This stage is for the Stage 1 graduates and time duration for this one is for around 3 weeks. In this stage, we will be shared with materials regarding coding and mini-projects and we’ll be assessed on that basis itself. The Stage 2 graduates will be eligible for the final Stage 3.
• Stage 3 : This one and half month stage is for the Stage 2 graduates. In this stage and the most interesting one, we will be allocated with projects from the above mentioned companies and we will be working in a team of 2 under the guidance of industry mentors.

Starting with the HTTP module, what I did was analyzing a request, response, how to work on terminal, curl command, using Postman to perform HTTP request, and also posted LinkedIn using a terminal. After learning the basics of HTTP, I moved on to the next byte of REST and came to know what rest APIs are, how we can build one, and then build a rest weather API to get the weather of any pincode.

Next comes the LINUX byte where I learned the power of Linux, its commands. Do you know even the android phones run on Linux! That’s the power of it. Honestly speaking, if you are a developer, you simply cannot avoid Linux and it’s terminal whether you are working on your local machine or your cloud instance.

After we were done with these, AWS Byte was waiting for us. I learned how we can deploy our server on AWS and deployed one android app(Qeats, a food ordering app) on AWS using EC2 server, by selecting a proper configuration. I was even able to test it by downloading QEats mobile app and then analyzing the logs.

The last byte, we learned about was GIT, the most common version-control system. We learnt how to manage our codebase using Git, how to pull and push code using Gitlab.

After these all bytes, an additional (bonus) task was there called QProfile. QProfile is basically a portfolio where you can showcase your projects that you have built. Before working on QProfile, we were first introduced to Frontend technologies like HTML, CSS and JavaScript. We even solved few Javascript problems as well. Then we moved on to create our very own QProfile. Almost the entire code was provided by Crio, we had to make enough changes to work it for us. While building this project, we practised our Git byte, how we cloned a repository, then how we pulled code from another repository to our repository, then pushing it back with our changes in it. We made the Backend using Node and Express. Then we were introduced to two platforms, Netlify — where we had to deploy our frontend code and Heroku — where we had to deploy our backend code. Then these both communicate with each other so that our QProfile works properly. You can find mine here.

One very important thing worth mentioning is Curious Cats. These were some important and tricky questions that made us scratch our heads while learning each Byte. We experimented ourselves and tried to find their answers.

So, the Stage 1 is almost over and I must say, this one week I have learnt a lot starting from simple HTTP to topics like Cloud and AWS. Within this week, different sessions were held. In addition to sessions regarding the topics from amazing mentors, there were some more exciting sessions with industry experts like Binny Bansal, Co-Founder of xto10x and Flipkart, Vivek Ravisankar, Co-Founder of HackerRank and Karan MV, Developer Relations, GitHub . Apart from the amazing mentors like Sridher Jayachandran and Kiran Suresh, the slack community is quite enthusaistic and helpful.

Apart from learning activities, there were some fun activites as well such as Solve the Mystery : Fraud or Not? and Bring the Data Scientist in you. And before I end this blog I want to share one fun fact : All the attendees were so active and enthusiastic that we crashed the Gitpod server one day and then Crio server another day 🤣🤣.

At last, I am very happy that I was able to get selected in the program and hope to graduate successfully for the Stage 2 as well. Thank you Crio.do for this amazing opportunity and the externship.

The blog was originally published on my own Blog Site : Technik . Read the blog here.