Brian,
Good to see you're back in the flow of things.
Before you continue to blow this guy out of that water that he doesn't know enough or is not skilled enough, I think "we" as the people who are helping re-write the questions for up-and-coming Linux sys admins, we should evaluate what truth we can pull out of this person's email and apply it. We'll only made the quality and caliber of the LPI test that much better.
Issue 1: Fill in the blank.
"'fill in the blank' questions were often hard to understand, given with little criteria/syntax to use. There are 50 ways to do any one task in Linux".
True, there could be 50 ways. And, if the fill-in question is not detailed and specific to what LPI is testing, we do a disservice. As we discovered during our writing, to make a question challenging and understandable according to the topic objective is a difficult but necessary responsibility.
How can we do this better?
Issue 2: Question Confusion
"More so, silly stuff like piping and input direction questions seemed to just be there to be confusing, and not really get to the bare idea of what it does. You don't need to combine two pipes and a stdin into one question, it just makes it confusing, regardless if you know what they do. "
Again, it sounds like this person has two questions in one (possibily) and became confused. I disagree that one doesn't need to use two pipe in combination. If we minimize confusion, the knowledge can be better assessed.
Steve
_______________________________________________ lpi-examdev mailing list [EMAIL PROTECTED] http://list.lpi.org/mailman/listinfo/lpi-examdev
