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
Good programmers write code that humans can understand.
--Martin Fowler
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
Programming is the art of thinking really hard about how to avoid having to think really hard.
--unknown
A language that doesn't affect the way you think about programming is not worth knowing.
--Alan Perlis
First solve the problem. Then, write the code.
--Waseem Latif
College is a waystation - the last convenience store on the road to life-long responsibility.
--Dennis Miller
How do you expect to succeed if you do not know the rules?
--Anonymous
There is nothing good or bad about knowledge itself; morality lies in the application of knowledge.
--Jon Erickson
People who are really serious about software should make their own hardware
--Alan Kay
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
Object-oriented programming offers a sustainable way to write spaghetti code. It lets you accrete programs as a series of patches.
--Paul Graham
Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable code.
--Edsger W. Dijkstra
[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
What kind of programmer is so divorced from reality that she thinks she'll get complex software right the first time?
--James Alan Gardner