Quotes About Software

any function that contains a yield statement is turned into a generator function.

When you say 'I wrote a program that crashed Windows,' people just stare at you blankly and say 'Hey, I got those with the system, for free.'

Windows 8 is key to the future, the Surface computer.

Mult-Tenancyi is really the future of our industry.

Our goal in making these changes is to enable Microsoft to achieve greater agility in managing the incredible growth ahead and executing our software-based services strategy.

I believe consistency and orthogonality are tools of design, not the primary goal in design.

The vision is really that in the information age the microprocessor-based machine, the PC, along with great software, can become sort of the ultimate tool dealing with not just text, but numbers and pictures, and eventually, even difficult things lik.

Reading computer manuals without the hardware is as frustrating as reading sex manuals without the software.

este país el sector que más creció en los últimos veinte años no es la tecnología, no es el software; es la desigualdad, que creció más que en ningún otro momento de nuestra historia.

Repetition is the root of all software evil

Code that communicates its purpose is very important. I often refactor just when I'm reading some code. That way as I gain understanding about the program, I embed that understanding into the code for later so I don't forget what I learned.

So, my overall advice on performance with refactoring is: Most of the time you should ignore it. If your refactoring introduces performance slow-downs, finish refactoring first and do performance tuning afterwards.

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.

A heuristic we follow is that whenever we feel the need to comment something, we write a method instead.

When you find you have to add a feature to a program, and the program's code is not structured in a convenient way to add the feature, first refactor the program to make it easy to add the feature, then add the feature.

In almost all cases, I'm opposed to setting aside time for refactoring. In my view refactoring is not an activity you set aside time to do. Refactoring is something you do all the time in little bursts.

I've found that refactoring helps me write fast software. It slows the software in the short term while I'm refactoring, but it makes the software easier to tune during optimization. I end up well ahead.

Parallel inheritance hierarchies is really a special case of shotgun surgery. In this case, every time you make a subclass of one class, you also have to make a subclass of another.

First Law of Distributed Object Design: Don't distribute your objects!

Notice how I'm playing the part of an enemy to code. I'm actively thinking about how I can break it. I find that state of mind to be both productive and fun. It indulges the mean-spirited part of my psyche. When you are doing tests, don't forget to check that expected errors occur properly.

With 70 percent accuracy, my source tells me, software can assess how people feel based on the way they type, and the number of typos they make. With 79 percent precision, software can determine a user's credit rating based on the degree to which they write in ALL CAPS.

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

The biggest cause of failure in software-intensive systems is not technical failure; it's building the wrong thing.

Suppose a developer has a conversation with a customer about details of a feature. The conversation should not be considered complete until it is expressed as a customer test.