Top 1200 Software Engineering Quotes & Sayings - Page 3

Explore popular Software Engineering quotes.
Last updated on November 8, 2024.
There is one major problem with anti-virus software: It needs updating. Users cannot be relied upon to have even the anti-virus software in the first place, let alone be able or willing to pay for the updates.
The default movement on a software project should be in the direction of taking elements of the software away to make it simpler rather than adding elements to make it more complex.
If in my lifetime the problem of non-free software is solved, I could perhaps relax and write software again. But I might instead try to help deal with the world's larger problems. Standing up to an evil system is exhilarating, and now I have a taste for it.
My first exposure to sanitation issues occurred when I got admission into an engineering college. They probably didn't want to admit me and informed me that there was no ladies toilet in the college. I was adamant and pursued my studies in engineering in that very college.
Because software is all about scale. The larger you are, the more profitable you are. If we sell twice as much as software, it doesn't cost us twice as much to build that software. So the more customers you have, the more scale you have. The larger you are, the more profitable you are.
In 1986, Microsoft and Oracle went public within a day of each other, and I recall telling one of my colleagues that the software business will become big. So I started working with software companies in the mid-'80s and never turned back.
We're trying to make our software available to users in as economically efficient a way as possible. That means distributing the software directly to them; taking payment through Mastercard, Visa, Paypal, and other options; and not having a store take 30 percent.
Paying isn’t wrong, and being paid isn’t wrong. Trampling other people’s freedom and community is wrong, so the free software movement aims to put an end to it, at least in the area of software.
Energy Engineering started first in IIT Kharagpur in 1983 and mine was the third batch. It was definitely not a popular course. It was basically an amalgamation of nuclear, mechanical, chemical engineering, etc. But I don't think it was a big factor because if we look, most of them joined the IT sectors and not the energy sector.
Engineering is not a science. Science studies particular events to find general laws. Engineering design makes use of the laws to solve particular practical problems. In this it is more closely related to art or craft.
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.
I hated science in high school. Technology? Engineering? Math? Why would I ever need this? Little did I realize that music was also about science, technology, engineering and mathematics, all rolled into one.
Even in such technical lines as engineering, about 15% of one's financial success is due one's technical knowledge and about 85% is due to skill in human engineering, to personality and the ability to lead people.
Software is usually accompanied by documentation in the form of big fat scary manuals that nobody ever reads. In fact, for the past five years most of the manuals shipped with software products have actually been copies of Stephen King's The Stand with new covers pasted on.
One of the big changes at the heart of Web 2.0 is the shift from the creation of software artifacts, which is what the PC revolution was about, to the creation of software services. These are services that ultimately, if they are successful, will require competencies of operation, of scale, and the like.
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.
Both social engineering and technical attacks played a big part in what I was able to do. It was a hybrid. I used social engineering when it was appropriate, and exploited technical vulnerabilities when it was appropriate.
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better.
Software production is like any other production the preceded it, no raw materials are required, no time is required and no effort is required, you can make a million Copies of Software instantaneously for free and its very unique about that.
Colleges will try to get the good students. That's the way to go. When I chaired my department of Materials Engineering at the Technion in 1990, we started a program for which we set the bar very high. It was the highest at the Technion, above electrical engineering and medicine.
There's a tendency to make jazzy educational software that's very uniform and therefore just like school. I'd like to see a company develop software for rebellious kids who don't want to go to school.
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.
Some says that genetic engineering is within the scope of the God! Well, it was so, that area would have been encircled with the impassable high walls! Mankind cannot lose its time with this kind of religious craps! Genetic engineering is our garden!
Today many people are switching to free software for purely practical reasons. That is good, as far as it goes, but that isn't all we need to do! Attracting users to free software is not the whole job, just the first step.
I'm the founder of the McAfee Anti-Virus Software Company. Although I have had nothing to do with this company for over 15 years, I still get volumes of mail asking 'how do I uninstall this software'. I have no idea.
Scrivener is where I live. I'm planning the next novel, two screenplays and a couple of short stories with it and it's amazing how fluid the software makes the process. I genuinely think this is the biggest software advance for writers since the word processor.
Software suppliers are trying to make their software packages more 'user-friendly'... Their best approach so far has been to take all the old brochures and stamp the words 'user-friendly' on the cover.
TV and the press have always functioned according to the same sets of rules and technical standards. But the Internet is based on software. And anybody can write a new piece of software on the Internet that years later a billion people are using.
When I was at Tek, I was frustrated that computer hardware was being improved faster than computer software. I wanted to invent some software that was completely different, that would grow and change as it was used. That's how wiki came about.
One can expect the human race to continue attempting systems just within or just beyond our reach; and software systems are perhaps the most intricate and complex of man's handiworks. The management of this complex craft will demand our best use of new languages and systems, our best adaptation of proven engineering management methods, liberal doses of common sense, and a God-given humility to recognize our fallibility and limitations.
The complexity of software is an essential property, not an accidental one. Hence, descriptions of a software entity that abstract away its complexity often abstracts away its essence.
Poor management can increase software costs more rapidly than any other factor. Particularly on large projects, each of the following mismanagement actions has often been responsible for doubling software development costs.
I am so old, I entered engineering school with a slide rule. And I left engineering school with a calculator. I can still use a slide rule but it's not a skill you especially need anymore.
I would definitely like to work at Microsoft, since software development and exploring new technologies has always been my passion, and Microsoft is best when it comes to next-generation software technologies.
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.
You can have an Apple in the phone business, or a RIM, and they can do very well, but when 1.3 billion phones a year are all smart, the software that's gonna be most popular in those phones is gonna be software that's sold by somebody who doesn't make their own phones.
The essence of a software entity is a construct of interlocking concepts. I believe the hard part of building software to be the specification, design, and testing of this conceptual construct, not the labor of representing it and testing the fidelity of the representation.
Blockchain software companies may end up being amalgamated into existing software giants, at which point blockchain patents will just become part of the existing patent war.
There are a variety of techniques for breaking software down into pieces and making software development more efficient. Many of these techniques have been sort of... and everybody got excited about but very little benefit was actually derived once the thing was put into practice.
I've actually started a number of businesses in my career. So I'm 28 currently, but when I was about 16, I started building Websites, and that's how I put myself through school. I went to Duke with a degree in electrical engineering, computer science, computer engineering, and then to Princeton.
Microsoft Research has a thing called the Sense Cam that, as you walk around, it's taking photos all the time. And the software will filter and find the ones that are interesting without having to think, 'Let's get out the camera and get that shot.' You just have that, and software helps you pick what you want.
I'm the kid that tried to take Latin in school because I felt if I could understand the root of everything, then I could understand why it worked. That was what took me into engineering. And the reason I stayed is, engineering teaches you to solve problems. It teaches you to think.
Microsoft knows that reliable software is not cost effective. According to studies, 90% to 95% of all bugs are harmless. They're never discovered by users, and they don't affect performance. It's much cheaper to release buggy software and fix the 5% to 10% of bugs people find and complain about.
While I was at Cornell in engineering, I was an engineering co-op student, and that turned out to be very valuable because we'd go out every other term to work in industry and have that close association with industry.
If anything, there's a reverse Moore's Law observable in software: As processors become faster and memory becomes cheaper, software becomes correspondingly slower and more bloated, using up all available resources.
As the commercial confrontation between [free software] and software-that's-a-product becomes more fierce, patent law's going to be the terrain on which a big piece of the war's going to be fought. Waterloo is here somewhere.
When I got started in my own engineering course, my interest in physics and maths was very high. After all, engineering is all about applied maths and physics. If I were to learn anything further in physics or mathematics, it simply was not there.
Indian software engineers are the best in the world; even in Silicon Valley, the best software engineers are Indians. — © Masayoshi Son
Indian software engineers are the best in the world; even in Silicon Valley, the best software engineers are Indians.
On the back end, software programming tools and Internet-based services make it easy to launch new global software-powered start-ups in many industries - without the need to invest in new infrastructure and train new employees.
I had originally wanted to be a lawyer. Even when I went to college and majored in engineering, I still thought I'd get a law degree. Then I started taking electrical engineering classes where I saw some of the innovation happening around computers and solid-state technology in the mid '80s.
The Ninth Circuit Court of Appeals agreed, and software has been treated as a form of speech ever since. So if software code is speech, Apple says the First Amendment also means the government can't tell Apple what to say.
Engineers do engineering, i.e. they build bridges. So engineering needs engineers. The economy does NOT need economists. Economists do not make economy, but they try it and that is why we have so much problems with some financial models.
Great software has seemingly limitless potential to solve human problems - and it can spread around the world in the blink of an eye. Malicious code moves just as quickly, and when software is created for the wrong reason, it has a huge and growing capacity to harm millions of people.
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.
Unless there is one master gene for yield, which I'm guessing there is not, engineering for yield will be very complex. It may happen eventually, but through the coming decades, we must assume that gene engineering will not be the answer to the world's food problems.
I think Nintendo is fortunate, having been in this business for over 30 years, to really understand the dynamics and recognize that it's software that drives hardware, and it's new, unique, compelling experiences within software that make it stand out.
Another trick in software is to avoid rewriting the software by using a piece that's already been written, so called component approach which the latest term for this in the most advanced form is what's called Object Oriented Programming.
I started in engineering, where I think I could have happily remained and, who knows, made a bundle as a civil engineer or mechanical engineer. But more of my friends happened to be majoring in physics than engineering, so I switched over. No more compelling reason than that.
Early on, when software was developed by computer scientists, just people working with computers, people passed around software because that was how you got computers to do things.
Our ancient yogis and sages were not just medical healers, but systems scientists and systems engineers, who saw the body and the universe as an interconnected engineering system, a system of systems that are governed by fundamental engineering systems principles.
This site uses cookies to ensure you get the best experience. More info...
Got it!