top of page
"But despite the universality of URLs, we often forget that they're not just a handy way to address network resources. They're also valuable communication tools."
Standard
Customized
Exlpore more Communication quotes

"Listening is more important than solutioning."

"What advantage has the person who will not listen over the one who cannot hear?"

"Language is a ladder that always falls short of reality."

"There's a lot of difference between listening and hearing."

"Know the other person's viewpoint first and then talk. To Talk after comparing it or mixing it with our viewpoint is an offence."

"If you speak, that is rain; if you speak too much, that is flood!"

"Talk to strangers politely... Every friend you have now was once a stranger, although not every stranger becomes a friend."

"Not being heard is no reason for silence."

"Don't use your words to criticize, condemn, or complain; us your words to appreciate, inspire, and empower."

"The thing is that it could never again feel natural to talk to her."
Explore more quotes by Jesse James Garrett

"If you need to take a step back from day-to-day operations and plot out the long-term direction of your user experience strategy, consultants can give you a perspective you can't get on your own."

"Ajax isn't a technology. It's really several technologies, each flourishing in its own right, coming together in powerful new ways."

"I'm not sure that you can say definitively that some roles are better filled by consultants, but I would say that some projects are better handled by consultants."

"The main benefit of the book for the more experienced practitioners is as an evangelical tool. The book will give you some ways of expressing the value and importance of your work that you may not have had before."

"Well, the whole story is in the book, but the short answer is that I was the first information architect in an organization that was traditionally design-oriented, and I felt I needed a tool to help me gain the trust and support of my colleagues."

"Building technical systems involves a lot of hard work and specialized knowledge: languages and protocols, coding and debugging, testing and refactoring."

"But the best teams I've encountered have one important thing in common: their team structure and processes cover a full range of distinct competencies necessary for success."

"As much as we may want to withdraw into a world of pure problem solving, we have to acknowledge that the most successful architectures are the ones you can actually convince someone to implement."
bottom of page