2: Keep your toolchain and build process independent from the operating system and editors.
3: Don't use IDEs.
4: Have a one command automated build and run as soon as you write a basic skeleton of your project.
2: Keep your toolchain and build process independent from the operating system and editors.
3: Don't use IDEs.
4: Have a one command automated build and run as soon as you write a basic skeleton of your project.
an IDE adds complexity when the main goal should be to learn to program. An IDE has a bunch of features you need to learn and understand when learning to program by itself is hard enough.
You don't have to use all the power but letting for example Visual Studio handle the project references and build for a .NET project will allow a beginner to focus on coding. Not to mention all the tutorials will assume they use Visual Studio.
I finally settled on Python after jumping around quite a bit and am still learning.
They introduce unnecessary complexity and tend to make users too dependent on them, while hiding actual functionality behind colorful buttons. There's a reason most productivity-focused programs are terminal or text-mode programs.
An IDE-dependent toolchain is a sure sign of an immature project and, likely, rookie developers.