Note: I was a part of a remote cohort due to COVID-19. Pros: - The community at Makers is truly amazing and people always go out of their ways to help each other. - Job support after graduation is great, there are plenty of workshops for people who are at applying stage or interviewing stage. Sometimes coaches take a while to respond, but I had a positive experience most of the time. I got help with my CV, cover letters and advice on preparing to different kinds of interviews. - Almost all of the jobs from the partner scheme were very high quality vacancies that you would want to apply to. - This bootcamp puts a lot of focus on industry best practices, such as TDD and Agile - employers value this a lot! - At Makers, you learn how to learn. By the time of our final project, I was confident that I could pick up any technology that I need. Some teams even managed to build their final projects in completely new languages and frameworks. Cons: - The curriculum has some important areas left uncovered, the most obvious one is working with the cloud. I acknowledge that the course is quite intense anyway, but there is a lot of value in going over the basic stuff, as AWS or Azure are listed in every job description nowadays. - Makers has little learning material of its own, which makes the value for money of the remote course questionable. I think that you are paying for a platform that connects you with like-minded people (your cohort) and job support, which are probably the most important things if you're a motivated career-switcher. However, 99% of the technical information we used is available online for free. I would appreciate if there were more learning materials, especially about explaining different tools and how to set them up. When youre doing the course remotely, it becomes a lot more difficult to reach out to someone next to you and solve a problem quickly, like you would on-campus. - For the majority of the course, you get to work in pairs every day. I really liked pair programming, but I also think that it could be structured in a better way. We would have one big task for the week, but you switch partners every day. If your new pair partner had done less work, you start where they ended. While there are some positive aspects to it, such as consolidating your knowledge by doing something several times, if you're a technically strong student, it will eventually be a frustrating experience repeating the tasks for 8 weeks and never getting far. Personally, I would've liked it better if you had one pair partner per week - this would have made the experience a lot less chaotic, while still getting to work with many different people over the course. For the projects, your team is fixed for the week or two and everyone I talked to liked it that way. |