[nickjj]

Hi,

Sorry you didn't like the course. I don't recall any snarky replies, but you're right. There were a few people who would have preferred a "code everything from a blank page" approach.

The problem is, how do you code up a 4,000+ line Python application with dozens of files and thousands of lines of HTML/CSS/JS together 1 character at a time?

It would take 100+ hours of video and you would want to punch me in the face after hearing me say "ok now type D I V close bracket" for the 400th time in a row.

A vast majority of people (as seen by the reviews) really enjoy the way it's presented and like seeing it get built up in 12+ stages. It's impossible to make everyone on the internet happy. The best I can do is listen to the feedback of everyone and continue tinkering with future content.

[ggame]

FYI - this is a snarky reply

[biot]

You're being highly disingenuous with your reply, to the point that I agree with the other comment that it is snarky. Assuming your audience already knows HTML and Python is perfectly acceptable if the focus is on building the application, not on teaching how to type HTML and Python from scratch one character at a time. A video could then say "Now we enter in this page of HTML [cut from blank editor to already typed in text]. Note the following sections: [brief explanation of important parts with highlights]" etc. which the audience can follow along via section-by-section downloads. This is a very standard style, and that you seem unaware makes you appear ill-suited for teaching anybody.

[nickjj]

Hey,

The course does mention you should have a basic understanding of HTML and Python before starting it. It's meant to teach you about Flask.

There's about 60 HTML templates in total. Rather than put the burden of copy/pasting each one onto the student, I decided to break the entire project up into 20 stages (separated by folders and git commits).

You get to see the application at 20 stages of development (to see how it gets built up). It starts with a single app.py file and finishes with the end result.

Basically I go over each line of code, and explain why it's written and what it does.

This style of teaching was a choice I made based on the direct feedback of hundreds of students in previous courses.

Most of them like the fast paced style where I talk over the code. There's also many hours of code challenges built into the course to get your hands dirty. The refund rate is currently less than 1%.