A collection of 123 inspiring quotes about programmer from various authors and sources.
It is not the language that makes programs appear simple. It is the programmer that make the language appear simple!
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.
One difference between a smart programmer and a professional programmer is that the professional understands that clarity is king. Professionals use their powers for good and write code that others can understand.
At forty, I was too old to work as a programmer myself anymore; writing code is a young person's job.
A real programmer reads much more than he writes.
The lyrical programmer even writes the code in the form of poetry!
A programmer who thinks about his convenience, and not the convenience of the user who will use the software product is bad. Without knowing how, they start from scratch, but look at the present through the prism of past experience.
It always helps to be a good programmer. It is important to like computers and to be able to think of things people would want to do with their computers.
Common programmer thought pattern: there are only three numbers: 0, 1, and n.
When you have a programmer-founded company it often gets really techy, if you have a producer or a business-person, it all really sets the flavor of the company, just the priorities and the way you deal with everything.
The effective exploitation of his powers of abstraction must be regarded as one of the most vital activities of a competent programmer.
Finding a programmer to work with if you don't already know one will be a challenge. Merely judging if a programmer is exceptional vs. competent will be very hard if you are not one yourself. When you do find someone, work together informally for a while to test your compatibility.
The intellectual property situation is bad and getting worse. To be a programmer, it requires that you understand as much law as you do technology.
The choice of approaches could be made the responsibility of the programmer.
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say \'programmer\' or something like that.
...when fits of creativity run strong, more than one programmer or writer has been known to abandon the desktop for the more spacious floor.
To be a programmer is to develop a carefully managed relationship with error. There's no getting around it. You either make your accomodations with failure, or the work will become intolerable.
Programming is how we talk to the machines that are increasingly woven into our lives. If you aren't a programmer, you're like one of the unlettered people of the Middle Ages who were told what to think by the literate priesthood. We had a Renaissance when more people could read and write; we'll have another one when everyone programs.
Most programming languages contain good parts and bad parts. I discovered that I could be better programmer by using only the good parts and avoiding the bad parts.
Observe that for the programmer, as for the chef, the urgency of the patron may govern the scheduled completion of the task, but it cannot govern the actual completion. An omelette, promised in two minutes, may appear to be progressing nicely. But when it has not set in two minutes, the customer has two choices - wait or eat it raw. Software customers have had the same choices.
My message to the serious programmer is this: spend a part of your working day examining and refining your own methods. Even though programmers are always struggling to meet some future or past deadline, methodological abstraction is a wise long term investment.
I have never seen an experienced programmer who routinely made detailed flow charts before beginning to write programs.
I'm still a really shitty programmer, but I know enough to hack a prototype together.
I used to want to be a computer programmer when I was younger. We got an Apple II Plus when I was, like, 11 and I wrote programs and BASIC on that, like I think a lot of people did, but I have no idea how to program in the current languages at all.
It would've been amazing [to work as programmer]. You're good at numbers, you're good with people, you like to wear shorts in the summertime.
It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.
The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea.
The mark of a mature programmer is willingness to throw out code you spent time on when you realize it's pointless
A good programmer is someone who always looks both ways before crossing a one-way street.
I'm not a real programmer. I throw together things until it works then I move on. The real programmers will say Yeah it works but you're leaking memory everywhere. Perhaps we should fix that. I'll just restart Apache every 10 requests.