First of all a HUGE shout-out for keeping FCC moving forward!
Sounds trivial, but I know how much work, thoughts and fatigue goes into each step.
So props to @QuincyLarson, and all the FCC contributor for the constant effort.
Now, if I may, I would like to raise two main “concerns” I had:
- I fear at some point some longer explanation of some sort would be required.
I am not talking about long college-like lectures, but at least some sort of explanation about the reasoning why certain things are the way they are is mandatory.
I have a feat that without it, a new camper with zero experience in coding, following only directives, will end up knowing how to do a thing because “that’s what I was told to do” instead of “I do it like this because…”
So in my opinion finding a good compromise between “a boring wall of explanatory text” and “dynamic yet informative” will certainly be a challenge
- Hitting a wall, and overcoming it, is one of the most valuable lessons to learn.
We have all been there. Not only during the learning process, but also on the job.
There will always be a time where, as a dev, you will have to face a challenge that you have no clue how to overcome (yet!).
Learning to roll up my sleeves, do my own research, being frustrated, waste days (that always in retrospection are never a waste but experience gained regardless) of time only to do what seems basic, but ultimately overcome them, is what made me the developer I am.
Again, I think that finding a good compromise between “smashing into a wall”, and learning to struggle will be another good challenge.
That said I’ll see If I can contribute more concretely… looking at you flappy-bird-react