Viewing profile — wpride

We do, but mostly as a fairly nice and fairly well-documented interface for plugging together tools like vector DBs and memory with LLMs. My feeling is that with the agentic/AutoGP…

Maybe "complaint" was the wrong word but I disagree with the conclusion that LLMs are "not for trustworthy production systems" for the reasons I stated. Full disclosure, I wrote a …

What is the complaint here exactly? That LLMs aren't enforcing database access best practices for you? That's not their job, that's your job. LLMs generate text. You do the rest. G…

Everyone in this space seems to be building on the LSP and classic auto-complete in particular as their UI. But I've found this to be non ideal. - As mentioned in this paper I defi…

Also, accumulating powerful backers and friends to signal "this is a successful company" instead of building an actual company.

Phew, was worried when all my CI jobs failed simultaneously

Not OC but we generate the client types with Apollo codegen ( https://www.apollographql.com/blog/typescript-graphql-code-g... ) using the schema file generated by our NestJS backen…

What news they choose to make News is an opinion.

We use Contracts too and are in the process of transitioning to Sorbet. In addition to the same runtime type checking as Contracts, Sorbet offers static type checking (and will re-…