Thank you for catching this, Chan. You’re right to flag it.
Keras Quest was migrated from older Boot Camp material, and the automation script used during that migration damaged parts of the content structure — repeated code blocks, too-thin lesson sections, and empty Backend Note headings included.
It is not intentional. We’re already fixing it, and this report helps confirm the exact failure pattern we need to clean up.
Hi Chan — I appreciate what you’re trying to achieve here, and I can see that you’re going through these quests very carefully.
One important note, though: please don’t treat the quests in this section as full-blown tutorials or complete courses. They’re meant to be pointers — curated signposts that show you what to look at, what questions to ask, and where to continue studying.
If you treat them as complete tutorials, they can become misleading, especially because they may give you a false sense that you’ve mastered the subject when you’ve really only completed a bootcamp-style orientation.
So after finishing any quest here, please remember: you’ve done the bootcamp. That’s valuable — but it’s only the beginning.
The quests are pointers, not substitutes for deeper study.
And I have to point out something obvious: you’re going too fast. Please don’t speedrun this.
One more thing, and I’m saying this because the pace itself is starting to matter.
From the outside, it looks like the quests may be turning into a reading checklist. Reading is useful, of course, but it is not the same as learning the subject.
The real learning happens when you build something with the idea, run into friction, break things, debug them, and try again. That trial-and-error loop is the part you should not skip.
So please slow down. After each lesson, make at least one small thing with it before moving on. Let it fail if it fails. Fix it. Write down what actually confused you.
If you move through the quests too quickly, they can give you the wrong signal that you understand more than you actually do. I don’t want the quests to do that to you.
These quests are pointers and bootcamp maps. They are not mastery.
And from decades of experience, I can honestly tell you this: you don’t need all the knowledge presented here before you start building something beautiful. I don’t learn everything first before I build either.
I learn as I go, on a need-to-learn basis. The reason is simple: you don’t actually need that knowledge until you need it.
If you only study a subject for the sake of studying, most of that knowledge will slip away.
Trust me. Learn it when you truly believe you need it.
You’ll know when you do.
Hello, Pippa.
While reviewing this quest, I noticed several recurring content patterns that seem inconsistent with the quality and depth of other quests. I wanted to check whether these are intentional or if they may need revision.
This is not limited to a single lesson.
Across multiple lessons, the same code often appears twice:
In many cases, the two versions appear identical. As a result, the Code Callout does not seem to add additional explanation or context beyond what is already presented in the lesson.
Is this duplication intentional, or should the Code Callouts contain supplemental information instead of repeating the same code?
Several lessons appear to consist primarily of:
Compared to other quests, the instructional content feels significantly lighter and less detailed.
I am unsure whether this is the intended style for this quest or whether additional explanation is still planned.
In multiple lessons, I found sections labeled:
Backend Note:
However, no content follows the heading.
The section header exists, but the actual note appears to be missing.
Could you confirm whether these Backend Note sections were intentionally left blank, or whether content was accidentally omitted?