6,881 karma · joined October 11, 2010
https://www.benkophone.com/
Currently building:
https://www.benko.app/
team@benko.app
EDIT: this is like saying hourly rate or salary is meaningless. Different people have different output. You have to evaluate performance.
EDIT2: just pray the LLM providers don’t start taking Patrick McKenzie’s advice and start charging based on “value delivered”
“ Automatic Prefix Caching (APC in short) caches the KV cache of existing queries, so that a new query can directly reuse the KV cache if it shares the same prefix with one of the existing queries, allowing the new query to skip the computation of the shared part.”
https://docs.vllm.ai/en/latest/features/automatic_prefix_cac...
EDIT: oh wait looks like I never got around to implementing the ability to use custom classes :) this is still in the to do section:
come up with a good "mix in" style to cast the objects returned from the iterator to a new class for implementing custom functionality (that one would normally include as part of the "boilerplate" class)
The idea is that you like SQL, but it gets repetitive writing joins and accessor code. I had always hoped it would catch on as a pattern: no boilerplate, automatic mapping to objects in your code of any query (whether generated by the ORM or passed in as a raw query) and easy to override/dynamically build bits of the query as you pass the object around.
Satellite internet is not a “generation above” fibre internet
And it is SO fucking cheap.
Not in Australia
There are sometimes false positives but when I give Kimi’s report to the frontier models they more often than not confirm they are valid security issues but didn’t find them themselves.
Is 2 better than x.ai
I saw /graphify recently which cuts down on exploration cost and seems more appealing (although I haven’t tried it yet)
If there is a decision that you need to make don’t ask me for input, do the thing that you think makes sense and then write down what you did and why.
If it’s the wrong thing I’ll update the docs to make it clear for next time.
Without this I would always wake up in the morning to an inbox full of questions and no work done, rather than an inbox full of finished tasks and maybe a couple of corrections.
With LLMs if I ask for a code analysis and plan to fix something they tend to put a list of questions at the end about which they want confirmation.
Then I have to waste time saying yes or no or coming up with the solution. If I tell them to instead just make assumptions and record them all at the end then I only need to correct 1 or 2 assumptions if required.
The right model for agentic API usage is having LLMs write scripts that use APIs. Connecting agents to MCPs and telling them to go and do stuff over and over not only wastes money but invites catastrophe.