1. Be careful making nouns such as ” spread consumption”, you need to write “the consumption of spreads”.
2. You don’t need to put the data in the overview for this graph because you will give it in the body paragraphs.
3. Be careful when you are writing about one particular spread, for example butter, and you write “the amount of spreads consumed “. This actually refers to all spreads, not just butter. So, you need to write “The amount of butter which was consumed…” or “the amount of this spread which was consumed…”
4. It’s quite long and may be difficult to write in only 20 mins. Don’t include information which is not important. For example, the consumption of butter in 1996 – this date isn’t really important to highlight and could be missed completely.
5. Don’t confuse the reader. I know that low fat etc spread declined in the final years but to write that it became less popular is confusing because during that time it was the most popular spread of all of them.
Again, wrong question. A better attitude is to assert that we have to be able to understand the state of our programs. We can then ask: How do we design data structures that can be visualized? Can we invent data structures that are intended to be visualized? How do we move towards a culture where only visually-understandable data is considered sound? Where opaque data is regarded in the same way that "goto" is today?* * Forward reference: Some work that I've done in automatic visualization of ad-hoc data structures will be published later this year, in collaboration with Viewpoints Research.