Jumping on the bandwagon of this is a pretty ridiculous "article". If the advice is "learn how things work before using some kind of automation" that's valid g

Jumping on the bandwagon of this is a pretty ridiculous "article". If the advice is "learn how things work before using some kind of automation" that's valid guidance but this article seems to assume using an IDE or something like that is a substitute for using your brain, which is pretty bogus. Not everyone who uses an IDE is doing it because they want fancy "code completion" or "AI-enabled write a for-loop for me". I didn't get the hype around VSCode until I ended up working on a project where I was forced to use a Windows PC but the machines I was interacting with were Linux-hosts. The "Remote SSH" capability wasn't just "slightly helpful" it was realistically the only way (along with VSCode IDE) to navigate a project that had thousands of files of proprietary, non-open source code (i.e. you couldn't use github or something "offline" to traverse the code base). Remote SSH enabled me to go from hating life using grep / ripgrep and nano/vim/emacs to figuring out a crazy complex code base to being able to wrap my head around the design thanks to VSCode's "jump to definition" and other really helpful features. I use VSCodium and open-source plug-ins now for personal work and I'm constantly finding new and useful features. Addendum: If you work in languages like Python, the single-step and debug experience in VSCode (haven't tried it in VSCodium) is also really impressive. You're not using some strange Python IDE which has its own ideas about how do "single-step" and "watch variables".