General Question re Query Errors

[karafecho]

@stevencox : I can either post errors the minute they arise for developers to explore, as I've done today, or I can spend just a little bit of time investigating the issue(s). I'd prefer the latter, but the discussion during Monday's meeting leads me to believe that you'd prefer the former. I can see the value in both approaches: one demonstrates a typical user's interaction (and frustration) with the app; the other allows a team member (and user) to better understand the general design, strengths, and limitations of the tool, especially as it matures and moves from prototype to production. Please advise.

[stevencox]

Ya, this is a great point. I'm hoping we can have our cake and eat it too:

I'd like to involve @mmersmann in the first part. Namely, share with @mmersmann right away then further explore and share findings. So as our product manager, I'd like her to collect stories and a sense of user frustrations.

Then she can

• Triage issues so we don't write duplicates
• Route issues so we assign things to the best suited developer.
• Look for patterns of the kinds of things we see to improve overall quality

What do you think?