Chris Hansen Quotes

It is time we stop believing in the GOD WENTRUST, andnstart believing in the God that trust us.

He apparently sees us the same way. He’s not just an artist, of course, like Chris. He’s also a Father. Good dads are like that. You may be a drop-out, underachiever, whatever, and a good dad will still love you, but he’ll push you to change, because he sees a different you ahead. He sees a finished product, an adult who uses his or her talents and is a blessing to others. He sees something wonderful.

Breathe me in, for I am the wind - Chris Mendoza, Breathe Me, Austin Hansen

Breathe me in, For I am the wind - Chris Mendoza (Breathe Me)

Seibel: What's your desert-island list of books for programmers? Peyton Jones: Well, you should definitely read Jon Bentley's Programming Pearls. Speaking of pearls, Brian Hayes has a lovely chapter in this book Beautiful Code entitled, “Writing Programs for ‘The Book’” where I think by “The Book” he means a program that will have eternal beauty. You've got two points and a third point and you have to find which side of the line between the two points this third point is on. And several solutions don't work very well. But then there's a very simple solution that just does it right. Of course, Don Knuth's series, The Art of Computer Programming. I don't think it was ever anything I read straight through; it's not that kind of book. I certainly referred to it a lot at one stage. Chris Okasaki's book Purely Functional Data Structures. Fantastic. It's like Arthur Norman's course only spread out to a whole book. It's about how you can do queues and lookup tables and heaps without any side effects but with good complexity bounds. Really, really nice book. Everyone should read this. It's also quite short and accessible as well. Structure and Interpretation of Computer Programs. Abelson and Sussman. I loved that. And Compiling with Continuations, Andrew Appel's book about how to compile a functional program using continuation passing style. Also wonderful. Books that were important to me but I haven't read for a long time: A Discipline of Programming by Dijkstra. Dijkstra is very careful about writing beautiful programs. These ones are completely imperative but they have the “Hoare property” of rather than having no obvious bugs they obviously have no bugs. And it gives very nice, elegant reasoning to reason about it. That's a book that introduced me for the first time to reasoning about programs in a pretty watertight way. Another book that at the time made a huge impression on me was Per Brinch Hansen's book about writing concurrent operating systems. I read it lots of times.

On the topic of winning, and the lottery: You can't lose if you don't play, therefore not losing , is winning!