Quotes About Expectation

Man is the only trained animal who expects his reward before he does his trick.

What good is love if you never ask anything of it?

How do you achieve success? Well, for one thing, you don't define it before you achieve it.

An optimist is someone who figures that if it walks like a duck and quacks like a duck, it's the bluebird of happiness.

We find things where we look for them, which is why I never look for a golf ball out of bounds.

I've learned never to be surprised if what must inevitably happen happens right now.

I've observed that there are more lines formed than things worth waiting for.

It is easy to mistake being ready for a wedding with being ready for marriage.

It's curious the way we get nostalgic for some hoped-for thing that never happened, as if something that never happened were in the past.

Moque-toi d'une mauvaise réputation. Crains une bonne que tu ne pourrais pas soutenir.

Provoke the unexpected. Expect it.

Create expectations to fulfil them.

That's all we may expect of man, this side. The grave: his good is—knowing he is bad.

Cheer up!" said Mr. Sutton when he'd read the letter. "Kathy Alice may come to see you!" All the children groaned. "Earnestine wants to meet your Aunt Myrtle and Uncle Ross and Kathy Alice here on Thanksgiving Day." "Tell her we won't be home," said Ellen. "Where will we be?" asked Dewey. "Anywhere except here," said Ellen, "if they're coming to see us.

Suspense is worst than disappointment.

Many things happen between the cup and the lip.

All our geese are swans.

it's confusing to have a controller and a manager and a driver in the same code base. What is the essential difference between a DeviceManager and a Protocol-Controller? Why are both not controllers or both not managers? Are they both Drivers really? The name leads you to expect two objects that have very different type as well as having different classes. A consistent lexicon is a great boon to the programmers who must use your code.

Am I suggesting 100% test coverage? No, I'm not suggesting it. I'm demanding it. Every single line of code that you write should be tested. Period. Isn't that unrealistic? Of course not. You only write code because you expect it to get executed. If you expect it to get executed, you ought to know that it works. The only way to know this is to test it.

You know you are working on clean code when each routine turns out to be pretty much what you expected.

Ward's principle: "You know you are working on clean code when each routine turns out to be pretty much what you expected.

We also confuse trust with familiarity.

Turk had family in Austin, Texas. But they hadn't heard from him lately and wouldn't expect to.

They come to accept things that are made cheaply and quickly. The idea that they might have to expend much effort to get what they want has been eroded by the proliferation of devices that do so much of the work for them, fostering the idea that they deserve all of this—that it is their inherent right to have and to consume what they want.