A recent article brings up some interesting discussion. I definitely agree that high quality code can be created without tools or any automation.
But in organizations where you have tight deadlines, fewer developers and more features than ever, something has to give. To me, saying that you don’t need tools or automation is like saying you want to dig a hole for your pool with a spoon OR climb Mount Everest jumping on one foot OR you get the point…Sure you can write high quality code, but how productive will you be when you have your customers on your ass for the next feature?
Additional comments by the author goes on to say:
The very point of a tool is to change a process. Usually the goal is replacing a manual process, with an automated process.
Well, how is this changing your process? Isn’t that taking something that may take 1 hour manually down to 1 minute something that is desirable?
Either way there are plenty of tools that don’t change your process. The ones I’m very familiar with is static analysis tools. The whole point of them is to extend and embrace your existing process.
But with that said, let’s look at how some IDEs have evolved. Going from a text editor to an IDE, I guess is changing your process. But what are the reasons for this? A more targeted debugger, auto completion, refactoring etc. What does that do? It makes you code faster and smarter. I think I’m more than happy to change the process for that.