3 ms·
You forgot to add "for me ...". You also implicitly defined IDEs as "the right tools". After that you imply that those who do not use "the right tools" (in your
by the_third_wave 5y ago
You forgot to add "for me ...". You also implicitly defined IDEs as "the right tools". After that you imply that those who do not use "the right tools" (in your definition of "right") are "severely restricted in the complexity of the programs [they] can create".
In other words, you state that your way is the right way while my way is wrong.
Notice I did not state that my way is the right way for everyone? What makes you think yours is?
- bitwize 5y agoIt's one of those "the mouse is objectively faster than the keyboard, no matter how much it feels otherwise" things. So much of the taxing minutiae of programming is automated away by a good IDE that, unless you're working on a very small project, the time and effort saved is worth it.
- the_third_wave 5y agoThat argument can easily be turned around by adding a short phrase: As long as you're working on a fairly standard type of project much of the taxing minutiae of programming is automated away by a good IDE that, unless you're working on a very small project, the time and effort saved is worth it. In other words, that IDE which may assist you while you're building yet another CRUD project gets in the way when you're, say, developing a driver for a sensor on an IP camera based on a reverse-engineered example.