But there's a difference between simplifying and changing. This is a bit of a skill in itself: presenting simplified versions of information without misleadin

But there's a difference between simplifying and changing. This is a bit of a skill in itself: presenting simplified versions of information without misleading the learner. When learning, I don't appreciate reading a description of something, thinking about it, generating my own conclusions, then finally reading forward to find I had been misled not by my own fault but by faulty explanations. As an example, a book I read on SQL was narrated from the point of view of an employee at a startup and stated that indexes on views were efficient, but then eventually backtracked on that statement, saying that this is only true for materialized views.