2 ms·

No, it's your fault. Saying your IDE is to blame is the equivalent of saying using C to program is making you stupid because it abstracts you too far away from

No, it's your fault. Saying your IDE is to blame is the equivalent of saying using C to program is making you stupid because it abstracts you too far away from the underlyung architectures. Or like using the languages implementation of quicksort is bad because you don't know how efficient it is. IDEs are great because they can provide you with useful information about your project, and they can automate tasks, like refactoring, or setting up the boilerplate code. If you feel like you don't know what's going on, then it's up to you to understand what the IDE is doing. Once you know that, you'll appreciate the value of the tool doing most of the heavy lifting for you so you can focus on the actual work that needs to get done.

zedshaw 12y ago
In a language like C# I agree with you. You have to use an IDE to get anything useful done. Same with a lot of iOS development, and Java. But, tools have a major impact on people's ability to work. If you aren't used to using a tool it can be incredibly difficult to get started and feel capable. Telling someone that they're at fault when they're basically forced to use a foreign tool to do their job is disingenuous. I mean, if you went to work somewhere that used Vim only how would you feel if everyone said you sucked because you had a hard time using Vim? That's basically what you did here.
- Delmania 12y ago
  No, I think you misunderstand. I'll stick with Visual Studio here because that's used as the classic example. Visual Studio does a lot of the heavy lifting when generating boilerplate code for things like Entity projects and ASP.NET MVC projects, and it does hide a lot of those configuration files. However, there is nothing stopping you from looking at those files, and investigating what tools VS is calling under the hood to generate them. The individual is at fault because he's not taking the time to learn what Visual Studio is doing and how C#/ASP.NET projects are organized. That exercise can be done independently of an IDE. Don't blame the IDE, it's like blaming the bread machine for not teaching you how to make bread.

zedshaw 12y ago

In a language like C# I agree with you. You have to use an IDE to get anything useful done. Same with a lot of iOS development, and Java. But, tools have a major impact on people's ability to work. If you aren't used to using a tool it can be incredibly difficult to get started and feel capable. Telling someone that they're at fault when they're basically forced to use a foreign tool to do their job is disingenuous. I mean, if you went to work somewhere that used Vim only how would you feel if everyone said you sucked because you had a hard time using Vim? That's basically what you did here.

Delmania 12y ago
No, I think you misunderstand. I'll stick with Visual Studio here because that's used as the classic example. Visual Studio does a lot of the heavy lifting when generating boilerplate code for things like Entity projects and ASP.NET MVC projects, and it does hide a lot of those configuration files. However, there is nothing stopping you from looking at those files, and investigating what tools VS is calling under the hood to generate them. The individual is at fault because he's not taking the time to learn what Visual Studio is doing and how C#/ASP.NET projects are organized. That exercise can be done independently of an IDE. Don't blame the IDE, it's like blaming the bread machine for not teaching you how to make bread.