I’m not saying that there haven’t been occasions in the Codecademy material where I’ve found an unreasonably long variable or function name to be irritating, having to type it out… and yes, I can see how a more proficient learner might also want to have this functionality.
Opening up developer aids like this to complete beginners however opens the door to learning by rote, at which point you’re not learning what the code does but rather what pattern solves the exercise.
I’d draw a comparison to someone learning to play the guitar. Many people when they’re learning the instrument will learn a scale, say C Major, in discrete blocks of notes. They know that specific pattern they’re playing is the C Major scale, but not necessarily what notes it contains or where / how else they can play those same notes outside that pattern.
If the budding guitarist goes back to first principles and learns the theory behind why that is the C Major scale, how to formulate that scale, and where the root occurs elsewhere they’ll have a better understanding of the instrument.
Same with programming. Tools like Emmet are there to make you more efficient, not to replace foundational knowledge of how to produce the code in the first place.
We see plenty of people come to the forums as it is with questions about “how quickly” they can complete certain tracks, when the focus should always be on “how completely” they understand the material. For the most part, I think we manage to convince them that speed is not the important metric… but I suspect that introducing Emmet and other convenience features to the Learning Environment would exacerbate that and lead to poorer learning outcomes…