2026-08-14 –, Room 6
Julia was created by greedy programmers who wanted it all. What if we are equally greedy about tooling? This session invites discussion on missing capabilities in Julia’s development tools. What tools or workflows still fall short? Where should future efforts be made to improve productivity and insight?
Why they created Julia: "In short, because we are greedy."
The goal of this bird of a feather is to explore concrete gaps and pain points across Julia’s tooling such as debugging, performance analysis, compilation visibility, and workflows.
Topics we hope to talk about include:
What workflows feel harder than they should?
Where do current tools fall short?
What functionalities would significantly improve productivity, confidence in correctness and performance?
Which tooling issues become most visible in larger or production systems?
Where do current debugging workflows fail?
The aim is to better understand community priorities and to connect contributors that are greedy in advancing Julia’s development experience.
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?
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
Software Architect in ASML working on Julia algorithms in the near real time system.
GitHub