Disagree strongly on the premise you should walk to school uphills both ways because someone else had to.
I'm really sorry that that's what you took away from this post - it's not at all what I meant. This is why I pair the recommendation to not use an IDE at first with the recommendation to not teach Java (a language which really needs an IDE to be productive) at first, and suggest Python or other languages.
The core concepts never reach people because you don't know what you don't know.
I absolutely agree. A big part of that, though, is instructors trying to shield their students from the reality of the computers they're working with - in large part by using IDEs instead of programming in a text editor and compiling at the command line.
the only folks that work on *nix are the devops types that coordinate ci/cd (from a container, not as their desktop).
This is a common experience in larger companies, but as .NET and other technologies move away from requiring proprietary platforms that will be less and less the case. Even Windows developers have a real shell at their fingertips these days.
From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
This is a common experience in larger companies, but as .NET and other technologies move away from requiring proprietary platforms that will be less and less the case. Even Windows developers have a real shell at their fingertips these days.
I'm not certain this is the case. All the tools I use on Windows also have *nix counterparts. I think it's for ease of maintenance from an administrative and support perspective. My shell, browser, IDE and build toolchain all run on every platform (except Jenkins, this is the only pain point I have).
As a primarily Python dev these days, I'm not certain I'd recommend it first; package management is still a major point of pain. Rust has a much more intuitive first experience and better documentation imo. C# w/ .NET Core is also leagues better than it was in the Framework-only days, though using Visual Studio still provides a lot of "magic" to me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm really sorry that that's what you took away from this post - it's not at all what I meant. This is why I pair the recommendation to not use an IDE at first with the recommendation to not teach Java (a language which really needs an IDE to be productive) at first, and suggest Python or other languages.
I absolutely agree. A big part of that, though, is instructors trying to shield their students from the reality of the computers they're working with - in large part by using IDEs instead of programming in a text editor and compiling at the command line.
This is a common experience in larger companies, but as .NET and other technologies move away from requiring proprietary platforms that will be less and less the case. Even Windows developers have a real shell at their fingertips these days.
I'm not certain this is the case. All the tools I use on Windows also have *nix counterparts. I think it's for ease of maintenance from an administrative and support perspective. My shell, browser, IDE and build toolchain all run on every platform (except Jenkins, this is the only pain point I have).
As a primarily Python dev these days, I'm not certain I'd recommend it first; package management is still a major point of pain. Rust has a much more intuitive first experience and better documentation imo. C# w/ .NET Core is also leagues better than it was in the Framework-only days, though using Visual Studio still provides a lot of "magic" to me.