[PeterStuer]

"I have a genuine fear for Junior developers using ..."

I have been around long enough to have heard the same about

- writing code on the terminal as oposed to on paper (their coding will become just trail and error)

- using debuggers (repeat until it works, they will never understand why it failed to begin with)

- using IDE's (real programmers don't need crutches)

- using languages with extensive standard libraries (how can they ever understand their code if they didn't write their own dictionary)

- using domain frameworks (TF is for people incapable of grokking NN's)

- ...

It's most often not the tool that is producing bad programmers, it's bad programmers holding it wrong ;)

[DonHopkins]

From the HN discussion about the video of "A Conversation with Language Creators: Guido, James, Anders and Larry"

https://news.ycombinator.com/item?id=19568381

>James Gosling wants to punch the "Real Men Use VI" people.

>"I think IDEs make language developers lazy." -Larry Wall

>"IDEs let me get a lot more done a lot faster. I mean I'm not -- I -- I -- I -- I -- I'm really not into proving my manhood. I'm into getting things done." -James Gosling

[jamil7]

Yeah I tend to agree. I also feel like the majority of my deeper software knowledge has come from reading/modifying existing code, debugging and reverse engineering rather than actually writing code.

[marginalia_nu]

I think it's kind of right though. Like we're in the midst of a generation of developers most of whom can't seem to be productive without stackoverflow or Google open in a tab somewhere.