"The only thing that matters in software is the experience of the user." is going on the wall in the office. And I'm mailing one to Android development team.
That statement seems simple and correct at first, but the term "user" is not well defined. Even if there was only one user in the world, me, it still isn't well defined. The reason being that I can't tell you right now at this moment about all the possible use-cases I might have for some software in the future.
I think what this statement really means is that we all create software for the end user, but then get lost in all the theory and principles of software engineering that often drag out software projects and make them overly complex. The point at the end of the day is that "it's all about delivery" and we need to remember that without the customer/end user, we're just wasting everyones time moving bits and bytes around because we can.
That's where the YAGNI principle comes in. You cannot reason about use cases you don't know yet, so don't even try to predict what you might need until you have a clearer picture.
