A quote, often attributed Albert Einstein, comes to mind:
Make everything as simple as possible, but not simpler.
When you go overboard in trimming things down, it can make the code more difficult to read. As "easy/hard to read" can be a very subjective term, I'll explain exactly what I mean by this: a measure of the degree of difficulty that a skilled developer will have in determining "what does this code do?" by just looking at the source, without the assistance of specialized tools.
Languages like Java and Pascal are infamous for their verbosity. People often point to certain syntactical elements and derisively say that "they're just there to make the compiler's job easier." This is more or less true, except for the "just" part. The more explicit information there is, the easier the code is to read and understand, not only by a compiler but also by a human being.
If I say
var x = 2 + 2;, it's immediately obvious that
x is supposed to be an integer. But if I say
var foo = value.Response;, it's a whole lot less clear what
foo represents or what its properties and capabilities are. Even if the compiler can easily infer it, it puts a lot more cognitive effort on a person.
Remember that programs must be written for people to read, and only incidentally for machines to execute. (Ironically, this quote comes from a textbook devoted to a language infamous for being extremely difficult to read!) It's a good idea to remove things that are redundant, but don't take away code that makes it easier for your fellow human beings to figure out what's going on, even if it's not strictly necessary for the program being written.