How shit works: the CPU

Building software gives you the warm and fuzzy illusion of total control; this is the result of layers upon layers of successful abstractions hiding immense complexity. But when they inevitably leak, that’s when knowing what’s under the hood pays off.

In this talk we’ll peel a few layers and take at our “car engine”, the CPU. All applications, even in high-level Scala, end up executing machine code instructions on a processor; that is why the JVM has a memory model, why memory layout still matters at scale, and we’ll show why you’re usually free to ignore these and go about your job.

Session length

40 minutes

Language of the presentation

English

Target audience

Intermediate: Requires a basic knowledge of the area

Who is your session intended to

All "non-system-language" developers that want to know a bit more about how their code actually gets executed.

Speaker

Tomer Gabel (Wix)