A Quote by Wietse Venema

However, writing software without defects is not sufficient. In my experience, it is at least as difficult to write software that is safe - that is, software that behaves reasonably under adverse conditions.
I'm not of the opinion that all software will be open source software. There is certain software that fits a niche that is only useful to a particular company or person: for example, the software immediately behind a web site's user interface. But the vast majority of software is actually pretty generic.
The software patent problem is not limited to Mono. Software patents affect everyone writing software today.
In the free/libre software movement, we develop software that respects users' freedom, so we and you can escape from software that doesn't.
Software patents are dangerous to software developers because they impose monopolies on software ideas.
Why shouldn't we give our teachers a license to obtain software, all software, any software, for nothing? Does anyone demand a licensing fee, each time a child is taught the alphabet?
When you develop software, the people who write the software, the developers are the key group but the testers also play an absolutely critical role. They're the ones who ah, write thousands and thousands of examples and make sure that it's going to work on all the different computers and printers and the different amounts of memory or networks that the software'11 be used in. That's a very hard job.
I named my software 'EMAIL,' (a term never used before in the English language), and I even received the first U.S. Copyright for that software, officially recognizing me as The Inventor of Email, at a time when Copyright was the only way to recognize software inventions, since the U.S. Supreme Court was not recognizing software patents.
With software products, it is usual to find that the software has major `bugs' and does not work reliably for some users... The lay public, familiar with only a few incidents of software failure, may regard them as exceptions caused by exceptionally inept programmers. Those of us who are software professionals know better; the most competent programmers in the world cannot avoid such problems.
Although the most advanced software innovation may take place in big cities with research universities, there is a lot of work concerning the application of software to business processes and the administration and maintenance of software systems that can be done remotely.
The challenge with Postfix, or with any piece of software, is to update software without introducing problems.
There's a fundamental problem with how the software business does things. We're asking people who are masters of hard-edged technology to design the soft, human side of software as well. As a result, they make products that are really cool - if you happen to be a software engineer.
I started a software company with a couple other folks. It went public. We made plenty of money. And I thought it was this incredible mission, but in fact, we sold software to Haliburton; we sold software to Frito-Lay and Pepsi and all these companies that didn't necessarily do good things.
...One of the most important lessons, perhaps, is the fact that SOFTWARE IS HARD. From now on I shall have significantly greater respect for every successful software tool that I encounter. During the past decade I was surprised to learn that the writing of programs for TeX and Metafont proved to be much more difficult than all the other things I had done (like proving theorems or writing books). The creation of good software demand a significiantly higher standard of accuracy than those other things do, and it requires a longer attention span than other intellectual tasks.
The QSM Software Almanac is an invaluable resource. It establishes a norm for software projects, including best of class, worst of class and averages. In addition, it profiles the state of the art of software construction and enhancement. I wish I'd had this wonderful reference book years ago.
My parents had a software company making children's software for the Apple II+, Commodore 64 and Acorn computers. They hired these teenagers to program the software, and these guys were true hackers, trying to get more colors and sound and animation out of those computers.
High-quality software is not expensive. High-quality software is faster and cheaper to build and maintain than low-quality software, from initial development all the way through total cost of ownership.
This site uses cookies to ensure you get the best experience. More info...
Got it!