>Most people aren't interested in mucking with >the process, they want the results.
This is an interesting observation considering how much time people will spend trying to figure out and use complex GUI based programs when they could do the same thing in less time, including the learning curve, with a non-GUI based tool. With a solely GUI based tool scripting is extremely difficult, and you have to learn how to do it the way the vendor wants you to (for example, Word Basic). Contrast that with something like the Gimp, which contains script-fu, but also contains bindings for other scripting languages -- making the learning curve for scripting the Gimp much less steep if you already happen to know one of the languages that has bindings.
If people were not interested in process, there wouldn't be classes which teach you how to use office suites because it would be so obvious how to use them. I know people who have a hard time using the tools they have because they can not remember the process (select a menu item, change a few options, hit ok) it takes to do something -- this problem transends the interface even, and is part of the general laziness people have. Unfortuantely, most people are more thought-lazy than time-lazy -- that is, rather than think through something, they'd rather just randomly try things until it works. Also, if people were only interested in results, they would realize that it's worth their time to learn the process if they know they are going to continually want the same kinds of results on a continual basis.
Unfortunately, a place that has more "junior" people than experienced people is a bad thing. My U lost my whole home directory when a disk crashed. Then they found out that the backups they had been making for weeks were bad also because they didn't install a certain OS patch. Things like this should not be put up with in a production environment. The goal should be to work with someone who has experience, not to be thrown into the mix with a bunch of other somewhat inexperienced people and hope that, together, you can work something out or solve some problem. Admittedly, that can be a great way to learn, but it won't leave the users happy. Choose your mentor carefully.
Slashdot Mirror
My 386SX has over 1800 days uptime. It takes to long to compile a kernel, nearly 12 hours, so I don't want to upgrade.
>Most people aren't interested in mucking with
>the process, they want the results.
This is an interesting observation considering how much time people will spend trying to figure out and use complex GUI based programs when they could do the same thing in less time, including the learning curve, with a non-GUI based tool. With a solely GUI based tool scripting is extremely difficult, and you have to learn how to do it the way the vendor wants you to (for example, Word Basic). Contrast that with something like the Gimp, which contains script-fu, but also contains bindings for other scripting languages -- making the learning curve for scripting the Gimp much less steep if you already happen to know one of the languages that has bindings.
If people were not interested in process, there wouldn't be classes which teach you how to use office suites because it would be so obvious how to use them. I know people who have a hard time using the tools they have because they can not remember the process (select a menu item, change a few options, hit ok) it takes to do something -- this problem transends the interface even, and is part of the general laziness people have. Unfortuantely, most people are more thought-lazy than time-lazy -- that is, rather than think through something, they'd rather just randomly try things until it works.
Also, if people were only interested in results, they would realize that it's worth their time to learn the process if they know they are going to continually want the same kinds of results on a continual basis.
Unfortunately, a place that has more "junior" people than experienced people is a bad thing. My U lost my whole home directory when a disk crashed. Then they found out that the backups they had been making for weeks were bad also because they didn't install a certain OS patch. Things like this should not be put up with in a production environment. The goal should be to work with someone who has experience, not to be thrown into the mix with a bunch of other somewhat inexperienced people and hope that, together, you can work something out or solve some problem. Admittedly, that can be a great way to learn, but it won't leave the users happy. Choose your mentor carefully.