Competitive/Collaborative Programming Class

A language that doesn't affect the way you think about programming is not worth knowing.
--Unix Fortune
The most important property of a program is whether it accomplishes the intention of its user.
--C.A.R. Hoare
Object-oriented programming offers a sustainable way to write spaghetti code. It lets you accrete programs as a series of patches.
--Paul Graham
First solve the problem. Then, write the code.
--Waseem Latif
How do you expect to succeed if you do not know the rules?
--Anonymous
Not only is this incomprehensible, but the ink is ugly and the paper is from the wrong kind of tree.
--Professor W.
The real nightmare, worse than the one in which the Big Machine wants to kill you, is the one in which it sees you as irrelevant, or not even as a discrete thing to know.
--Benjamin H Bratton
People who are really serious about software should make their own hardware
--Alan Kay
One knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?
--Brian Kernighan
Perl – The only language that looks the same before and after RSA encryption.
--Keith Bostic
Simple things should be simple, complex things should be possible.
--Alan Kay
Einstein repeatedly argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer.
--Frederick P. Brooks Jr.
I'm not a great programmer; I'm just a good programmer with great habits.
--Kent Beck
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
--perldoc perl
Managers of programming projects aren’t always aware that certain programming issues are matters of religion. If you’re a manager and you try to require compliance with certain programming practices, you’re inviting your programmers’ ire. Here’s a list of religious issues:
■ Programming language
■ Indentation style
■ Placing of braces
■ Choice of IDE
■ Commenting style
■ Efficiency vs. readability tradeoffs
■ Choice of methodology—for example, Scrum vs. Extreme Programming vs. evolutionary delivery ■ Programming utilities
■ Naming conventions
■ Use of gotos
■ Use of global variables
■ Measurements, especially productivity measures such as lines of code per day
--Steve McConnell
You are not reading this book because a teacher assigned it to you, you are reading it because you have a desire to learn, and wanting to learn is the biggest advantage you can have.
--Cory Althoff