What are projects?
Projects are a space to practice, learn and showcase what you can build with your code.
If you are learning new languages we recommend that you learn by building, which also leaves you something to talk about at interview.
Why are they important?
Not only are they great to practice problem-solving, but they also represent what you can expect to be doing in your first role when creating business and user focused solutions.
What should I be building after the Course?
By the time you finish the Makers Boot Camp, you will have experience of working in both team and individual projects.
We recommend that you focus on a language is that you really enjoy, building projects you are genuinely passionate about. This will make it easier for you to talk about them and be enthusiastic with employers.
How big should they be?
Rather than having a few large projects which can seem daunting, we recommend that you have a variety of smaller projects, so you can pick and choose the ones that you are more confident talking about.
This is great if you want to build projects in multiple languages as you can show your diversity within different tech stacks.
These may start out as just individual features with each one being their own project which you later build into a larger project.
For inspiration and project ideas click here
How and why to talk about them in an interview?
When writing applications and in interviews, projects are used to demonstrate your technical skills and understand more about your design process, technical knowledge and decision-making approach.
What interviewers really want is to get inside your head and to know how you think. Talking them through your project or doing a tech test is a way for them to gain this insight.
TALKING POINTS ON YOUR PROJECTS
Be prepared to talk through at least two of your projects in detail. They don’t need to be finished projects; try to pick ones that either fit the job description really well or ones that you are really passionate about.
Prep answers to the following:
What went well and what did you enjoy?
What did you learn?
What would you do differently with the knowledge you have now?
If you had more time, what would you add and how?
Explain your approach and how you made the design choices that you did.