John Carmack Quotes

Real programmers can write assembly code in any language.

To write a kernel without a data structure and have it be as consistent and graceful as UNIX would have been a much, much harder challenge.

Low-level programming is good for the programmer's soul.

And, I think that is actually appropriate because I'm really not the world's best programmer, I think it's a good thing that I'm not touching the code.

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

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

I designed and developed an unbelievable number of applications early in my life.

So Chuck and I looked at that and we hacked on em for a while, and eventually we ripped the stuff out of em and put some of it into what was then called en, which was really ed with some em features.

Any good software engineer will tell you that a compiler and an interpreter are interchangeable.

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 great coder. But I am not pushing that so much anymore because there are thousands of great coders.

It's strategic for us - lots of people will develop applications in .NET.

I basically wrote the code and the specs and documentation for how the client and server talked to each other.

After graduating in 1973 I went into the programming field.

Program construction consists of a sequence of refinement steps.

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.

We try to continually push ourselves to do more and more, not just on the hardware side but also in terms of developers' tools so they can take advantage of the hardware that's there, in the best way.

I enjoy evangelizing Java. In my heart of hearts, I'm an engineer, and what makes me happy is building something that works and having someone use it. That's cool.

It's something special being able to build a program up.

As software engineers trained to turn ambiguity into absolutes and fuzzy requirements into ones and zeros, we had a 'eureka' moment when we realized that our training had broader, real-world applications.

People sometimes ask me what I did when I was hired at HAL. The answer is that I was a programmer. And an engineer. And a designer. And I marketed our games. I also ordered food. And I helped clean up. And, it was all great fun.

The single most important thing for any processor is getting adoption by software developers.

You see people doing Java-based internal applications all over the place, regular desktop applications that are sort of front-ends to the things in the back, or standalone things.

While most game developers are focused entirely on what they're shipping in a year or two, a technology developer like Epic has to look much further out and plan many years ahead.

For every job you require a kind of mindset. To be a teacher one should be knowledgeable. To be a software engineer you should know computer data system analysis, computer language etc. So, my mindset is not aligned with politics.