Best tool for the job -- well, except voice since it works like crap and has worked like crap for three decades of hype, and will likely continue to work like crap for at least five more.
But I alternate between mouse and keyboard all the time -- sometimes the visual + mouse approach is more effective, sometimes mouse and keyboard at the same time are more effective, sometimes you've just got to get your hands dirty on the command line.
Like for working with editing code, I prefer multiple GUI windows with GUI task management. If I'm working on web projects you HAVE to test in the GUI since that's where the browsers are. If working with a compiled language I still prefer to go to the command line (with logging) just for the better control each time of the options and more verbose feedback I get than what some garbage IDE tries to water down.
Jason Knight
The less code you use, the less there is to break
Best tool for the job -- well, except voice since it works like crap and has worked like crap for three decades of hype, and will likely continue to work like crap for at least five more.
But I alternate between mouse and keyboard all the time -- sometimes the visual + mouse approach is more effective, sometimes mouse and keyboard at the same time are more effective, sometimes you've just got to get your hands dirty on the command line.
Like for working with editing code, I prefer multiple GUI windows with GUI task management. If I'm working on web projects you HAVE to test in the GUI since that's where the browsers are. If working with a compiled language I still prefer to go to the command line (with logging) just for the better control each time of the options and more verbose feedback I get than what some garbage IDE tries to water down.