Michele: In my professional experience, it’s usually not a good idea for a company to overhaul its databases.
Michele's Claims
1. It's usually not a good idea for a company to overhaul its databases.
2. The rewards rarely exceed the problems experienced along the way.
3. People considering a database overhaul should think twice before proceeding.
Alvaro's Responses
1. Did Alvaro argue that ... usually it is a good idea for a company to overhaul its databases?
No, not really. It doesn't seem like Alvaro weighs in on the usually modifier that dictates the truth value of this claim. He doesn't seem to address whether it's a good idea for companies to overhaul databases in most cases.
2. Did Alvaro argue that ... The rewards frequently exceed the problems experienced along the way?
Not really. There isn't any discussion of rewards outweighing problem.
3. Did Alvaro argue that ... People considering a database overhaul should not think twice?
Yes, kind of. He's definitely countering Michele's advice in her final claim. For her, the best advice for a company considering a database overhaul is to "think twice", which is an expression that means "you probably shouldn't do it".
If we say, , that's another way of saying, .
So Michele is saying companies should probably avoid overhauling their database, whereas Alvaro is saying
Goal
The disconnect seemed to be concentrated around the idea of generic advice about overhauling databases.
Michele: Alvaro: "It's fine, just do the job right"