Re:Object Oriented Programming Oversold (2001)
by woah on Friday December 04, 2015 @10:45AM
(#10676904)
Let's imagine that YOU were doing the rewrite, and for all the best reasons. Totally different situation. Would you write your code to continue saving some bizarre unnecessary data in the database, or would you get the job done with a sensible scheme? As for the other comment, were they supposed to continue renting out completely unused facilities in case someone came along who thought the old system was better?
Re:Object Oriented Programming Oversold (2001)
by jacquesm on Friday December 04, 2015 @12:56PM
(#10677851)
There are proper ways of doing this: you run the old system in parallel with the new system and you outfit both systems in such a way that all writes are done on both systems. That way the DBs stay in sync.
So you won't have to 'write your code to continue saving some bizarre unnecessary data in the database' and you can have your 'sensible scheme'. It just takes a little bit more care and planning.
> As for the other comment, were they supposed to continue renting out completely unused facilities in case someone came along who thought the old system was better?
They ended up renting a good part of those facilities anyway, the problem was not the money but the fact that certain comms lines had been torn up.
Playing cowboy with critical company data is not a winning strategy.
Just to provide another example, "write a stub prototype of the new system, discover $CRAPPY_ORM in my new hotness language doesn't like a couple of the database constructs, migrate production database to work better with the prototype, new system fails to generate some data the old system needed (history, audit logs, tons of options here)". Back migration now effectively impossible.