C3Subtitles: 31c3: Why are computers so @#!*, and what can we do about it?
back

Why are computers so @#!*, and what can we do about it?

If you suspend your transcription on amara.org, please add a timestamp below to indicate how far you progressed! This will help others to resume your work!

Please do not press “publish” on amara.org to save your progress, use “save draft” instead. Only press “publish” when you're done with quality control.

Video duration
00:59:14
Language
English
Abstract
Computers have become ubiquitous and essential, but they remain massively error-prone and insecure - as if we were back in the early days of the industrial revolution, with steam engines exploding left, right, and centre. Why is this, and can we do better? Is it science, engineering, craft, or bodgery?

I'll talk about attempts to mix better engineering methods from a cocktail of empiricism and logic, with examples from network protocols, programming languages, and (especially) the concurrency behaviour of programming languages and multiprocessors (from the ARMs in your phone to x86 and IBM Power servers), together with dealings with architects and language standards groups.

For more details of the underlying research and the many people who have contributed, see: http://www.cl.cam.ac.uk/~pes20/

Talk ID
6574
Event:
31c3
Day
4
Room
Saal 1
Start
12:45 p.m.
Duration
01:00:00
Track
Science
Type of
lecture
Speaker
Peter Sewell

Talk & Speaker speed statistics

Very rough underestimation:
142.6 wpm
794.0 spm
144.2 wpm
801.3 spm
100.0% Checking done100.0%
0.0% Syncing done0.0%
0.0% Transcribing done0.0%
0.0% Nothing done yet0.0%

Talk & Speaker speed statistics with word clouds

Whole talk:
142.6 wpm
794.0 spm
Peter Sewell:
144.2 wpm
801.3 spm