3 ms·
Always use an IDE for significant software projects. Maybe not for small scripts, or for faffing about on your own learning to code Charles Petzold style. But f
by bitwize 5y ago
Always use an IDE for significant software projects. Maybe not for small scripts, or for faffing about on your own learning to code Charles Petzold style. But for professionals working on production code, artificially restricting your productivity by denying yourself the time- and effort-saving features of a good IDE is tantamount to goldbricking.
- jlokier 5y agoCounterargument: Artificially restricting your productivity by denying yourself the features of a high-functioning daily-driver editor and CLI git+make and replacing them with a low quality IDE that lacks useful features and the features in it don't work very well anyway is tantamount to goldbricking. This is very common in embedded systems. I ditched one such IDE in a project a couple of years ago and switched to Emacs + git + make + command line compilers. The productivity improvement was huge. Finally, decent tools. Even debugging worked better via command line GDB. It was more reliable than the one in the IDE, and scriptable. The quality of what went into the repo went up as well.