Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

January 29 2010

mathias
16:42

At Rubyfringe a few years ago, I suggested that IDE features are language smells. This statement reflects a lot of bias: I spend a lot of time holding a programming language hammer, and thus every problem looks like a language paradigm nail to me. But just because I'm biased doesn't mean I'm wrong. Or more importantly, even if I'm wrong it might be interesting to ask ourselves what would happen if we looked at the tools in our development tool chains and treated them as failures.

You can play this game with IDEs, issue managers, wikis, time trackers, project management applications, even email. They're all sitting in their own silos completely disconnected from the code that is what we actually build and test. Honestly, when you look at the commit hooks and APIs that we use to bind them together, don't you despair? We're using tissue paper, spit, and baling wire to integrate components without any attempt to rethink the entire jenga pile of tools.

2010/01/beautiful_failure.markdown at master from raganwald's homoiconic - GitHub