291 karma · joined March 31, 2022
The interesting part is in the handling of joins. We can show a list of artworks, and for each artwork, a list of provenance timeline entries, and related data from other tables, and then use all of this data as context for the appraisal task. The UI for this is intentionally minimal; the user enters only a few words for a prompt (Appraisal column: "an appraisal of the artwork, in US dollars, for insurance purposes". Rationale column: "rationale for the appraisal").
People are conflating destructive and productive activities. These are fundamentally different.
(Or at least AI-assisted to the point where the author feels like they should mention it.)
If I'm running Windows, it means that the files and projects that I care about are on the Windows file system. And they need to be there, because my IDE and other GUI apps needs files to be on a real file system to work optimally. (A network share to a WSL2 file system would not let the IDE watch for changes, for instance.)
WSL1 was a great way to get a UNIX-style command line, with git, bash, latex etc., for the Windows file system. WSL2 was just too slow for this purpose; commands like "git status" would take multiple seconds on a large codebase.
Now I switched back to MacOS, and the proper UNIX terminal is a great advantage.
(W3C standards, for example, require "multiple independent implementations to proceed along a standardisation path". https://www.w3.org/TR/webdatabase/ )
(I wonder if it would convert cleanly to a redstone circuit...)
"Judges frequently invoke anti-redundancy principles in the interpretation of legal language, whether it appears in classic private-law documents such as contracts or classic public law-documents such as constitutions and statutes."
Redundancy: When Law Repeats Itself, John M. Golden (2016)
In a grocery store line once, I remember a distraught customer whose card was declined due to insufficient funds. The store manager came over, yanked the ethernet cable from the payment terminal, and told the customer to try again. "Accepted with signature."
That's it. It's the math notation from high school, plus cell references, which can be inserted by clicking a cell.
The engineering artifact is just a by-product. More often than not, the code is thrown away or never used again, once the experiments have been run and the paper has been published.
For example, if you propose some new technique to make databases faster (e.g. "store tuples column-wise instead of row-wise"), you'll implement it and run various workloads with and without the technique enabled. That gives you a quantitative measurement of the merit of the technique.
It does rule out some common SQLite use cases, such as using the database for app persistence. The app would never be able to upgrade the major version of PostgreSQL, unless it bundled PostgreSQL binaries for every major version ever used.
In theory the data directory works with any PostgreSQL binaries from the same major version of PostgreSQL, but I have seen cases where this fails e.g. because the binaries were from the same major version but compiled with different build options.
(I wonder what the specification-pages-to-man-years ratio is...)
Generating more training data from the same original data should not be fundamentally problematic in that sense.
A meeting happens every Tuesday at 9am, starting February 18, 2025. What time does the calendar show once DST kicks in?