I also didn't say "windows specific tooling". A modern code editor or IDE already covers 80%, if not more, of what the article's tools cover. You don't need sep

I also didn't say "windows specific tooling". A modern code editor or IDE already covers 80%, if not more, of what the article's tools cover. You don't need separate applications for the things that article explains as use-cases. And by not using or advocating unix-specific command line utilities, you solve two problems: people don't need to learn commands they don't want to learn, and the tools that you do use tend to be cross-platform by default. Anyone on Windows, Linux, MacOS, FreeBSD, etc can use those same tools. Telling a contributor "we recommend using VS Code with these extensions" in 2024 is pretty much the lowest barrier to entry you could ask for. Whether your build tooling requires platform-specific tools is a completely different issue: this article and my comment on it isn't about that context. They're about commands that the article claims are essential to you, a person, in order to be a better developer. And to that statement my response is: you really don't. These can certainly be useful to know, but they're also completely optional.