Ro Khanna Quotes

Software Engineering might be science; but that's not what I do. I'm a hacker, not an engineer.

Indeed, the woes of Software Engineering are not due to lack of tools, or proper management, but largely due to lack of sufficient technical competence.

We shifted our philosophy from being a computer mapping group that would support planners to the idea of building actual software that would be well engineered. Because at that time, our software was not well-engineered at all; it was basically built with project funding and for project work, largely by ourselves.

First, I'd like to see the basic tools such as compilers, debuggers, profilers, database interfaces, GUI builders, CAD tools, and so forth fully support the ISO standard.

This will surprise some of your readers, but my primary interest is not with computer security. I am primarily interested in writing software that works as intended.

I have never written a line of commercial code in my life. Nor should I.

The most sought-after candidates in the world today by companies like mine are people who make computer software - there's a shortage of talent.

I know one business, and that's how to make software.

I felt there was a need for us to build a new programming language. I also had come to see that Microsoft functions best when it controls its own destiny.

I think it's a combination of technical and social factors that leads to all the defects in deployed software.

Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves.

I feel lucky because earlier in my career, I found what I liked to do; it's build software that you see your friends using on the street, and they like it.

Like any well designed software product, Windows is designed, developed and tested as an integrated whole.

The way to be successful in the software world is to come up with breakthrough software, and so whether it's Microsoft Office or Windows, its pushing that forward. New ideas, surprising the marketplace, so good engineering and good business are one in the same.

Software eventually and necessarily gained the same respect as any other discipline.

Java and C++ make you think that the new ideas are like the old ones. Java is the most distressing thing to hit computing since MS-DOS.

Anyone can squash a bug but all professors of this world couldn't build one.

I have this hope that there is a better way. Higher-level tools that actually let you see the structure of the software more clearly will be of tremendous value.

I'm really good at making software for publishing.

The process of software development doesn't feel any better than it did a generation ago.

There is a strong movement towards increased accountability for software developers and software development organizations.

Most of the effort in the software business goes into the maintenance of code that already exists.

If you know how to make software, then you can create big things.

When I worked at Microsoft, I got to go and visit a bunch of different companies. Probably a hundred different companies a year. You'd see all the different ways they'd work. The guys who did Ventura Publisher one day, and then United Airlines the next. You'd see the 12 guys in Texas doing Doom, and then you'd go see Aetna Life Insurance.

Yet, I am convinced that there is a need for high quality software, and the time will come when it will be recognized that it is worth investing effort in its development and in using a careful, structured approach based on safe, structured languages.