Content
We probably want to link to their pages: https://pretalx.com/juliacon-2026/talk/AMFLYU/
Other recent work might want to link to i.e epinowcast?
No, the point was an LLM wrote the outline of me and I wanted that to be clear.
It is not really part of what these talks are about, cut that. There is less LLM emphasis here than we had in how I LLM, less self referential, but we do discuss as in the original prompt.
We already have a robot opener so we do not need the closing one at the end at all I think.
The following was drafted by @seabbs-bot who has a very suspiciously high opinion of me so take it with a pinch of salt.
Link to seabbs-bot GitHub profile.
I think this one is on Friday? [the composable talk, 2026-08-14 16:45-17:00]
We need the QRs in the second slide of each talk with bullets outlining what we talk about. We do not need the QRs on the home page for each project as they are already on it. Not all the text was generated by LLM, remove that. The point we were trying to make was the bio was LLM generated. Get agents to scan the projects and talks for LLM-isms we removed or asked to remove in our other presentations (get them to look at the git commit history) and clean them up. “Something something is the point” or “sentence, some random point” are both common patterns. Make sure slides are visually interesting. The primarycensored talk needs a second slide on right truncation after double interval censoring.
Also the composability paper has weird EpiNow2 justification vibes in the slides we have here that were not in the original. Also we now have ComposableTuringIDModels which is the prototype we talk about in those slides. It is not linked from the project page or otherwise mentioned clearly but should be.
Yes, everything in the 40 minute talk is canonical.
The slides honestly kind of suck. In general the content is not my style. How I LLM is not a good reference as it was all bots; the other talks are a better reference. The new diagrams are high level and not very good, and there is lots of text all over the place. Slides have become very cluttered.
For the delays talk we need what an epidemiological delay is, biases, double censoring, truncation, with a diagram as we had in the recent serial interval talk. Then the software for this. primarycensored, what is it. Then we need partial pooling, so how do we extend it, brms, okay, epidist, but. Then what about the population level, nowcasting, epinowcast. Then what about in Julia, CensoredDistributions.
For the ecosystem talk it is over indexed on the R stuff. It should instead be that we want to build this composable thing, then what we wanted: something like epinowcast, something like SciML, something like the Turing community. But that approach was hard, and multiple approaches are possible so I want to leave space for that. Something like rOpenSci for epi, ideally.
We can still have what we needed to make it work for fitting. Stan is what is used in epidist and epinowcast.
“Stan is the through line” is the kind of classic LLM language that I do not use and edit out.
brms is a nice way to metaprogram Stan but is limited in terms of being extensible. In epidist we try hard to extend it but it took a lot of effort. If Julia had something like brms, which a few people, maybe here, have been talking about, it would very likely be a lot more extensible and flexible.
We might not need one for a lot of use cases. People can more easily reuse CensoredDistributions in any model.
We just do not need to note those. I meant a few people in the room might be working on something like this.
This from the delays project page is a classic LLMism I would not use in my own writing: “The switch to a fixed rule, and what it cost”.
The paper being in CDC clearance is the bullet. ComposableTuringIDModels and epiaware.org have most of what we need, and the latter has an approaches page we can link to with the requirements.
This [“One correction since submission…”] should not be on the project page or similar.
This page [the delays page] needs to link to primarycensored. Remove the documentation link and link to it there.
Cut “Taste is not an argument”. “Cost” is very LLM.
In all the decks I also see lots of little tiny aside comments in the same style the references are. I do not think we want any of those.
From the case for composable, I think overly why and not enough on ComposableTuringIDModels?
Can we cut the Rt estimation ecosystem? Need to add Comrade.jl as an example alongside SpeedyWeather.
Remove “, which does the fitting”. Remove “The proof of concept exists because of it”. Remove “Our migration was one rename. The cost is the tracking”. Here, “Automatic differentiation is the part that decided it” is more that future support is uncertain.
Cut “EpiAwareADTools.jl is where we keep our autodiff workarounds. We delete them when upstream ships a fix”.
So what is a composable unit, and how far does it go, are terrible? What about other approaches, and pulling in the distributions based approach from epiaware.org? Can also note that also has only one or a few maintainers.
Last but one slide should be “Is Julia the place for this work?” with what about JAX as a bullet.
Cut “Multiple dispatch is why a composed delay is still a distribution. I do not know how to write that as cleanly anywhere else”, and “The teams under Turing, under the autodiff backends, and under our own packages are all small”.
If we could work in a few more code examples from ComposableTuringIDModels that would be great, nothing that the audience will not know about epi modelling.
Remove “our migration was one rename”.
Rebuild the roadmap deck. Start from what epiaware.org needs, then approach one and approach two with code from epiaware.org, then inspiration as three bullets. Then “I tried in R” with stars and downloads, and “what do we need to implement this” as the transition. Funding, a small team, and buy-in before the agents slide, then Claude Max and “we still need funding” after it. Then a five point current approach slide, with a slide each for infrastructure, AD, docs, community in the age of robots, and governance including whale contributors with emojis. Open on the DRC Bundibugyo outbreak, with the wow and the jank.