Week restructuring

[NouraldinS]

I can see that this week's current flow is made very carefully, by someone who is very experienced with ReactJS, which is very good.

Although I would argue that this flow could be simplified much more.

The week's learning outcomes merley revolve around the world of react. Which could mislead the students. Especially in ReactJS's case, as it has very complicated and various structures to work with, but the idea that this week had touched less which I believe should consume most of the week's time, is the React component.

The React component is the most valuable asset, and having an entire day only talking about what a component is even without much code is a very good first encounter with React, which I'd discussed with my other friends from FAC and agreed upon.

The entire week's goal should be dedicated to understanding the component rather than flooding the students with new classes, prototypes, es6 ...etc.

@oliverjam @ibraghada @yasminhillis @sofer

[oliverjam]

Thanks for the feedback. I agree that learning React's component model (and the component lifecycle) is important for a React developer. I would love to devote a whole day to teaching those concepts, but we just don't have time in React Week.

We have 2 full days for teaching, and lots of things to cover. Quite a bit of that time is patching gaps in knowledge due to the first 8 weeks of the course not focusing very heavily on modern frontend. I don't want to sacrifice any of that because it would make actually learning React much harder (for example if you've never seen an ES6 class before the React component syntax will be confusing).

I think it's more important to get students productive and creating things with React as quickly as possible so that they start to see how it can help them. If we spent the week studying the theory of how React works it might put some people off as they'll struggle to see the benefits of the library.

This approach also means students can quickly see if they like React, and if it will work for their upcoming client projects. They can then either decide React isn't for them (and we haven't wasted too much of their time) or they can use it on a real project where they can dive deeper into how the library works and gain more advanced understanding.

I would like to include some more resources for people who want to gain that deeper understanding, so that people can do extra reading during/after React Week, so maybe we can work on writing some of those.