campers hardcoding solutions for final projects about freecodecamp HOT 8 OPEN

One option could be trying to join the two, when that's possible. Taking the same example as above:

• One specific user story, using in test the exact values as in the user story.

When the #search-input element contains the value Red and the #search-button element is clicked, an alert should appear with the text "Pokémon not found"

• One generic user story, where test should be essentially the same as in the specific case, but using different value to search.

When searched text is not a Pokémon name, an alert should appear with the text "Pokémon not found"

from freecodecamp.

note, it's not only an issue for the Pokémon search app, I have seen this for the palindrome checker and the roman numeral converter too

from freecodecamp.

Yeah, campers seem to be struggling really hard with how to create original functions that meet the user story outcomes here.

This isn't wholly surprising, as up to the point where they get to the first project (and some of the later projects) they no longer encounter places where we ask them to generate small functions to accomplish a task. I think the fix is twofold. One, we need to test for and prohibit testing to the solutions. Second, we need to give campers smaller opportunities to build single functions from scratch that meet a tested objective - maybe something that looks like https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/#basic-javascript 🙃

from freecodecamp.

Yeah something like that basic JavaScript path would be great before we get to the html/css/javascript projects considering their bulky size.

As for the prohibiting testing to the solutions, I like the idea of a hidden test with additional inputs the code is tested against rather making all the tests generic. Some specific actual tests are nice so we can run the code right there and see a response in the console. If they're not coding just towards the solution, then those additional inputs will work and everything will be fine.

from freecodecamp.

@a2937 and @jeremylt

Yeah something like that basic JavaScript path would be great before we get to the html/css/javascript projects considering their bulky size.

that is why the new intro project is being created

freeCodeCamp/CurriculumExpansion#374

from freecodecamp.

I vote for this approach

One option could be trying to join the two, when that's possible.

A combination of generic and specific user stories would be ideal

from freecodecamp.

That's a good project but it's one project though. I'm proposing that we give back the campers the opportunities to do many small one off functions to practice open ended problem solving before they get to the certification projects.

from freecodecamp.