Competitive/Collaborative Programming Class

ICPC Computer Programming Contest Prep

Problem Solving in Computer Science

Spring 2025 -- CSC 2700 Section 01
1212 Patrick Taylor, 6:30 PM - 8:20 PM



Class Home




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
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
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
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live
--John Woods
Twenty hours at the keyboard can save you two hours of planning.
--Isaac Traxler
So if an algorithm is an idealized recipe, a program is the detailed set of instructions for a cooking robot preparing a month of meals for an army while under enemy attack
--Kernighan Brian
A language that doesn't affect the way you think about programming is not worth knowing.
--Alan Perlis
'Martyrdom' is the only way a person can become famous without ability.
--George Bernard Shaw
There is nothing good or bad about knowledge itself; morality lies in the application of knowledge.
--Jon Erickson
...I’m not saying simple code takes less time to write. You’d think it would since you end up with less total code, but a good solution isn’t an accretion of code, it’s a distillation of it.
--Robert Nystrom
Delivering good software today is often better than perfect software tomorrow, so finish things and ship.
--David Thomas
First solve the problem. Then, write the code.
--Waseem Latif
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.
It goes against the grain of modern education to teach children to program. What fun is there in making plans, acquiring discipline in organizing thoughts, devoting attention to detail and learning to be self-critical?
--Alan J. Perlis
I'm a programmer. I like programming. And the best way I've found to have a positive impact on code is to write it.
--Robert C. Martin
A language that doesn't affect the way you think about programming is not worth knowing.
--Unix Fortune
What is a university/college when the students lose interest?
--Isaac Traxler
If the steps become to big, they become walls...
--Herb Sutter
Some of the best programming is done on paper, really. Putting it into the computer is just a minor detail.
--Max Kanat-Alexander
The really good programmers spend a lot of time programming. I haven’t seen very good programmers who don’t spend a lot of time programming. If I don’t program for two or three days, I need to do it. And you get better at it—you get quicker at it. The side effect of writing all this other stuff is that when you get to doing ordinary problems, you can do them very quickly.
--Joe Armstrong
The big optimizations come from refining the high-level design, not the individual routines.
--Steve McConnell