Visual programming = bad idea

Visual Programming and Why It's a Bad Idea

User evaluation of an IDE, framework, .Net

Why I Left the .NET Framework: "because it kept reasserting itself and wanting to be more than it was: an implementation detail"

New IDE?

Light Table, a new IDE concept

The IDE divide

Good viewpoint on the world of developers: either you know well the language, or you know well the tool. See the IDE divide.

"The developer world is divided into two camps. Language mavens wax rhapsodic about the power of higher-level programming — first-class functions, staged programming, AOP, MOPs, and reflection. Tool mavens are skilled at the use of integrated build and debug tools, integrated documentation, code completion, refactoring, and code comprehension. Language mavens tend to use a text editor such as emacs or vim — these editors are more likely to work for new languages. Tool mavens tend to use IDEs such as Visual Studio, Eclipse, or IntelliJ, that integrate a variety of development tools."

"One consequence of the greater language selection available to the editor-only developer is it typically includes languages that are more powerful".
 

Unix as IDE

A different view of what should be an IDE. Plus the difference of the UNIX world, simple things like everything is a file and the use of pipes.