IDE

From Jonathan Gardner's Tech Wiki
Jump to: navigation, search

What?

IDE stands for Integrated Development Environment.

Why?

I don't know, really.

My "IDE" is the bash shell, ViM, all the GNU tools, and whatever program I am using.

My thought is that there are people who really, really don't want to learn the UNIX Philosophy. So they go about trying to recreate it, poorly. The result is the IDE.

There are others who can't bear the thought of using their own brain to understand or analyze their code. So they feel like the IDE can do a better job. (It can't. No computer is smarter than a programmer.)

There are others who don't know how to keep things simple and abstract. They like the IDE because it makes cut & paste a zillion times easier.

What to do?

Just avoid IDEs. If you run into a project that requires it, take the IDE apart and learn how to do it from the Linux bash shell. If that's not possible, then you're not doing it right.

What advantages to not using an IDE?

  • When you're using the shell, the ENTIRE FREAKING SYSTEM is literally a few clicks away. Now, those clicks are on the keyboard and requires some memory of what exists and how you spell the command.
  • If you forget how to do something, GIYF and there are man pages and help docs. And you can write things down! This is the magic of using words and sentences rather than points and clicks, which I equivocate with grunts and pointing. (How does Google index "Click on the app menu, then the config item, then the options tab..."? It can certainly handle "edit the config file and add a section called "params".)
  • Learn how to write programs that tie into the UNIX system.
  • Learn how to use Makefile. Yes, it's old, but it is wholly sufficient.
  • Can your IDE send email? Mine can: mail -s "See? Email!" you@example.com
  • Can your IDE redirect the output of a command into another? Can it redirect the output of a command into a file?