Quotes About Coding

A programming language is for thinking about programs, not for expressing programs you've already thought of. It should be a pencil, not a pen.

Write the tests first, or second, or third. But write the darned tests.

That voice you hear in your head, the one whispering that you need to add some comments, may just be your program crying out to be rewritten.

Let's face it: Despite shelves full of books on software architecture, enough UML diagrams to fill an art museum, and design meetings that seem to last longer than the pyramids, building software mostly comes down to writing one method after another.

By learning to create technology girls learn to speak up...

Controlling complexity is the essence of computer programming.

We all rely on technology to communicate, to survive, to do our banking, to shop, to get informed, but none of us knows how to read and write the code.

Learn. Ceaselessly. Learn to code, to write persuasively, to understand new technologies, to bring out the best in your team, to find underused resources and to spot patterns.

Software always remain softly for End users! But sometimes hardly to developers!

You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time.

If you want more effective programmers, you will discover that they should not waste their time debugging, they should not introduce the bugs to start with.

All great programmers learn the same way. They poke the box. They code something and see what the computer does. They change it and see what the computer does. They repeat the process again and again until they figure out how the box works.

It's actually very hard to find an area of the economy that doesn't fundamentally change in the measure that we are able to read and write life code.

When it comes to software, I much prefer free software, because I have very seldom seen a program that has worked well enough for my needs, and having sources available can be a life-saver.

First, solve the problem. Then write the code.

He coded like some people danced, glitter-eyed concentration and confident grace and never a hesitation.

I wrote code that merely did what it was supposed to do. Simon's solutions were rapid and weird—convoluted, sometimes in a pointless way, often in a way that looked pointless until you saw how elegant it was.

Problem-solving, inventing, hacking and coding is more of an adrenaline rush of endorphins rather than a feeling.

I think the best developers can learn any language; if they are a good developer, they can learn whatever. But the raw talent, the ability to learn it and do it and demonstrate the ability is helpful.

Grant, if we edited Fortran, I assume that you'd put a column thing in there.

I learned HTML in high school and then graduated to CSS. It's a great way to exercise my mind. But it's frustrating as hell.

So why do we sometimes appear in practice prototypical in our classifications, even if in principal we are Aristotelian? For two main reasons: because each classification system is tied to a particular set of coding practices; and because classification systems in general...reflect the conflicting, contradictory motives of the sociotechnical situations that gave rise to them.

The acknowledged legislators of the world take the world as given. They dislike mysteries, for mysteries cannot be coded, or legislated, and wonder cannot be made into law. And so these legislators police the accepted frontiers of things.

'Programming' is a four-letter word.