The Do's and Don'ts of Error Handling • Joe Armstrong • GOTO 2018
Vložit
- čas přidán 7. 06. 2024
- This presentation was recorded at GOTO Chicago 2018. #gotocon #gotochgo
gotochgo.com
Joe Armstrong - Principal Inventor of the Erlang Programming Language
ABSTRACT
Handling errors in programs is tricky.
We want to write systems that work reasonable well even if there are errors in the code. This is possible, and the results have been used in production systems for many years.
This talk outlines the do's and don'ts of error handling. Things you should do if you want to write fault tolerant code, and things you should not do.
I will argue that making fault-tolerant and scalable systems is possible if you [...]
Download slides and read the full abstract here:
gotochgo.com/2018/sessions/352
/ gotochgo
/ gotoconference
gotocon.com
#ErrorHandling #Erlang #FaultTolerance
Looking for a unique learning experience?
Attend the next GOTO Conference near you! Get your ticket at gotocon.com
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
czcams.com/users/GotoConf... - Věda a technologie
RIP, Joe Armstrong; I learned about you too late, but will certainly study your work.
"Kubernetes--"
Joe: 'Who? Who's that?'
LOL
What a fantastic mind.
Sad to hear about your parting, Joe.
The world was better with you here.
Esdras Mayrink oh no! I am so sad to hear this news. The world is darker without him, surely. Rest in peace, Joe.
RIP Joe Armstrong your work made significant impact on software industry
Wrap your main/entry point in a try-catch and pretend like nothing bad is happening.
Rip Joe!
Amazing talk, a shame the sound is so bad...
the emphasis on "messaging" in OOP, makes it seem like there's a lot more inherent similarity between FP and fundamental OOP
Korede Aderele; I believe that’s because almost everyone misapprehends the historical essence of OOP as described by Alan Kay.
OOP is about messaging between objects, not about instantiating Classes.
Fwiw, OOP doesn’t prescribe encapsulating state. That’s just how most people do it.
Smalltalk actually did Erlang style message passing. (Joe says I was wrong.)
16:51 Does anyone know what happened to the Bluetail Mail Robustifier?
If Joe isn’t among your heroes then you’re still a junior dev.
Joseph Leslie Armstrong (27 December 1950 - 20 April 2019) was a computer scientist working in the area of fault-tolerant distributed systems. He is best known as one of the co-designers of the Erlang programming language.
Died: 20 April 2019 (aged 68) :/
if the concepts he is talking about here are foreign for you, then you are a failed developer, enjoy your salary and don't make the community a toxic place.
@@D4no00 that's to say nothing of experience .-.
Requescat in pace
'The type system doesn't tell you that "open a file, close a file, read the file" is incorrect'.... well, a good type system has a different type for open-file and non-open-file.
Type systems can't prevent people from being stupid. If you are trying to reduce programming to the art of hiring people who can't program as much as "Hello World!" to reduce hourly wages, then you are in for a bad surprise.
What if Michael Palin was a computer scientist.
I call silent and deadly errors "ninja errors" 😀
"You can program in Rust and things like that or whatever and maybe you can prove it to be correct" and then get hit by lightning =)
The word "do's" is not correct. If it was, why isn't its counterpart written as "don't's"? The answer is that an apostrophe is not punctuation to denote plurality.
Concurrency is the execution of independently executable tasks. It doesn't mean they all are executing at once...
Christopher Stamp a fact not lost on Mr. Armstrong. Was your comment a shallow criticism, or did you have a deeper observation to make?
If you want to get pedantic even if you neglect the fact that the model and runtime he's promoting satisfy both properties because concurrent tasks are performed on multiple cores.
Even if he's using a single threaded event loop on a runtime with a GIL because he's running the code on multiple machines it is still both concurrent and parallel.
Honestly in general when it comes to nerds the ones who are super invested in pedantry and jargon are full of shit or are just OCD and hard to work with.
Interesting but too abstract.
You can read more detail in Joe's dissertation "Making reliable distributed systems in the presence of software errors".
Because your thinking is, as of yet, insufficiently abstract to derive value from it. Best wishes for the future!
@@JeremyAndersonBoise I looked up pompous in the dictionary and it linked me to your comment.
@@jaythomas3180 Jeremy is pompous but correct
What a nice person.
The talk was delightful, albeit useless.
ImaginaryNumb3r why though ?