A brief introduction
My journey through the Makers pre-course was an exciting opportunity to explore the world of coding without any prior knowledge or expectations. Even though I had no experience, I was still naive enough to think I'd be making a whopping £50,000 within three months – oh, how wrong I was! My first few months of coding were spent independently studying various tutorials, switching between languages like JavaScript and Python as if I was flipping a switch. As you can expect, my progress wasn't the most remarkable.
Realising I needed to take a more structured approach, I began researching all the available options - online courses, degrees in computer science, and boot camps. I went into full Sherlock Holmes mode, leaving no stone unturned in my search for the right fit. Degrees didn't seem to be as valued in this field as knowledge and experience, so I decided against investing in one. The online courses weren't efficient enough for me, so I decided to go with a boot camp. I took the time to do my due diligence, perusing reviews and assessing the course materials, all in an effort to ensure I was getting the most out of my investment. Having narrowed my selection to the two most comprehensive boot camps, I chose Makers despite my friend's glowing reviews of Le Wagon. I filled out the application, paid the fee (ouch!), and fully embraced the risk of making this huge investment.
Good communication, but was it just for the fees?
At the start of the course, I encountered a range of communication styles. I was offered a basic overview of the course, a timeline of when assignments were to be completed, and was made aware of the expectations. This gave me an impression of order and organisation, which was needed to make the course more manageable. Still, the communication following the payment of fees and the initial enrolment was, to put it mildly, not great. It was only after the end of the pre-course that I heard from the coaches again.
The clan
Despite this, the cohort was an immense help. All 24 of us were in a Slack channel where we could communicate and ask for assistance. Additionally, there was an entire community of other students who were willing to lend a hand if needed. Personally, the cohort was the best coach throughout the course.
Studying in the Age of YouTube
Attending the course remotely from the get-go seemed like the obvious choice - given that public transportation in London is about as reliable as the British weather forecast. Snuggling up in my blanket, I embraced the opportunity to experience an entirely online-based learning atmosphere. The flexibility it offered was unparalleled - I could access the course material and complete assignments whenever it suited me best without needing to adhere to a strict schedule or attend classes. It also enabled me to manage my time, allowing me to complete the course on my terms.
Another great thing about this online-based learning environment was that it enabled me to make full use of external resources - like videos, tutorials, and lectures - to supplement my learning. Even though the course makers provided us with plenty of resources of their own, it was still nice to have the option of outside sources.
Lastly, the online-based learning environment allowed me to connect with a global community of learners. In spite of the drawbacks, like YouTube Shorts destroying my productivity, my online learning experience was still positive, and I wouldn't let the inability to attend on-site deter me from taking the course.
Ruby, Command Line and Other Elements
My journey through the pre-course has given me an insight into coding. Though I had previously attempted to learn to code independently, I learned more in the first two weeks of the course than I had ever known before. No, I wasn't an IT genius shocked by the course's teaching. I was simply somebody with limited knowledge. But was this the same for all my peers? No. There were many people who, due to other commitments such as work or family duties, were unable to complete their pre-course. Despite claiming that someone who did not complete the pre-course could not enrol on the main course, everybody who wanted to join was still allowed to do so regardless of whether they had gone through the pre-course. However, not completing the tasks set would have an effect over time, leaving a person feeling increasingly behind.
My studies consisted of 4 hours of actual coding, five days a week. The course was said to be an average of nine-five daily, yet I felt the time I invested was enough to finish the pre-course comfortably. You’ll learn to use the command line, which, although complex at first, becomes increasingly efficient later and a handy skill. You will also be introduced to some coding tests, which at this period of my studies, sounded like it was being spoken in the national language of infants, gibberish.
Why Ruby?
No, Ruby isn’t some girl. Rather, it is a language which you spend the majority of the pre-course and the first half of the main course covering. But during my experience of seeking employment, it is seldom a desired ability. I understand that Ruby is a fairly straightforward language to learn, therefore allowing one to focus on the fundamentals. This, in turn, makes other languages easier to learn. But I can't help but think that this time could have been better spent mastering another language, especially as every day is money ticking away.
Summary
For those that made it read down here; congratulations! And for those who skipped directly to this, shame on you (I'm only kidding). All in all, the pre-course was an enjoyable experience. Although there was a lot of time wastage, I did learn a fair amount, and it is something that should be taken seriously. However, would I have considered it worth the investment if the remainder of the course remained like this? Most definitely not.