Do you believe these 3 development tool myths?
*This post is from Brian Crowley, mrc’s Director of Development*
While at a recent tech conference, I had an interesting conversation with a long-time programmer. The programmer had apparently had some bad experiences with development tools, based on his views on the subject.
Frankly, nothing he said surprised me. I’d heard it all before. Most “anti-development tool” programmers usually cite the same reasons, and to be honest, I understand where they’re coming from. They’ve run into enough bad development tools in the past to form a pretty negative opinion of the whole lot. Their criticisms aren’t always accurate, and certainly don’t apply to ALL development tools, but I get why they feel that way. …
Suppose you’re buying a new computer. You find a great-looking computer at a local store, bring it home, boot it up, and…it’s extremely slow. You open up the case only to discover that all of the internal parts are at least 10 years old. You storm back to the store demanding your money back because they sold you an old computer. Their response: “Of course it’s new, look at the new, beautiful case we put it in.”
A few months into owning our first house, we learned something: The builder took some short-cuts. Unfortunately, you don’t recognize architectural defects when you buy the house. They become apparent after you’ve lived in it for some time.