8/ Absolutely DETERMINED to make mutable collections key in a dict? Make them the default parameter of a lambda:

>>> {{}: {}}
TypeError: unhashable type: 'dict'
>>> x = lambda y={}: y
>>> x()[1] = 2
>>> x()
{1: 2}
>>> {x: {}}
{<function <lambda> at 0x000001E45E80E440>: {}}

The program is up and tickets are live at www.hytradboi.com/2025/#program.

I'll keep updating this thread as the last 10 talks hit camera-ready.

Such a package index would encourage open source contribution of prompts plus pre-made code fragments

This might really help when building apps using coding assistants. Having assistants write so much code from scratch still feels unpredictable. What I really want is to be able to suggest from an index of code fragments and prompts which things to glue into my app.

But if you wanted to package up a partial table schema and some prompt about how it could be rendered in a UI, then the package manager+coding assistant could auto merge the partial schema into the user's existing schema and even make the right UI updates to show the new fields

Libraries and packages indexes (especially language specific ones) have been a boon for code reuse. But they can only be used for code that can be cleanly abstracted. I often encounter chunks of code I wish could reuse as a lib, but I can't because I can't abstract it well enough

A lot of no-code lab software (LIMS, automation scheduling) suffers from trying to reinvent a software practice concepts in a GUI. Things like branches, test environments, API integrations are either not supported or reinvented in strange ways.