3

The title here almost feels like a trick question to me. Not that it's intentionally trying to mess with people, but "which one first" is a bit of a false dichotomy. This is a somewhat unfortunate example, but it's the one I was reminded of. Long, long ago, in the ancient history of Stack Overflow, there was a... kinda rude and presumptuous question about a ...


2

I would definitely start with front-end. It's possible to avoid many of the warts of javascript by using ECMA6 or only teaching small pieces of the language. For example, loops and if statements are sane in JS--you don't have to show them the weirdness with == vs. ===. Another reason to start with front-end is that modifying pages by editing the DOM is ...


2

Front end First teach HTML along with inline styles(it is a bad practice though). Because it is very less strict in syntax. You can skip the <head> tag or anything even if you didn't closed the <body> at bottom it show the desired output.(It is a bad practise though) So, when you introduce such a language to students, they will wonder because ...


2

I'd like to summarize a few of the answers already given by suggesting a general framework for such "chicken and egg" problems. You have two things to teach that are closely related but different. You can't really learn one without the other. The solution to such kinds of problems is to use a spiral approach. This is already used to take students through a ...


1

There are already answers here. I will add a contrary one, as this point of view is missing. When designing a program, the best ones are the ones where the business logic was designed first. Therefore it is better to design the back-end first. That is get all the processing done. Then output the data, possibly in json. Then think about how it will be ...


1

True full stack from the base install of an OS with an IP address up to the next StackExchange? Multiple classes.. HTML+CSS is always first, then Linux Admin, Back End Coding, and Pure SQL. Only order requirement with the last 3 is that Pure SQL has to be done before Back End Coding, but some of the Linux admin stuff could help with solving issues OR using ...


1

I'll probably elaborate more on this in a blog post at some point but I usually do the following: Simple HTML (load from file, no styling) Simple baclend - I usually use Flask More backend templates programatically making a web page simple forms (GET/POST) Sessions Styling on the front end Using Web APIS Databases Simple JS A whole lot more front end ...


1

Students need at least a cursory understanding of how web pages are built before moving to the back end. Last year we did a project where there were groups split into front end design, front end JS, and backend PHP. The JS and PHP groups weren't able to get started without going back and learning the very basics of HTML. If it were me, I'd probably start ...


Only top voted, non community-wiki answers of a minimum length are eligible