I’ve been a developer for several years and throughout my career I’ve learned how to write clean, well-tested code. I’ve also discovered that sometimes writing the most beautiful poetic code can be horrendously slow when working with lots of data. What I really want is fast code. I know the topic of performance can seem intimidating at first - don’t worry I am by no means an expert in performance either!

My talk isn't about compiler optimisation, multithreading, profilers, buffer management or cyclomatic complexity. In fact, what I’ve found is that optimising code doesn’t need to be more complicated than good old fashioned refactoring. Using a real problem that I encountered, my talk will take you through how I made slow code fast. Oh, and bunnies. Lots and lots of bunnies.

How buggy / insecure are new gem releases? Analysis of 10 years of Rubysec data and 50,000 dependency updates PRs.

A lot of real problems can be described by a collection of mathematical equations. From sudoku to dependency resolution to verifying correctness of processors and cryptographic protocols. Z3 is a very powerful solver for such problems, and an elegant Ruby DSL is a great interface to it.