Okay, let's ask me.

Easy to Reproduce Crashes: I can easily fix those in less than an hour.

Random Crashes: How random? How often? How catastrophic? Depending on your answers and assuming it's a software issue, the time-to-fix usually ranges from 5 1/2 hours to ∞ - 1. But this topic is too big for this discussion.

Have you ever been part of a successful software project? Good developers don't freak out like you're suggesting. In your context, absolutes like "never end well" are FUD. WEEKS is a long time, and it doesn't frighten a good development group if they're in bug-fixing mode. Sh*tty management is what usually frightens a good development group.

If it's your code, bug fixing shouldn't be difficult. Good design is where all the real work is, right? So, children, the moral of the story is: Worry less about bugs and worry more about design, then things will always (okay, mostly) end well.

Back to the topic:

Nokia needs to find out what happened, having a high profile shoot-from-the-hip blogger as an extended part of your QA department doesn't seem like a good thing. That's what we're here for. And my prototype should be arriving any day now...