Schema changes are not uncommon during development. Often, a field will move from one table to another. Being a good developer has little or nothing to do with that. Not getting bogged down with a tool that cannot handle those changes, that is a mark of a good developer.

In "theory" the database design is supposed to be frozen. In "reality", that is rarely the case.

As for how you split the use between RV's and SPT, if you use RV's for updating data, why don't you use RV's for queries? I could see why one would use a RV for queries and SPT for updates, since SPT gives you access to SP's.