Respond to a Review

Responses should answer questions and address concerns raised in the review or clarify information about your school. Once we authenticate that you are an official school representative, we will publish your response under the corresponding review. Each review is limited to one response, but you may submit a new response to replace the previous one. Please restrict comments to addressing the content of the review in question and refrain from including advertising/promotional material or unrelated exchanges. Official representatives will have the option to make a contact email available, but please avoid directing users from our site through other means.


Reviewer Name Review Body
Georgia Connell-Bass My Coding Experience Prior to the course: Knew I liked coding for several years but didn't have much experience prior to the course apart from a few bits and pieces with Fortran at uni, Swift and very basic HTML and CSS. Content: There is a great balance between keeping up with the latest technologies and developments in the industry and teaching content that incorporates the fundamental aspects of programming that can be universally applied across different languages and frameworks. We were taught coding best practices: code reviews, unit testing, properly documenting our code and backing it up regularly on github. We got to work as a team and individually, on brand new and legacy projects. Class Size: There were 2 different classes in my cohort that ran in parallel. Max size 8 people per class up until the point where you can choose your track in week 14 after which my class was 9 so it still stayed pretty balanced numbers wise. The small class size definitely contributed hugely to my learning, you get a lot of 1-1 time with the trainers which was brilliant for clarifying things we'd just learnt or getting some help with a difficult exercise. I think I would have begun to struggle in a larger group of 12 or more. The Teachers: I was lucky to get the chance to learn from all the trainers at Mayden who did their best to make us feel welcome and included, accommodating their classroom and teaching style for students different learning needs. Mike was my trainer for the majority of the course. He taught me not just how to code but how to write code that is good quality, concise and secure. He consistently went above and beyond for his students, sometimes staying late so we could work on our portfolios, giving people help with CV writing, always being approachable for advice or if we had any problems. It was great to have Ashley around while he completed his teacher training, he brought a different perspective to problems and was a patient teacher, I think he will fly with his first cohort! :) I took Charlie’s track for the final two weeks: Charlie is very fun and full of energy, he has a very practical approach to teaching which suited my learning style, the track was very exercise based and felt a lot closer to project weeks but with a bit more structure and guidance. Classmates: These people really made the experience amazing! Mayden Academy are very good at putting together a team of people that work well together and get on. I made some great friends from the course and I think we all learnt a lot from each other, everyone has a unique approach to solving a problem or a quicker, neater, more interesting way to write code. We did a lot of pair-programming on the course and I found it invaluable it helped to improve my standards and got me to think problems through and be able to explain my process to another person. Skills aside from coding: I felt like the course at Mayden Academy simulated what working in the industry is actually like. We pair-programmed, code reviewed each other’s work, learnt the ins and outs of Git and Github for backing up work, we planned projects from start to finish holding each other accountable for our mistakes and for our achievements, we rallied together and supported each other, it was awesome being a part of such a great team! We learnt Scrum, an organisational framework which is used throughout the industry (not everywhere but a lot of places use it or a variation of it) to estimate the speed at which a team can work through projects and breaking down projects into smaller more manageable chunks of tasks. The had daily quizzes and bi-weekly tests (just for your own reference) that helped us gauge how much of the content we had grasped and what we needed to go over. We had a daily meeting as part of Scrum which meant we were always checking in with each other about how everyone’s learning was going and how each project was progressing. These skills have put me in great stead for a job in the industry. Career Support: A full day dedicated to interview skills, CV and cover letter writing as well as ongoing support with job applications for the duration and even following the course. I even got some advice with writing introduction emails as it’s a huge blocker for me and I generally put it off so much the vacancy has been filled by the time I actually apply! The hiring event they put on was initially nerve wracking but ultimately exactly what I needed, it was great to just be able to chat face to face with representatives from really great local companies without the communication barrier of phone calls and email conversations and without the intense pressure of an interview situation. I think we all benefited from this stepping stone into the world of technical interviews and I think personally I owe this networking evening to the job I have now. Attending with a Partner: My partner and I took the course together, although we were in separate classes on the prior request of the teachers (this is for several reasons but the one that resonated with me most was that you then get to bond with your teammates better and have your own individual experience of the course). So in my cohort there were 2 classes of 8 and we attended in parallel. It was a great getting to share the experience with one another, we learn it quite different ways so we could help when the other one was struggling and we could talk though a problem together. Both of us have come to coding from different industries so it is nice to be able to share that understanding with each other now as we start our new careers. It was difficult financially choosing to attend together and we had to rely on savings as well as loans from family and friends to see us though so I would definitely consider that aspect as well before jumping in. But it was very worth it in the end :)