6 ms·
1: Keep everything as simple as possible. 2: Keep your toolchain and build process independent from the operating system and editors. 3: Don't use IDEs. 4: H
by nukeop 9y ago
1: Keep everything as simple as possible.
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.
- axvk 9y agoWhat do you have against IDEs and what languages do you mainly write in?
- Teichopsia 9y agoNot the OP. When I started out I took a conscious decision to stay away from IDE'S. 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.
- deleted 9y ago[deleted]
- cc81 9y agoWhat language did you use?
- Teichopsia 9y agoPython.
- megaman22 9y agoPython is, possibly because it originated as a scripting language, very amenable to non-IDE development. In general, my experience is that the less statically-typed a language is, the less essential IDEs are.
- cc81 9y agoThat is a language that is perfectly fine to start without an IDE but for example Java and C# are pretty much designed to use with an IDE, at least when you are building something that is non trivial. 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.
- Teichopsia 9y agoI had a feeling it would be something along those lines. When I began I actually started with Java and later dabbled with C# but didn't get far with either one of those. I had no idea what I was doing. I probably still don't ¯\_(ツ)_/¯ I finally settled on Python after jumping around quite a bit and am still learning.
- nukeop 9y agoC++, Python, bash, javascript, Rust. 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.
- dukeflukem 9y agoFor .NET the IDE is almost essential
- darkwinx 9y agoIf you just starting learning programming, I totally agree with you. I always tell that to everyone wanting to learn programming. But, if you already good enough in programming or a professional one, you should use anything useful for your productivity, including IDE.