Quotes About Software

Software-industry battles are fought by highly paid and out-of-shape nerds furiously pounding computer keyboards while they guzzle diet Coke. The stakes aren't very dramatic. Life? Liberty? The pursuit of happiness? Nope, it's about stock options.

Android's user-space is so different from stock Linux, you can easily say that Android is not in any way a Linux system, except for the kernel.

I think my software is going to become so ubiquitous, so essential, that if it stops working, there will be riots.

Suprisingly, one of the most complex pieces of code is the code to determine where a note is in the staff. Finale stores notes as relative scale positions in the current key.

Microsoft was not a mysterious, strange entity. You put your PC on and there's an ad for them.

It's strategic for us - lots of people will develop applications in .NET.

We're entering a new world in which data may be more important than software.

We built something, we get feedback, we try to figure out what make sense out of the suggestions, and then we do something about it and then we listen some more." That is a great description of how Internet software is typically built today, with what is now called a "build-measure-learn" cycle, in which the users of a minimally useful service teach its creators what they want from them.

what we believe to be the core competencies of Web 2.0 companies: Services, not packaged software, with cost-effective scalability Control over unique, hard-to-recreate data

revolution be limited to PC applications. Salesforce.com demonstrates how the web can be used to deliver software as a service, in enterprise scale applications such

Ramit builds checklists for as many business processes as possible, which he organizes using software called Basecamp. Google "entrepreneurial bus count" for a good article on why checklists can save your startup.

That's not a bug. It's a feature!

I have come to learn that part of the business strategy is to solve the simplest, easiest, and most valuable problem. And actually, in fact, part of doing strategy is to solve the easiest problem, so part of the reason why you work on software and bits is that atoms [physical products] are actually very difficult.

Yo uso VeraCrypt (ver

NetLimiter con Windows

para detectar y decidir si permitir o bloquear este tipo de conexión por parte de una aplicación concreta,

The statistics about reading are particularly discouraging: The average software developer, for example, doesn't own a single book on the subject of his or her work, and hasn't ever read one.

While this [10 to 1] productivity differential among programmers is understandable, there is also a 10 to 1 difference in productivity among software organizations

The average software developer, for example, doesn't own a single book on the subject of his or her work, and hasn't ever read one.

That makes good sense if you're an Indy 500 racer. But you aren't. (Sorry.) You're a software project manager. The same mind-set on a software project is a disaster.

Both VisiCalc and MultiPlan were available when the IBM PC shipped in October 1981. 1-2-3 didn't hit the market until January 1983.

One IT group adopted the "sterile cockpit" concept to advance an important software project.

Carpo explains what this represents: "Algorithms, software, hardware and digital manufacturing tools are the new standards of product design.… Unlike a mechanical imprint, which physically stamps the same form onto objects, an algorithmic imprint lets outward and visible forms change and morph from one object to the next.

The Standish Group's 2002 "Chaos" study of software project success and failure rates states that in a typical software system, 45% of features are never used. Only 7% of features are always used, and another 13% are used often.