I really don’t want to be right.

If I’m right, it means that we have at least 2 weeks worth of work that will need to be redone.

I really don’t want to be right, but I’m afraid I might be.

And what really sucks is that I vocalized my concerns about this issue when it first came up (2 weeks ago). So if I’m right, I’ll at least have an “I told you so” – but I’d really rather not, in this case.

gah.

also: I need to get back into the habit of posting here. (how long have I been saying that now?)

returns to lurking in the corner and hoping that he’s wrong.

Published by

Robert

Robert Belknap has been writing online sporadically since 2001. See the colophon for more details.

4 thoughts on “I really don’t want to be right.”

  1. Yes and no. I was right about the problem, but wrong about the scope. There were fewer entries in the database that were affected by the problem than I was afraid of. We had to re-do some work, but not everything for the project for previous 2 weeks. And there’s another upside – better documentation has been created for our processes in the lab to avoid similar problems in the future.

Leave a Reply

Your email address will not be published.