Competitive/Collaborative Programming Class

ICPC Computer Programming Contest Prep

Problem Solving in Computer Science

Fall 2022 -- CSC 2700 Section 01 (1216 Patrick Taylor, 6:00 PM - 7:50 PM)



Class Home




Know the rules well, so you can break them effectively
--Dalai Lama XIV
First solve the problem. Then, write the code.
--Waseem Latif
There ain't no rules around here. We are trying to accomplish something.
--Thomas Edison
The personal computer isn't "personal" because it's small and portable and yours to own. It's "personal" because you pour yourself into it - your thoughts, your programming.
--Audrey Watters
Walking on water and developing software from a specification are easy if both are frozen.
--Edward V. Berard
Happiness should be a function without any parameters.
--Pranshu Midha
There is nothing good or bad about knowledge itself; morality lies in the application of knowledge.
--Jon Erickson
Delivering good software today is often better than perfect software tomorrow, so finish things and ship.
--David Thomas
The three principal virtues of a programmer are Laziness, Impatience, and Hubris. See the Camel Book for why.
--perldoc perl
Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable code.
--Edsger W. Dijkstra
What is a university/college when the students lose interest?
--Isaac Traxler
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
--Nartin Fowler
Programming isn't about what you know; it's about what you can figure out.
--Chris Pine
A university is what a college becomes when the faculty loses interest in students.
--John Ciardi
The issue of finding the best possible answer or achieving maximum efficiency usually arises in industry only after serious performance or legal troubles.
--Steven S. Skiena
Good programmers write code that humans can understand.
--Martin Fowler
How do you expect to succeed if you do not know the rules?
--Anonymous
[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