Joe Armstrong Quotes
1950–2019 United States
Joseph Leslie Armstrong (27 December 1950 – 20 April 2019) was a computer scientist working in the area of fault-tolerant distributed systems.
- United States
- Computer scientists
Also known as: Joe Armstrong
Random Joe Armstrong quote
110 quotes
I got this Prolog system, and I thought, let's do a message passing object model there. There were an influence with CSP.
What's legacy code? That's dead programmers stuff, not only there are no comment in it, you can't ask people because they are dead. It written in languages that nobody understand, there is no specification and yet it works beautifully!
Four good tools to learn: Emacs, Bash, Make and Shell. You could use Vi, I am not religious here. Make is pretty damn good! I use Make for everything, that good!
Composing computation. Why do we do compose computation? Because We want to make reusable things out of small things. We take small things to make bigger things.
I was programming Prolog []... What happens when a Prolog program goes wrong? it says no. There "no" is not a very good error. Core damage is much more informative for no.
The inability to isolate software components from each other is the main reason why many popular programming languages cannot be used for making robust system software. (page 32)
If you do something and it fails you can do it again, it will work the second time. That's because quite often you are using something underneath where you've missed a message or messages are coming in wrong order.
The Middle man is the thing that imposed Erlang only in the Erlang world. If people try to talk to each other, the complexity of the program is O(N²). But, if we put middle men here, this turns the complexity to O(N).
Your first question must always be: what is the most difficult part of this problem that I am trying to solve and then try and solve that. If you can't solve the most difficult bit, give up! Seek advice, find somebody who can solve it!
The clarity of programming languages have several advantages over traditional languages. For example, programs in such languages are considerably shorter than the equivalent programs in imperative languages. They also encourage clear programming styles.