[at_a_remove]

That sounds reasonable, from a "passion" angle.

However, I would like to hear what someone who dislikes sysadmining but must anyway has to say. Why? A different perspective. I know some sysadmins who "left the car up on blocks," as in, they couldn't stop tweaking and fixing and so on, and they love that, and that's great.

Someone who is forced into the job, however, is communicating to me what I would expect to be the most necessary tasks. Maybe I also am in a similar place and would like to get on with the rest of my job. And in an Agile world, programmers get pushed into sysadmining ... at least, in some versions of Agile to which I have been subjected.

[AdieuToLogic]

> However, I would like to hear what someone who dislikes sysadmining but must anyway has to say. ... Someone who is forced into the job ...

The only way a job is done consistently well is by those whom want to do that job well consistently.

HTH

EDIT: added missing "do" verb.

[Zarathustra30]

Too bad.

Sometimes a business can't or won't hire a real sysadmin. The people forced into the job need guides just as much.

[AdieuToLogic]

> Too bad.

> Sometimes a business can't or won't hire a real sysadmin. The people forced into the job need guides just as much.

I was making a more general statement regarding people having to do tasks they don't want to do, even if they have the skills to do them. Which makes resources helpful to "people forced into the job" rather difficult to produce.

How can one make a guide to assist people to be successful in something they don't want to do in the first place?