Learning to code with JavaScript and building UI with React

My experience with  @MCRcodes   as a Quality Assurance Tester.  This is an evening part-time coding boot camp based in central Manchester which runs for 24 weeks, from February 2018 to July 2018. Week 5 (March 2018) - Just the end of last week, I have received feedback on my assignments with lots of pointers to becoming a better coder. One of the suggestion was to use an extension on my code editor ESLinter. In the first session, Joe helped me set this extension up and it is brilliant. Why haven't I installed this years ago? Lecture wise, we have moved on to lots of theory behind coding. This knowledge will make our employable stronger and a stronger knowledgeable programmer. Session 1 -  Object Oriented Programming &  SOLID Object Oriented Design Session 2 -  Test Doubles & jest.fn() Week 6 - Continued with last week Object-Oriented Programming exercise, finally understanding the benefits of creating a good code design. Also...

blog image source Group exercise - make our own JavaScript quiz challenge based on knowledge gain around  Object Oriented Programming in the last two weeks,  the quiz game will be created using user stories only.  Learning objectives from this exercise: Understanding of OOP (Object Oriented Programming)? Can you explain what Object-oriented Programming is? Can you effectively break down a user story into a domain model? Can you use dependency injection to get objects to talk to each other? Can you use mocks to emulate dependencies in tests? Can you use spies to override behaviour of other objects? GitHub Quiz Challenge exercise -  https://github.com/SharifCoding/quiz-challenge

blog image source The experience of encountering annoying and unexpected problems is a daily occurrence for software developers. Without the right mentality, a regular barrage of difficult and surprising problems can make learning how to code frustrating. Read the error message; e rror messages are used when user intervention is required, to indicate that the desired operation has failed, or to relay important warnings. Remember, an error message is a good thing since you find it during development and not on a live release by a user. Challenge your assumption; w hat do you think is going on? If you make too many assumptions, you are bound to build an application where the requirements are off, or the user experience is bad. Always take the time to review the requirements and make sure you fully understand them. Create and test the hypothesis; a  hypothesis is a prediction you create prior to running an experiment. It states clearly what is being changed, what you believ...