Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Starting the Syllabus with Backend vs Frontend #1

Open
kabaros opened this issue Mar 17, 2017 · 3 comments
Open

Starting the Syllabus with Backend vs Frontend #1

kabaros opened this issue Mar 17, 2017 · 3 comments

Comments

@kabaros
Copy link
Contributor

kabaros commented Mar 17, 2017

Few of us feel that introducing Backend (Node) before Frontend (React) could be a better path for our students.

Pros:

  • It's a less confusing ecosystem on Node, which could help the students to concentrate on getting their coding and JS core skills honed.
  • Starting with Backend fits how people and projects work (traditionally)
  • It seems to be the path taken by other coding schools (CC, F&C etc...)

Cons:

  • It might be too abstract for our students at that initial stage

We're experimenting with how we can start with Backend while making it less abstract. Few of the ideas floating around include Building a Frontend ourselves (the mentors) to reflect the Backend code the students are writing, or even using something like Slack Bots to do coding (which is fun and helps them learn the core concepts and understand how they can apply to anything)

@rarmatei
Copy link
Collaborator

@kabaros I'm still getting familiar with the syllabus, so please correct me where I'm wrong, but I understand the students will have already been taken through HTML/CSS/JavaScript by the time we get to Node/backend.

If that's the case, I don't think Node will be too abstract, as I'm assuming by that stage, they'd be familiar with how JavaScript is used to make pages interactive, and other more "tangible" examples on why JS is useful. Then Node can be a nice follow-up to how they can populate their pages with server data (or building the front-end ourselves, like you mentioned, though I'm wondering why this can't be built by the students as they're working through the modules?).

And once they're familiar with front-end and back-end basics, React can be a great module to finish on, where everything is made interactive, and it's gonna start to look more like a real world application.

But if we're planning to keep the last two modules (node and react) a lot more coupled together (use them together to build a complex app) and more separate from the first few introductory modules, than what I said above might not work?

@kabaros
Copy link
Contributor Author

kabaros commented Mar 23, 2017 via email

@Amwam
Copy link
Member

Amwam commented Mar 26, 2017

I think teaching node first might make sense. Largely because testing can be introduced a lot earlier in the course. I think having tests in place for homework has made things easier for the students.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants