- Developer at TVBeat
- PhD student at Jožef Stefan International Postgraduate School.
- Solving hard problems with data
Why this topic?
What happens to things that you are working on?
Failure to learn
Own your core
part of your system that you spend the most time on
We're not here to just learn.
Summing up - learning
- Quick iterations
- Own critical parts
Failures in operation
how does your system respond to load?
is there a cliff?
- Keep the system in the happy zone
- Make the system stable by design
Things will happen
hardware failure is a part of normal operation
- distributed computational systems
- distributed databases
Summing up - systems
- Distributed systems
- The babysitting trap
Failure to communicate
if you use this interface, an implementation can solve your problem
One magic button
feature nominally exist, but with ridiculous performance envelope
Summing up - communication & abstraction
- Fake simplicity
- Leaky abstractions
- Lying abstractions
Failure to observe
what axis is your problem hard at?
- Failures to learn
- Failures to operate
- Failures to abstract
- Failures to observe