A Quote by Jon Evans

I am very happily employed as a full-time software engineer; I travel a lot, and I write books along with this here weekly TechCrunch column; and I still find the time to work on my own software side projects.
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.
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.
Yes, we are a producer of cameras, but we understand that at the end of the day, you have to make photos in software. A lot of companies focus on the camera side, and a lot are on the software side. There's a chasm between the two.
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?
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.
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.
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.
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 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.
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.
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.
We flew down weekly to meet with IBM, but they thought the way to measure software was the amount of code we wrote, when really the better the software, the fewer lines of code.
My best decision was to choose to go to Wall Street over law. I learned a lot and focused on the expanding software industry at a time when the independent software industry was just beginning.
I have mostly software synthesizers and software drum machines. I'm very lazy. I don't really like to plug in a lot of equipment and external boxes and everything.
Oracle is my second job ever that did not involve waitressing. But I still have my waitress apron just in case this does not work out. It's just that I fell in love with software when I was programming in college. When I was an investment banker, there were mostly mainframe companies and very few software ones.
The software patent problem is not limited to Mono. Software patents affect everyone writing software today.
This site uses cookies to ensure you get the best experience. More info...
Got it!