Thanks for the feedback. It's worth noting that at 20 minutes I stopped; I did not complete the documentation in 20 minutes.
You're correct that the overhead won't exist in a second attempt. I'd be interested to see how long it would take me just to write the documentation itself. Brandon On Fri, Oct 3, 2008 at 11:13 AM, Philip Olson <[EMAIL PROTECTED]> wrote: > > On 3 Oct 2008, at 06:42, Brandon Savage wrote: > > Hannes et. al., >> >> I took 15 minutes (I actually took 20), read the documentation, installed >> the PEAR package and followed the directions. But I wasn't able to finish >> the task in the time you gave me. >> > > A 25% increase of required time isn't too bad! :) > > Some of the challenges: I'm using a Mac and the PEAR package gave me some >> trouble. Once I resolved that, everything went smoothly. However, I'm not >> particularly strong in XML, and even with other documentation to aid me, I >> wasn't able to do it in time. >> > > Please write down specific problems and how you overcame them so that > others may learn or perhaps prevent these problems from happening again. > > The PHP manual and HOWTO would like to not require strong XML skills or > barely any XML knowledge at all, so that's something else that can be > discussed. How would strong XML knowledge help here? Was the template > missing something? Maybe we can be specific on what parts do not need to be > touched. > > An online tool would have made this a lot easier, since I would have just >> logged in, written the documentation, and been done. >> > > One note is now that you're setup you won't need to do it again, and given > that PhD is beta and still has kinks it should be easier in the future. The > HOWTO too. But yes I understand why an online tool is attractive but offline > tools are attractive too. > > Regards, > Philip > >
