A key-value database, or key-value store, is a data storage paradigm designed for storing, retrieving, and managing associative arrays, a data structure more commonly known today as a dictionary.
I wonder if there's a place for something like matrix, but for repositories (or maybe matrix protocol can handle that?). A world where we have selfhosted, saas, etc, but all interlinked and searchable? Say I find a project on gitlab, I want to contribute to, I checkout to my personal server (or someone elses hosted), and raise a pr back to original repo.
I know it doesn't answer your question, just thinking aloud really.
> if the agent has difficulty generating Haskell code then that suggests agents aren't capable of reliably generalizing beyond their training data.
doesn't that apply to flesh-and-bone developers? ask someone who's only working in python to implement their current project in haskell and I'm not so sure you'll get very satisfying results.
May be it's just me, but the very first example (contacts form) looks better (easier to read) on the left than text in empty space on the right (which is supposed to be the good design)...
But not all of us are working in the open air office... Brightly lit office after 5pm in winter (ie after sunset) doesn't mean dark mode is the best option.
> As far as I could tell, it’s because the CEO or CTO didn’t think the type of work they were doing was worth doing, and also didn’t think they were making a difference.
So the CEO/CTO weren't able to express their concerns and priorities and instead just fired the whole team?
If, as you say, there were no financial reasons, then the team could've been re-purposed to do more meaningful (at least in CEO/CTO eyes) work.