For example. let's say "bubba", needed to know why his valve would not come on. He goes online and finds this:
Code:
Valve:=(SW1 AND LS1) OR ((LS2 and SW1) OR LS3);
Most likely he would just turn off the computer and brute force the troubleshooting or go find and engineer.
Now let's say he finds this:
Code:
SW1 LS1 Valve
--+--][-------][---------------------------------------------()--
| |
| LS2 SW1 |
+-][-------][----+
| |
| LS3 |
+-][-------------+
Within seconds he will be able to easily locate the problem.
A good programmer is not one that just gets something to work, nor does it the fastest. A program written by a good programmer will not only work properly, but will also be easy to maintain by the next person who uses it.
So my point is, having and using the tools properly makes a good programmer. But losing sight of the big picture and abusing the tools, can make a not so good programmer.