Competitive/Collaborative Programming Class

Delivering good software today is often better than perfect software tomorrow, so finish things and ship.
--David Thomas
[On identifying talented programmers] It’s just enthusiasm. You ask them what’s the most interesting program they worked on. And then you get them to describe it and its algorithms and what’s going on. If they can’t withstand my questioning on their program, then they’re not good. I’m asking them to describe something they’ve done that they’ve spent blood on. I’ve never met anybody who really did spend blood on something who wasn’t eager to describe what they’ve done and how they did it and why. I let them pick the subject. I don’t pick the subject, so I’m the amateur and they’re the professional in this subject. If they can’t stand an amateur asking them questions about their profession, then they don’t belong.
--Ken Thompson
'Martyrdom' is the only way a person can become famous without ability.
--George Bernard Shaw
Think twice, code once.
--Waseem Latif
A language that doesn't affect the way you think about programming is not worth knowing.
--Unix Fortune
Programming isn't about what you know; it's about what you can figure out.
--Chris Pine
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
What is a university/college when the students lose interest?
--Isaac Traxler
When in doubt, do something.
--Harry Chapin