So we’ve been arguing among the team about exactly that, and can’t come to a conclusion.
Some think autocompletion per se, without snippets, is OKAY for beginners and will help them make sense of methods and classes. But snippets might make them skip over fundamentals/basics.
Some think autocompletion, including code snippets, will fast-track their development in the beginning and give them the confidence they need to persevere.
The site you linked looks less like a question or discussion and more like selling points for your website’s products. We do not allow commercial links promoting products or services, so I have removed the link, but have left this thread open for others to chime in.
Post doesn’t talk about e-commerce or Snipcart at all, and we do dedicate considerable time to actually producing content that helps devs without pushing Snipcart, but hey, you’re in charge here.
Would still love to hear what devs think about the issue, so thanks for keeping it up!
I can make arguments for or against.
My argument against auto-completion is that I think that a lot of fundamentals are really ground in through the act of typing each quote, curly-brace, and semicolon. We all run into errors where our brackets got mismatched or our code blocks got confused. If they are always generated automagically it can be a lot harder to identify the problem. Going one step further, many syntax-aware editors will do even richer code-completion by suggesting method names etc, and will conveniently tell you what arguments it expects. Does building the habit of typing the first few letters of a method name and hitting
tab interfere with newbies’ learning or is it just the way things really work?
On the other hand, I see new students get extremely frustrated by typos and misspellings. Without the experience to identify when an error is caused by a typo, they can get completely derailed by them. Editors with autocompletion can help avoid these.