I really don't want to be pessimistic nor do I want to put somebody off,
but I have to mention that, whoever wants to take the job, has to be sure, what he has to do.
It's not only a taking part (but of course it's a great chance to learn Ruby),
but also a lot of giving, meaning that it can be alot more work than you may think in the first
moment.
Oh yeah, it's a lot of work. I'm sure you can search the archives and find me saying that, a lot.
Luckily, it is rewarding work. Well, at least for those who value the same things I do.
(Why I'm posting this as a reply to James and not to Thomas is that James shouldn't be too
much like "It's a great job" without mentioning the possible problems.
The time commitment is the biggest problem. I have it down to about four or five hours of my time a week now (depending on how popular the quiz was) and I have a hard time imagining someone doing it in less time.
Well, unless you want to ditch the summary.
I've considered that. It's hard to know how much the summary adds. I don't know if I write about the right stuff or show the right code. I'm sure I don't do all of that all the time.
The discussion for the good problems is usually very good. I bet reading the emails is at least as helpful as reading my summaries. That's how I decide what to write about anyway.
That might be one option to reduce the time commitment.
However, I hope you don't see this in any offending way.
No offense taken.
I'm new to this quiz and I really like it, so I just want the best for it :))
Me too on all accounts except for being new to the quiz.
James Edward Gray II
···
On Jan 29, 2008, at 4:01 PM, Dominik Honnef wrote: