Top 178 Programmer Quotes & Sayings - Page 3

We would write our songs, then we'd have a programmer come in and add, for lack of a better term, bloops and bleeps on top of everything. Of course, the funny thing is that a lot of the modern-day dance music people are super-influenced by the '70s and '80s stuff that we already love. So it was a natural fit for No Doubt.

It is, therefore, possible to extend a partially specified interpretation to a complete interpretation, without loss of verifiability... This fact offers the possibility of automatic verification of programs, the programmer merely tagging entrances and one edge in each innermost loop.

If you're a doctor, or a scientist, or a computer programmer, it shouldn't matter whether you come from Nigeria, or Norway, or any other country on this earth. Today though we have a system that rewards ties of blood, ties of kin, ties of clan. That's one of the most un-American immigration systems I can imagine.

UNIX has a philosophy, it has 25 years of history behind it, and most importantly, it has a clean core. It strives for something - some kind of beauty. And that's really what struck me as a programmer. Operating systems that normal home users are used to, such as DOS and Windows, didn't have any way of life. Nobody tried to design Windows - it just grew in random directions without any kind of thought behind it. [...] I don't think Microsoft is evil in itself; I just think that they make really crappy operating systems.

I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important. Bad programmers worry about the code. Good programmers worry about data structures and their relationships.

If you, or any public-spirited programmer, wanted to figure out what the software on your machine is really doing, tough luck. It's illegal to reverse engineer the source code of commercial software to find out how it works.

My high school, the Illinois Mathematics and Science Academy, showed me that anything is possible and that you're never too young to think big. At 15, I worked as a computer programmer at the Fermi National Accelerator Laboratory, or Fermilab. After graduating, I attended Stanford for a degree in economics and computer science.

Lisp is worth learning for the profound enlightenment experience you will have when you finally get it; that experience will make you a better programmer for the rest of your days, even if you never actually use Lisp itself a lot.

The complexity of C++ (even more complexity has been added in the new C++), and the resulting impact on productivity, is no longer justified. All the hoops that the C++ programmer had to jump through in order to use a C-compatible language make no sense anymore - they're just a waste of time and effort. Now, Go makes much more sense for the class of problems that C++ was originally intended to solve.

The act of focusing our mightiest intellectual resources on the elusive goal of goto-less programs has helped us get our minds off all those really tough and possibly unresolvable problems and issues with which today's professional programmer would otherwise have to grapple.

I actually started off majoring in computer science, but I knew right away I wasn't going to stay with it. It was because I had this one professor who was the loneliest, saddest man I've ever known. He was a programmer, and I knew that I didn't want to do whatever he did.

After moving to Los Angeles in the early '90s, I started looking into "music for picture" more seriously and in broader scope. My collaboration as a programmer and arranger with Graeme Revell exposed me for the first time to the full spectrum of film music, including the hectic demands of orchestral scoring and the power politics surrounding the finalization of any score for a major motion picture in Hollywood.

The funny thing was, with IT, I was never really a tech type of person: I was better with people, good at dealing with people. I had technical experience; I knew the nitty gritty. I could never be a programmer or anything, but I knew my way around.

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.

The corollary of constant change is ignorance. This is not often talked about: we computer experts barely know what we're doing. We're good at fussing and figuring out. We function well in a sea of unknowns. Our experience has only prepared us to deal with confusion. A programmer who denies this is probably lying, or else is densely unaware of himself.

My dad grew up as a computer programmer, so he always had random computer software, and I started opening up editing software at age 12 and figuring out how to build websites.

Some folks actually talk a whole lot more than me, so I'm grateful for the people like Cliff Bleszinski. He talks about our games, and Mark Rein talks about our business strategy. I'm the shy programmer myself.

Evolution, dismissed as a sloppy programmer, has seen fit to create us as a wild amalgam of everything that came before us: except for the realm of insects, the whole history of life on earth is inscribed within our bodies.

I am a programmer. If I write code, I don't evaluate the results by what I hope the code will be. I evaluate it by what happens when I compile it. I evaluate it by results.

The best way to prepare [to be a programmer] is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating systems.

God, our genes, our environment, or some stupid programmer keying in code at an ancient terminal - there's no way free will can ever exist if we as individuals are the result of some external cause.

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.

When I got started, I was a sideshow. At my first Consumer Electronics Show, in 1977 in Chicago, people came from all over the floor to see the 'lady programmer.' They had me dressed in a turquoise lab coat with my name embroidered on the pocket.

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.

I'm a designer, but I rely on programmers to bring my ideas to life. By learning to code myself, I think I can make things easier for all of us. Similarly, I want to be able to build things on my own without having to bother a programmer.

Don't blame me for the fact that competent programming, as I view it as an intellectual possibility, will be too difficult for the average programmer, you must not fall into the trap of rejecting a surgical technique because it is beyond the capabilities of the barber in his shop around the corner.

I actually started off majoring in computer science, but I knew right away I wasn't going to stay with it. It was because I had this one professor who was the loneliest, saddest man I've ever known. He was a programmer, and I knew that I didn't want to do whatever he did. So after that, I switched to Communications.

The truth is I'm not actually an expert programmer! I really don't consider myself to be an expert at anything. For me, it's more about having a well-rounded and broad horizon. I think that's where a lot of the more interesting things come from - mashing up completely disparate aspects of life to create something new and original.

When you think about it, there's no way to input things into a computer. It's all... the holes only go out, right? Like you can plug a keyboard or a mouse in but that's a trick because the computer thinks the inputs are outputs. That's a programmer trick, basically magic. The key to the future is to make holes that go in too.

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 programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures.

With the exceptional talent that is Guy Sigsworth as producer and collaborator, we have recorded a collection of original songs that sees me moving away from a generic line up and back into the world of a programmer. Born of reconstructed improvisation I like to think of it as Prog-Pop, but I also like to think of big dogs as small horses. So don’t hang on to that thought long. Unless, of course, you think it astute of me in which case I am right

Like the famous mad philosopher said, when you stare into the void, the void stares also; but if you cast into the void, you get a type conversion error. (Which just goes to show Nietzsche wasn't a C++ programmer.)

In this respect a program is like a poem: you cannot write a poem without writing it. Yet people talk about programming as if it were a production process and measure "programmer productivity" in terms of "number of lines of code produced". In so doing they book that number on the wrong side of the ledger: we should always refer to "the number of lines of code spent".

The psychological profiling [of a programmer] is mostly the ability to shift levels of abstraction, from low level to high level. To see something in the small and to see something in the large.

I went to Drexel University, majored in computer science. Drexel has a great program - they call it co-op - but its, like, mandatory to graduate to do internships. I loved it because it helped me figure out very quickly that I didn't really want to be a programmer.

The error which underlies the very existence of this debate is that there is some kind of perfect Platonic form of the computer language, which some real languages reflect more perfectly than others. Plato was brilliant for his time but reality is not expressable in terms of arbitrary visions of perfection, and furthermore, one programmer's ideal is often another's hell.

When I was a kid, I really wanted to be a writer and an artist when I grew up. So in college, I was an English major, and then I became a fine artist. But when I arrived in San Francisco in 1995, I figured I could leverage my artistic skills by becoming a Web designer and programmer.

And no, I'm not a walking C++ dictionary. I do not keep every technical detail in my head at all times. If I did that, I would be a much poorer programmer. I do keep the main points straight in my head most of the time, and I do know where to find the details when I need them.

I didn't realize how good I was with technology until I met my parents... my dad told me "You're good; you should be a computer programmer." I said, "You're bad... you should be a caveman."

Not having a schedule is OK if it's your PhD and you plan to spend 14 years on the thing, or if you're a programmer working on the next Duke Nukem and we'll ship when we're good and ready. But for almost any kind of real business, you just have to know how long things are going to take, because developing a product costs money.

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.

The computer programmer is a creator of universes for which he alone is the lawgiver. No playwright, no stage director, no emperor, however powerful, has ever exercised such absolute authority to arrange a stage or field of battle and to command such unswervingly dutiful actors or troops.

The best programs are written so that computing machines can perform them quickly and so that human beings can understand them clearly. A programmer is ideally an essayist who works with traditional aesthetic and literary forms as well as mathematical concepts, to communicate the way that an algorithm works and to convince a reader that the results will be correct.

Computer programming is an art, because it applies accumulated knowledge to the world, because it requires skill and ingenuity, and especially because it produces objects of beauty. A programmer who subconsciously views himself as an artist will enjoy what he does and will do it better.

I've been a DJ, janitor, ditch digger, waitress, computer instructor, programmer, mechanic, web developer, clerk, manager, marketing director, tour guide and dorm manager, among other things.

The government does things like insisting that all encryption programs should have a back door. But surely no one is stupid enough to think the terrorists are going to use encryption systems with a back door. The terrorists will simply hire a programmer to come up with a secure encryption scheme.

The difference between the best worker on computer hardware and the average may be 2 to 1, if you're lucky. With automobiles, maybe 2 to 1. But in software, it's at least 25 to 1. The difference between the average programmer and a great one is at least that. The secret of my success is that we have gone to exceptional lengths to hire the best people in the world. And when you're in a field where the dynamic range is 25 to 1, boy, does it pay off.

The term architecture is used here to describe the attributes of a system as seen by the programmer, i.e., the conceptual structure and functional behavior, as distinct from the organization of the data flow and controls, the logical design, and the physical implementation. i. Additional details concerning the architecture

Since I have always preferred making plans to executing them, I have gravitated towards situations and systems that, once set into operation, could create music with little or no intervention on my part. That is to say, I tend towards the roles of planner and programmer, and then become an audience to the results

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.

In the '80s, society created a caricature of what a hacker or a programmer looked like: a guy wearing a hoodie, drinking energy drinks, sitting in a basement somewhere coding. Today, programmers look like the men we see in the show 'Silicon Valley' on HBO. If you look at the message girls are getting, it's saying, 'This is not for you.'

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.

Space camp was actually, like, the best summer of my life. It was amazing. But I thought I wanted to be a computer programmer, and among computer science folks, Turing is this object of cult-like fascination.

All the things I used to count on to get my music out there - record companies, they're all gone. And radio stations, they're gone - they're completely controlled by the government. If they're not controlled by the government, they're controlled by a programmer who's controlled by the government. Mainstream radio is suspect. You can't trust it.

I don't like the idea that Facebook controls how people express themselves and changes it periodically according to whatever algorithms they use to figure out what they should do or the whim of some programmer or some CEO. That bothers me a great deal.

I created DonorsChoose by putting pencil to paper - literally - and sketching out each screen of the web site and how it would work. Then I paid a programmer from Poland $1,500 to turn my sketches and common-sense rules into a functioning website.

It's a very complex network of genes making products which go into the nucleus and turn on other genes. And, in fact, you find a continuing network of processes going on in a very complex way by which genes are subject to these continual adjustments, as you might say - the computer programmer deciding which genes ultimately will work.