dybr

Ok, it's 20:22 here, and 2:22 PM over there, but nobody shows up in Slack, so I've just closed my work computer.

What else happened. 

I tried to dump a list of consumers from prod db. Did not work. Asked, how exactly I should do that? Ok, need a github token. Added it. Did not work. Asked again. Mike pointed to the same question, asked by Janet last week. There was a long thread, and I repeated the steps. Did not work. Asked Janet. She writes that she did not retry.

Eventually it turned out that we are now in another team, removed from the list of the previous team. And our new team is not listed at all for access in the database. They don't have time for us.

We also had a "sprint review" later today. I was too insolent and posted three "bad aspects". Like wtf our playbooks/instructions have the form of threads in slack. (Devon says: "because that's where the information is"). Why people do updates of the same bugs in the same project in parallel? (Devon says: "I was first"). Can we handle random context switches? Here everyone agreed.

I should not have. They don't pay me for my attempts of the process improvement.

OTOH, it's not my duty day; finished yesterday. We had about 6 OPS cases; I closed five, and one is... in discussion, is it our team's fault, is it PRISM team's fault? Who knows. The Culinary College girl thinks it's ours. Oh, ok. Give me a chance to investigate? We don't have time for that.

BTW, Devon added some logging to `consumers` project to investigate what's up. This logging caused errors in logs, so it was rolled back.

I guess it was NPE, when he was trying to log a phone number of an account which is null.

BTW, the problem is, I believe, this:

- you create an account
- the frontend requests the account info to show it
- the backend requests the account's phone number
- the "phone number service", not having the phone number (yet) in its db, reports: "Unknown user"
- the backend is in panic: user does not exist!
- it reports to frontend: "user does not exist"
- frontend shows the user a message: "failed to create an account"
- the user creates another account

(rinse, repeat)

OTOH, if I closed almost (or just) all the ops cases, what will the next engineer be doing, I wonder. Was not I a strike-breaker? No clue. I behaved like a young pioneer. Bad, bad. But well...