But if the using them as mules is still producing silly mistakes, how will I have the confidence to defer to their intelligence for much more complex stuff?
These things bullshit their way about all the time. I've lost track of how many times they seem to produce something great, only for me, upon deeper inspect, to see what a subtle mess they have made. And when the work is a bit complex, I cannot verify on sight; I'd have to take time to do it.
Also, they absolutely cannot even produce some levels of code. Do you think I can just give them a prompt to produce a haskell-like language, allow them to crank for some hours, and have a language ready made?
Want an example? here is something Sonnet gave me just today:
const sort = sortKey ? { field: "name", order: "ascending" } as const : undefined
Where sortKey is defined as:
const sortKey: "name-asc" | "name-desc" | "recently-accessed" | "least-recently-accessed" | undefined
I just realized this a few minutes ago after reviewing the code.
Here is another one:
-------------------------------
Given:
queryX: >>(args
: {
entity: Ent
query: QueryArgs, Col, fOperators>
auditInfo?: AuditSpec
}
) => Promise, Col>[]>>
export type QueryArgs = StrKeyOf, FltrOp extends FilterOpsAll = FilterOpsAll> = {
/** Fields to include in results (defaults to all) */
fields?: Fld[],
/** Filters to apply */
filter?: RecordFilter,
/** Sorting to apply */
sort?: {
field: Fld
order: SortOrder
},
/** Pagination to apply */
page?: {
maxCount?: number | undefined
startFrom?: {
sortFieldKey: any,
idKey: ID
} | undefined
}
}
And:
const sort = sortKey ? { field: "name", order: "ascending" } as const : undefined
const xx = storage.queryX({ entity: "cabinets", query: { filter, sort, page: page ? { startFrom: page } : undefined } })
I get this as the type of xx: Promise[]>>
Which is obviously wrong. I should be getting the full type, i.e., all columns picked. The problem is that the Column generic parameter is not being properly inferred, which is (probably) due to the sorting by name, since the sort column is defined to have to be part of the query field name, so when field is not provided, TypeScript infers the fields as the sort column name.
Neither ChatGPT nor Claude Opus have been able to solve this after one hour, suggesting all kinds of things that don't work. But I have solved it myself, with:
export type QueryArgs = StrKeyOf, FltrOp extends FilterOpsAll = FilterOpsAll, Srt extends Fld = Fld> = {
/** Fields to include in results (defaults to all) */
fields?: Fld[],
/** Filters to apply */
filter?: RecordFilter,
/** Sorting to apply */
sort?: {
field: Srt// StrKeyOf
order: SortOrder
},
/** Pagination to apply */
page?: {
maxCount?: number | undefined
startFrom?: { sortFieldKey: any, idKey: ID } | undefined
}
}
And:
queryX: >, Srt extends Col = Col>(args
: {
entity: Ent,
query: QueryArgs, Col, fOperators, Srt>,
auditInfo?: AuditSpec
}
) => Promise, Col | Srt>[]>>