Linked by Thom Holwerda on Fri 18th Dec 2009 16:58 UTC
Thread beginning with comment 400346
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
So.... you enjoy writing boilerplate code? If you aren't writing it and rather have it saved off in a file, then what is the difference between that and an IDE except for the time it takes to do it? You wrote it? big deal.
besides that, languages with huge frameworks under them were meant to be "cobbled" together, if by that you mean reusing highly optimized code.
The world you need to fear is where researchers are trying to taking it... Modeling that generates most of the code for you. My graduate prof is researching that with UML right now.... not sure why he chose UML when formal modeling languages are much more expressive and precise... you would think it would be easier to generate code from that.
So.... you enjoy writing boilerplate code?
Of course not, no one is.
The issue in this subthread is about 'professional programmers' who *depend* on tools to do this for them because they couldn't do it themselves, since they actually don't know/understand what is going on 'under the hood'. Their knowledge is, in effect, very shallow.
And once you understand the boilerplate code (and the reasons for it), then sometimes/often, you can do it yourself much better than the tool can.





Member since:
2009-02-19
That was always my fear: I've heard horror stories about people who can basically only work with Java inside Eclipse, have a very weak grasp on what's actually going on when their code executes, and just get carried through haphazardly slapping their code together with immense help from the IDE. I've never wanted to be that coder, and I've long been a proponent of gvim, an xterm, and Makefiles.
That's actually something of a culture conflict where I work, because a lot of the other programmers here come from Java or C# backgrounds, and think that's an extremely antiquated viewpoint, and that my productivity would be immensely greater if I'd just start letting a well-designed IDE do a lot of the grunt work for me. And they may be right, but I'm enormously terrified of becoming a Java Cobbler.