Subscription pricing
Michele: Support In my professional experience, it’s usually not a good idea for a company to overhaul its databases. ███ ███████ ██████ ██████ ███ ████████ ███████████ █████ ███ ████ ███ █████ ███████ ████ ██████ ███████████ █ ████████ ████████ █████ █████ ██████ ███████████
███████ ███ ███ ████████ ███ ██████ ██████ ██ █ ███████ ██ ██████ ███ ████████ █████████ ███ ████ ██████ ███ █ ███████ ███████████ █ ████████ ████████ ██ ██ ██ ███ ███ ██████
Speaker 1 Summary
Michele concludes that people should think twice before proceeding with a database overhaul. This is because the benefits of an overhaul rarely outweigh the problems of an overhaul.
Speaker 2 Summary
Alvaro asserts that problems of an overhaul are always caused by failing to recode the database properly. Thus, he concludes that a company considering an overhaul should do the overhaul correctly.
Objective
We’re looking for a point of disagreement. A point of disagreement is difficult to predict up front. They seem to disagree over how to approach a database overhaul. Michele recommends strongly considering whether an overhaul is the right decision. Alvaro recommends doing an overhaul correctly, but doesn’t express as much caution about doing the overhaul as Michele does.
20.
Michele and Alvaro disagree with ████ █████ █████ █████ ███ ██ ███ ██████████
a
why companies should ████████ ███████████ █████ █████████
b
whether the problems ███████████ ██████ █ ████████ ████████ ████ ████████ ███ ███████
c
which kinds of ████████ █████████ ████ ████ ████████ ████ ███ █████████ ██ ███ ███████
d
what a company ██████ ██ ████ ███████████ █ ████████ ████████
e
when professional experience ██ ████████ ██ █████████ ██████ █ ████████