Jascha Achterberg
1
APPEARANCES
1
PODCASTS
012
DEC 30
JAN 6
JAN 13
JAN 20
JAN 27
FEB 3
FEB 10
FEB 17
FEB 24
MAR 3
MAR 10
MAR 17
MAR 24
MAR 31
APR 7
APR 14
APR 21
APR 28
MAY 5
MAY 12
MAY 19
MAY 26
JUN 2
JUN 9
JUN 16
JUN 23
JUN 30
JUL 7
JUL 14
JUL 21
JUL 28
AUG 4
AUG 11
AUG 18
AUG 25
SEP 1
SEP 8
SEP 15
SEP 22
SEP 29
OCT 6
OCT 13
OCT 20
OCT 27
NOV 3
NOV 10
NOV 17
NOV 24
DEC 1
DEC 8
DEC 15
DEC 22
DEC 29
JAN 5
JAN 12
JAN 19
JAN 26
FEB 2
FEB 9
FEB 16
FEB 23
MAR 2
MAR 9
MAR 16
MAR 23
MAR 30
APR 6
APR 13
APR 20
APR 27
MAY 4
MAY 11
MAY 18
MAY 25
JUN 1
JUN 8
JUN 15
JUN 22
JUN 29
JUL 6
JUL 13
JUL 20
JUL 27
AUG 3
AUG 10
AUG 17
AUG 24
AUG 31
SEP 7
SEP 14
SEP 21
SEP 28
OCT 5
OCT 12
OCT 19
Oct 13, 2026
The Compute 100: Jascha Achterberg, Co-Founder & CTO, Callosum
29:59
30:16
30:23
30:33
Jascha AchterbergGUEST
What's the path of getting there? I mean, sometimes you sit down and you're like, I wish I knew, right? The matchmaking in the first instance is a data collection problem in the first instance.
Jascha AchterbergGUEST
How do you understand the chips? But also, how do you understand the workloads? How do you understand how they are brought together? So there's a bit of a discussion that we just had.
Jascha AchterbergGUEST
It's ultimately a large-scale testing exercise, but also how to keep the maximum experimental data, how to queue format, how to extrapolate from two different sets to a new workload.
Jascha AchterbergGUEST
So there's lots of just nearly kind of data science-like work on the back end, which is like the fundamental data you need to capture to do anything.
34 MINS LATER