How so? I'm just saying being able to produce quality code without your favorite IDE is a good skill to have.
The problem is that no junior will ever write quality code, and neither should you expect them to. The most important thing for a junior is for them to easily get up to speed, and realize that "Wow! I can actually do something with this". Trying to focus on quality early, and you'll just struggle and lose motivation. How do a junior even know what quality means?
The will to write quality code grows from professional pride, and that comes later when you understand what you're doing and can make good decisions from experience. That is my view of it all.
Well then "quality" might not have been the right word. I mean code that works. IDEs will do a lot for you, including fixing your mistakes, which often means you won't learn from them.
I do agree with what you say about motivation though and I feel like I should clarify my thought: I'm not saying juniors should not use IDEs, I'm saying they should avoid using only that and sometimes go back to the basics so they can fix some mistakes by themselves and learn whats happening in the background (building process is also something IDEs hide a lot).
I just feel like learning to code only using IDEs is like learning to drive on an automatic transmission... but then again, it's the norm in some countries, so let's agree to disagree if you think that's ok 😁
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.