Tyrone Krieger
I've been writing code since I was 11. Nearly two decades later, I'm still baffled by the fact that most developers spend only 32% of their time actually coding.
My professors used to say this was just the way things were. But instead of accepting it, I decided to push back. One step at a time.
Why? Because we can.
As developers, we build the tools that move entire industries forward. So why not turn that same energy inward and improve our own?
Still think it's impossible? Have a look: https://CodeGlass.io
What I Love:
• Diving deep into complex codebases
• Sharing developer knowledge
• Building powerful tools (like CodeGlass)
• Exploring superconductors and the Meissner effect (hoverboards when?)
• I Like Trains
• Lizard Doggo
Let’s grab a digital drink: Tyrone@CodeGlass.io or Discord #aBrokenDonut
Session
Seven years ago, I hit my first “bug from hell”, the kind of issue that would be trivial to solve if we had something like an airplane’s flight data recorder, but for software. A system that records every change in execution so you can replay and analyze issues down to the exact line of code.
That idea grew into what we now call CodeGlass: technology that provides time-travel analysis and deep runtime insights, already helping enterprises tackle elusive bugs, performance bottlenecks, and memory issues across multiple programming languages.
Last year, members of the Julia community asked us: can we bring this to Julia?
In this talk, I’ll explain how the technology works, where it can help Julia developers today, especially in high-performance computing, scientific research, and reliability, and what it could enable next for the Julia community, like trace-based debugging. Most importantly, we want to connect with researchers, engineers, developers, and organizations who can benefit from this now, and collaborate with us to shape the future of CodeGlass in the Julia ecosystem.