This blog is written to shed light on how a python coding bootcamp always goes down. Being an avid developer myself, I must say this was one of the many experiences I have come to love. The bootcamp was a two-week study session, where we learnt a whole lot of stuff regarding Python and many more development-related ideas. For week one, it was an intensive problem-driven session. A lot of coding python program and trying to solve them in as much as we could. So flashback to where it all began. You may want to ask why I did sign myself up for a coding bootcamp ,which was partially online and a part of it on-site. I wanted to expose myself to challenging (software development environment)environment something that could challenge my mindset ,and to me this was the right opportunity that presented itself.
The first day of bootcamp was friendly and chill. So for context, our week one of bootcamp was entirely online. We had assignment to handle and then hand them to the bootcamp facilitator. I believe you can find some of them on my git hub repository. The sessions majorly started at 8 am in the early morning and ended at 4pm. Through that span of 8 hours, we had group work to tackle, personal assignments to handle and also our projects to take a peek into. On the side of projects, we picked our project ideas on the second day of bootcamp. There was a whole list of projects we could select from, and that required each one of us to pick a project from on there.
The week two of bootcamp was an on-site session where we availed ourselves at the office at 8 am in the morning, as well. The session stretched through midday till 4pm where we would leave the offices and back to our homes. Of the two week, the on-site one was quite intensive and required diligence and dedication. Waking up on time, taking a bus to town and eventually to the office. For week two, w tackled Test-Driven Development and had a go-ahead to start working on our solo-projects. My project involved a number-guessing game and In a nut shell I am going to give you a little description of what I did, I integrated GitHub actions to automate and help with testing and create a workflow(CI/CD) in conjunction with pytest this helped me produce a test coverage of 96% ,also added badges for issues(helped me to track unsolved issues)and forks(helped me to track number of forks done).On the project I also used pywhatkit library to call WhatsApp messaging function into the code that will be receiving the score as a message.
That’s pretty much it for our two-week session. I got the chance to pick on as many new ideas as possible and managed to learn many things as well. Will I do this again next time? Definitely yes.