Vivek Wadhwa Quotes

I knew tech was going to be increasingly important in my lifetime, so I focused on it early.

The most disastrous thing that you can ever learn is your first programming language.

Design and programming are human activities; forget that and all is lost.

I am not versed in production software. I have basic knowledge, but it ends there.

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.

I've been on the Web from the beginning of the Web. The good part about writing about technology is that you never run out of ideas, because it's changing so fast. The bad part is that it's changing so fast that there's a million new products and ideas every day and every week.

Our society expects that everyone should learn to write, even though very few become professional writers. Similarly, I think that everyone should learn how to program, even though very few will become professional programmers.

I'm just an observer of Java, and where Microsoft wants to go with C# is too early to tell.

I had to actually purchase a book to learn the API and write the client. It was pretty frustrating trying to learn the API and develop a product quickly.

The world is changing, and I believe that, if I want to stay employed as a programmer, I'm going to have to change with it.

My list of basic tools is a partial answer to the question about what has changed: Over the past few years, large numbers of programmers have come to depend on elaborate tools to interface code with systems facilities.

I'm thinking of going to programming school. Learn how to sit down at any computer and learn to do anything on it. That's all I have left and have interest in.

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.

In my daily work, I work on very large, complex, distributed systems built out of many Python modules and packages. The focus is very similar to what you find, for example, in Java and, in general, in systems programming languages.

I'm a victim of Developaralysis: the crippling sense that the software industry is evolving so fast that no one person can possibly keep up.

The computing field is always in need of new cliches.

Computer programming is pretty much guaranteed income. I'm good at it, and I like it.

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.

I don't program or code or anything like that.

We don't know how to actually code, but I wish that I did. It's so much harder than anyone could possibly imagine - it's like learning German.

Whether you're looking at manufacturing and the use of robotics or the knowledge industries, they need computer programmers.

We just think it's important that everybody have some technical training and background. Even though not everybody is coding but even our deals team and our designers all have GitHub accounts and they go into the code base.

One of the first major programming projects that I worked on when I was growing up in Ireland, back just coding by myself, was a programming language. Then I spent a bunch of time working on a new web framer. Just back-end things to make it easier to go in and build things on top of, do other development.

Before coming to Congress, I worked as a computer programmer and a systems analyst.

Everyone on the founding team ought to invest the time in a coding bootcamp.